Description of problem: This seems to happen the first time after a reboot when I connect to this machine remotely, using SSH. It started to occur after I set fish 2.00 (compiled from source) as my default shell. As a workaround, on the first login, I use CTRL-B CTRL-Z to background the shell, then disconnect my SSH client, then reconnect. I think this is when tmux crashes. There are a lot of things going on at once, but the obvious suspect is fish, which is a beta compiled from source. Version-Release number of selected component: tmux-1.7-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/tmux new-session -s brian-remote crash_function: main_arena executable: /usr/bin/tmux kernel: 3.8.1-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 main_arena at /lib64/libc.so.6 #1 bufferevent_disable at bufferevent.c:505 #2 tty_stop_tty at tty.c:259 #3 tty_close at tty.c:307 #4 tty_free at tty.c:327 #5 server_client_lost at server-client.c:144 #6 event_process_active_single_queue at event.c:1340 #7 event_process_active at event.c:1407 #8 event_base_loop at event.c:1604 #9 event_loop at event.c:1518
Created attachment 706838 [details] File: backtrace
Created attachment 706839 [details] File: build_ids
Created attachment 706840 [details] File: cgroup
Created attachment 706841 [details] File: core_backtrace
Created attachment 706842 [details] File: dso_list
Created attachment 706843 [details] File: environ
Created attachment 706844 [details] File: limits
Created attachment 706845 [details] File: maps
Created attachment 706846 [details] File: open_fds
Created attachment 706847 [details] File: proc_pid_status
Created attachment 706848 [details] File: var_log_messages
*** Bug 914858 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.