Description of problem: Crash on Tmux session exit Version-Release number of selected component: tmux-1.9a-2.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: tmux crash_function: evbuffer_chain_insert executable: /usr/bin/tmux kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 evbuffer_chain_insert at buffer.c:295 #1 evbuffer_add at buffer.c:1608 #2 bufferevent_write at bufferevent.c:379 #3 tty_puts at tty.c:402 #5 tty_putcode at tty.c:364 #6 tty_start_tty at tty.c:208 #7 server_client_msg_dispatch at server-client.c:881 #8 server_client_callback at server-client.c:235 #9 event_process_active_single_queue at event.c:1350 #10 event_process_active at event.c:1420
Created attachment 885479 [details] File: backtrace
Created attachment 885480 [details] File: cgroup
Created attachment 885481 [details] File: core_backtrace
Created attachment 885482 [details] File: dso_list
Created attachment 885483 [details] File: environ
Created attachment 885484 [details] File: exploitable
Created attachment 885485 [details] File: limits
Created attachment 885486 [details] File: maps
Created attachment 885487 [details] File: open_fds
Created attachment 885488 [details] File: proc_pid_status
Created attachment 885489 [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.
(In reply to Filipe Rosset from comment #12) > 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. It happened one time only. I'm afraid I can't provide any clue.