Bug 1070877

Summary: [abrt] tmux: evbuffer_chain_new(): tmux killed by SIGSEGV
Product: [Fedora] Fedora Reporter: John Schmitt <marmalodak>
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, marmalodak, praiskup, rosset.filipe, strobert, sven
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2e740614a18820aac562a2b692f227998fd53a26
Whiteboard: abrt_hash:f5125587aefa563c448bfa3fc2bbf6169f019682
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:55:16 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description John Schmitt 2014-02-27 16:07:52 UTC
Description of problem:
My .xinitrc launches xterm.  From there I launch openbox manually.

openbox --replace --debug

I created my tmux session, then logged out of openbox.
Then I started KDE with 

startkde 

from the xterm window.

Version-Release number of selected component:
tmux-1.8-3.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        tmux -2 new-session -d -s badboy
crash_function: evbuffer_chain_new
executable:     /usr/bin/tmux
kernel:         3.13.4-200.fc20.x86_64
runlevel:       N 3
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 evbuffer_chain_new at buffer.c:168
 #3 _evbuffer_expand_fast at buffer.c:1886
 #4 evbuffer_read at buffer.c:2087
 #5 bufferevent_readcb at bufferevent_sock.c:165
 #6 event_process_active_single_queue at event.c:1350
 #7 event_process_active at event.c:1420
 #8 event_base_loop at event.c:1621
 #9 event_loop at event.c:1533
 #10 server_loop at server.c:207
 #11 server_start at server.c:198

Comment 1 John Schmitt 2014-02-27 16:07:57 UTC
Created attachment 868607 [details]
File: backtrace

Comment 2 John Schmitt 2014-02-27 16:08:01 UTC
Created attachment 868608 [details]
File: cgroup

Comment 3 John Schmitt 2014-02-27 16:08:06 UTC
Created attachment 868609 [details]
File: core_backtrace

Comment 4 John Schmitt 2014-02-27 16:08:08 UTC
Created attachment 868610 [details]
File: dso_list

Comment 5 John Schmitt 2014-02-27 16:08:10 UTC
Created attachment 868611 [details]
File: environ

Comment 6 John Schmitt 2014-02-27 16:08:13 UTC
Created attachment 868612 [details]
File: limits

Comment 7 John Schmitt 2014-02-27 16:08:15 UTC
Created attachment 868613 [details]
File: maps

Comment 8 John Schmitt 2014-02-27 16:08:19 UTC
Created attachment 868614 [details]
File: open_fds

Comment 9 John Schmitt 2014-02-27 16:08:23 UTC
Created attachment 868615 [details]
File: proc_pid_status

Comment 10 John Schmitt 2014-02-27 16:08:27 UTC
Created attachment 868616 [details]
File: var_log_messages

Comment 11 Filipe Rosset 2014-02-27 19:04:03 UTC
Hi John, can you please update to the latest version (1.9a-2) and double check if you will be able to reproduce the issue?

yum update tmux --enablerepo=updates-testing -y

Comment 12 John Schmitt 2014-03-02 02:10:23 UTC
I've only just tried it, but so far so good.

$ rpm -q tmux
tmux-1.9a-2.fc20.x86_64

Comment 13 John Schmitt 2014-03-08 23:17:17 UTC
Mar 08 14:43:05 localhost.localdomain kernel: traps: tmux[1865] general protection ip:7f9a12959fe6 sp:7fff74ae5a90 error:0 in libc-2.18.so[7f9a128dc000+1b4000]
Mar 08 14:43:06 localhost.localdomain abrt-hook-ccpp[1378]: Saved core dump of pid 1865 (/usr/bin/tmux) to /var/tmp/abrt/ccpp-2014-03-08-14:43:05-1865 (21659648 bytes)

Is this the same problem?

rpm -q tmux
tmux-1.9a-2.fc20.x86_64

FWIW, I rely heavily on powerline.

Comment 14 Filipe Rosset 2014-03-09 12:58:59 UTC
I'm not sure, opened upstream bug to track this issue:
https://sourceforge.net/p/tmux/tickets/111/

Comment 15 Filipe Rosset 2014-03-09 15:45:33 UTC
John, can you please post all the steps to reproduce the issue in upstream bug?
Please remember to add all details, tmux/powerline versions, etc.
Thanks.

Comment 16 John Schmitt 2014-03-29 01:12:11 UTC
Did they just close the upstream bug as not reproducible?

Comment 17 Fedora End Of Life 2015-05-29 11:05:03 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 18 Fedora End Of Life 2015-06-30 00:55:16 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.