Bug 1131903

Summary: [abrt] tmux: window_pane_active_lost(): tmux killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Evgeniy Gurevich <godlike_devil>
Component: tmuxAssignee: Sven Lankes <sven>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcantrell, praiskup, rosset.filipe, strobert, sven
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/13027e763a70f5ddd4d318af70bfbed865379356
Whiteboard: abrt_hash:94a142259bb86dd29117a612a1e9153d03db72df
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:09:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Evgeniy Gurevich 2014-08-20 09:15:09 UTC 
Description of problem:
Just crashed during ordinary usage.

Version-Release number of selected component:
tmux-1.9a-2.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        tmux
crash_function: window_pane_active_lost
executable:     /usr/bin/tmux
kernel:         3.15.10-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_swap_pane_exec at cmd-swap-pane.c:123
 #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
Comment 1 Evgeniy Gurevich 2014-08-20 09:15:13 UTC 
Created attachment 928724 [details]
File: backtrace
Comment 2 Evgeniy Gurevich 2014-08-20 09:15:14 UTC 
Created attachment 928725 [details]
File: cgroup
Comment 3 Evgeniy Gurevich 2014-08-20 09:15:15 UTC 
Created attachment 928726 [details]
File: core_backtrace
Comment 4 Evgeniy Gurevich 2014-08-20 09:15:17 UTC 
Created attachment 928727 [details]
File: dso_list
Comment 5 Evgeniy Gurevich 2014-08-20 09:15:18 UTC 
Created attachment 928728 [details]
File: environ
Comment 6 Evgeniy Gurevich 2014-08-20 09:15:20 UTC 
Created attachment 928729 [details]
File: exploitable
Comment 7 Evgeniy Gurevich 2014-08-20 09:15:21 UTC 
Created attachment 928730 [details]
File: limits
Comment 8 Evgeniy Gurevich 2014-08-20 09:15:22 UTC 
Created attachment 928731 [details]
File: maps
Comment 9 Evgeniy Gurevich 2014-08-20 09:15:24 UTC 
Created attachment 928732 [details]
File: open_fds
Comment 10 Evgeniy Gurevich 2014-08-20 09:15:25 UTC 
Created attachment 928733 [details]
File: proc_pid_status
Comment 11 Evgeniy Gurevich 2014-08-20 09:15:26 UTC 
Created attachment 928734 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 12:41:02 UTC 
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.
Comment 13 Fedora End Of Life 2015-06-29 22:09:34 UTC 
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.