Bug 891757

Summary: [abrt] alltray-0.71b-3.fc17: g_logv: Process /usr/bin/alltray was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Chris <chris.j.n>
Component: alltrayAssignee: Rahul Sundaram <metherid>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: drizt72, huzaifas, metherid, yosifovemil
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a95a08f22397533cf96fdc7e0cb50d33f81a7471
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 04:52:00 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: xsession_errors
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Chris 2013-01-03 21:57:52 UTC
Version-Release number of selected component:
alltray-0.71b-3.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/bin/alltray
crash_function: g_logv
kernel:         3.6.10-2.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 g_logv at gmessages.h:101
: #4 handle_error at xcb_io.c:212
: #5 handle_response at xcb_io.c:324
: #8 gdk_flush at gdkevents-x11.c:2584
: #9 gtk_main at gtkmain.c:1259
: #10 show_hide_window at utils.c:1908
: #15 gtk_widget_activate at gtkwidget.c:5048
: #16 gtk_menu_shell_activate_item at gtkmenushell.c:1283
: #17 gtk_menu_shell_button_release at gtkmenushell.c:710
: #18 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86

Comment 1 Chris 2013-01-03 21:57:54 UTC
Created attachment 672226 [details]
File: core_backtrace

Comment 2 Chris 2013-01-03 21:57:56 UTC
Created attachment 672227 [details]
File: environ

Comment 3 Chris 2013-01-03 21:57:58 UTC
Created attachment 672228 [details]
File: backtrace

Comment 4 Chris 2013-01-03 21:58:00 UTC
Created attachment 672229 [details]
File: limits

Comment 5 Chris 2013-01-03 21:58:01 UTC
Created attachment 672230 [details]
File: cgroup

Comment 6 Chris 2013-01-03 21:58:03 UTC
Created attachment 672231 [details]
File: smolt_data

Comment 7 Chris 2013-01-03 21:58:04 UTC
Created attachment 672232 [details]
File: xsession_errors

Comment 8 Chris 2013-01-03 21:58:06 UTC
Created attachment 672233 [details]
File: executable

Comment 9 Chris 2013-01-03 21:58:09 UTC
Created attachment 672234 [details]
File: maps

Comment 10 Chris 2013-01-03 21:58:10 UTC
Created attachment 672235 [details]
File: dso_list

Comment 11 Chris 2013-01-03 21:58:12 UTC
Created attachment 672236 [details]
File: proc_pid_status

Comment 12 Chris 2013-01-03 21:58:14 UTC
Created attachment 672237 [details]
File: var_log_messages

Comment 13 Chris 2013-01-03 21:58:15 UTC
Created attachment 672238 [details]
File: open_fds

Comment 14 Emil 2013-02-02 10:45:07 UTC
I am using Fedora 17, with MATE desktop environment (though you probably see that already somewhere in the bug report). 
I use alltray with a few applications (firefox, terminator and thunderbird). 

In order to reproduce the bug:
1. Install terminator:
	yum install terminator
2. Set as startup application the following command 
	systray --key Alt:s terminator
3. It should crash when you log in.

Firefox and thunderbird start OK with this program, even as startup applications. Terminator only has this problem as a startup app, so if you run it when you already 
have logged in it will not crash. 


backtrace_rating: 4
Package: alltray-0.71b-3.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Comment 15 Fedora End Of Life 2013-07-04 00:47:55 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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.

Comment 16 Fedora End Of Life 2013-08-01 04:52:05 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.