Bug 642910

Summary: [abrt] xfce4-xfapplet-plugin-0.1.0-9.fc12: raise: Process /usr/libexec/xfce4/panel-plugins/xfce4-xfapplet-plugin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Sylvain Arth <sylvain>
Component: xfce4-xfapplet-pluginAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:e85d3884d5cb8829f963814b8ebd4259fa9e695a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-20 21:18: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: backtrace none

Description Sylvain Arth 2010-10-14 06:38:16 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/xfce4/panel-plugins/xfce4-xfapplet-plugin socket_id 34604408 name xfapplet id 128681135231 display_name XfApplet size 35 screen_position 2
component: xfce4-xfapplet-plugin
crash_function: raise
executable: /usr/libexec/xfce4/panel-plugins/xfce4-xfapplet-plugin
kernel: 2.6.34.7-56.fc13.i686
package: xfce4-xfapplet-plugin-0.1.0-9.fc12
rating: 4
reason: Process /usr/libexec/xfce4/panel-plugins/xfce4-xfapplet-plugin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1287010630
uid: 500
Comment 1 Sylvain Arth 2010-10-14 06:38:18 UTC 
Created attachment 453382 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-10-27 17:10:05 UTC 
What did you do when the applet crashed? Are you able to reproduce the crash reliably? If so, how?
Comment 3 Sylvain Arth 2010-10-29 23:06:07 UTC 
(In reply to comment #2)
> What did you do when the applet crashed? Are you able to reproduce the crash
> reliably? If so, how?
I sincerely have no clue on how it could even happened
I was not logged with Xfce but with Gnome at that time and away from the box
The odd thing is I found the  GDM login instead of the screensaver unlock GUI when I came back. When I don't disable the powersaving stuff this happens regularly on this machine, producing many application crashes with unusable backtraces even with all the related debuginfo installed.
At last, I'm totally sure there was no reboot at all because of the uptime value coherent in regard of may last boot.
Sorry not to be able to bring more information useful for further investigation.
Comment 4 Christoph Wickert 2010-10-30 23:11:36 UTC 
Thanks for your feedback. Does this mean that you whole session crashed or was the session still active when you logged in through GDM?
Comment 5 Christoph Wickert 2010-11-26 00:43:24 UTC 
Ping?
Comment 6 Christoph Wickert 2011-02-20 21:18:00 UTC 
Although I did not receive any more feedback from you I forwarded the bug to the Xfce bug tracker at http://bugzilla.xfce.org/show_bug.cgi?id=7323

Fell free to subscribe to the upstream bug report and please provide more input there.