Version-Release number of selected component: tmux-1.9a-2.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: tmux new-session -d -s wm -n rand crash_function: window_pane_active_lost executable: /usr/bin/tmux kernel: 3.13.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 window_pane_active_lost at window.c:426 #1 window_set_active_pane at window.c:451 #2 cmd_rotate_window_exec at cmd-rotate-window.c:113 #3 cmdq_continue at cmd-queue.c:227 #4 cmdq_run at cmd-queue.c:176 #5 key_bindings_dispatch at key-bindings.c:219 #6 server_client_handle_key at server-client.c:486 #7 tty_keys_next at tty-keys.c:586 #8 tty_read_callback at tty.c:168 #9 bufferevent_readcb at bufferevent_sock.c:186
Created attachment 882700 [details] File: backtrace
Created attachment 882701 [details] File: cgroup
Created attachment 882702 [details] File: core_backtrace
Created attachment 882703 [details] File: dso_list
Created attachment 882704 [details] File: environ
Created attachment 882705 [details] File: exploitable
Created attachment 882706 [details] File: limits
Created attachment 882707 [details] File: maps
Created attachment 882708 [details] File: open_fds
Created attachment 882709 [details] File: proc_pid_status
Created attachment 882710 [details] File: var_log_messages
Are you able to reproduce the issue? I need a test case to reproduce the issue, prior to file a bug with upstream, otherwise they will not work on it.
I don't know how to consistently reproduce, it always happens during a switch between panes in a split using <prefix>-o It's not very consistent but I have it happen at least once a week. I don't know how much better to describe it. I've been told that debian has patched against something that behaves similarly and I *think* this is the relevant patch. http://anonscm.debian.org/cgit/collab-maint/tmux.git/tree/debian/patches/upstream-78e783e786.diff
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.