Hide Forgot
Version-Release number of selected component: tmux-1.8-2.fc18 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: tmux crash_function: screen_write_linefeed executable: /usr/bin/tmux kernel: 3.11.4-101.fc18.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 screen_write_linefeed #1 input_c0_dispatch #2 input_parse #3 window_pane_read_callback #4 bufferevent_readcb at /lib64/libevent-2.0.so.5 #5 event_base_loop at /lib64/libevent-2.0.so.5 #6 server_loop #7 server_start #8 client_connect #9 client_main
Created attachment 818911 [details] File: backtrace
Created attachment 818912 [details] File: cgroup
Created attachment 818913 [details] File: core_backtrace
Created attachment 818914 [details] File: dso_list
Created attachment 818915 [details] File: environ
Created attachment 818916 [details] File: exploitable
Created attachment 818917 [details] File: limits
Created attachment 818918 [details] File: maps
Created attachment 818919 [details] File: open_fds
Created attachment 818920 [details] File: proc_pid_status
Created attachment 818921 [details] File: var_log_messages
Do you have any method to reproduce this? I contacted the tmux (upstream) team and they are looking for more information. like debug symbols in the backstrace and especially steps to reproduce.
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.