Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Searching through journalctl, same spot triggers consistent failure, but not sure why Version-Release number of selected component: tmux-3.2a-2.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-alacritty-8602.scope cmdline: tmux crash_function: __memmove_avx_unaligned_erms executable: /usr/bin/tmux journald_cursor: s=f49ba2bcf80e48abbd5d8373343bbef1;i=75d8;b=7b92f4ed3fbf4303998f762ba1d85995;m=48a22be1b;t=5d65a1ac8f860;x=6b20aa6e29bae36 kernel: 5.15.14-200.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __memmove_avx_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:549 #1 memmove at /usr/include/bits/string_fortified.h:36 #2 status_prompt_key at /usr/src/debug/tmux-3.2a-2.fc35.x86_64/status.c:1318 #3 server_client_handle_key at /usr/src/debug/tmux-3.2a-2.fc35.x86_64/server-client.c:1364 #4 tty_keys_next at /usr/src/debug/tmux-3.2a-2.fc35.x86_64/tty-keys.c:833 #5 tty_read_callback at /usr/src/debug/tmux-3.2a-2.fc35.x86_64/tty.c:171 #6 event_persist_closure at /usr/src/debug/libevent-2.1.12-4.fc35.x86_64/event.c:1623 #7 event_process_active_single_queue at /usr/src/debug/libevent-2.1.12-4.fc35.x86_64/event.c:1682 #8 event_process_active at /usr/src/debug/libevent-2.1.12-4.fc35.x86_64/event.c:1783 #9 event_base_loop at /usr/src/debug/libevent-2.1.12-4.fc35.x86_64/event.c:2006
Created attachment 1853193 [details] File: backtrace
Created attachment 1853194 [details] File: core_backtrace
Created attachment 1853195 [details] File: cpuinfo
Created attachment 1853196 [details] File: dso_list
Created attachment 1853197 [details] File: environ
Created attachment 1853198 [details] File: exploitable
Created attachment 1853199 [details] File: limits
Created attachment 1853200 [details] File: maps
Created attachment 1853201 [details] File: mountinfo
Created attachment 1853202 [details] File: open_fds
Created attachment 1853203 [details] File: proc_pid_status
I hit this a few times. Looked upstream and was mentioned issue 2905 [0] and issue 3048 [1] where the user bisect to the fix [2]. Not sure if one wants to backport or to wait 3.3 release (...) git tag --contains 022d0210c5afa4e516183bf19715316ccca5d240 3.3-rc [0] https://github.com/tmux/tmux/issues/2905 [1] https://github.com/tmux/tmux/issues/3048 [2] https://github.com/tmux/tmux/commit/022d0210c5afa4e516183bf19715316ccca5d240
*** Bug 2080104 has been marked as a duplicate of this bug. ***
git tag --contains 022d0210c5afa4e516183bf19715316ccca5d240 3.3 3.3-rc 3.3a None of which is in Fedora.
FEDORA-2022-8985737e34 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8985737e34
(In reply to Fedora Update System from comment #15) > FEDORA-2022-8985737e34 has been submitted as an update to Fedora 36. > https://bodhi.fedoraproject.org/updates/FEDORA-2022-8985737e34 Yay, thanks!
FEDORA-2022-8985737e34 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-8985737e34` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8985737e34 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-8985737e34 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.