Bug 613677

Summary: [abrt] crash in lxsession-0.4.4-1.fc13: raise: Process /usr/bin/lxsession was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Terry Wallwork <terrywallwork>
Component: lxsessionAssignee: 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   
URL: https://sourceforge.net/tracker/?func=detail&aid=3030576&group_id=180858&atid=894869
Whiteboard: abrt_hash:8c74c15d97f37041c1d8362a45eeba8decfa12fb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 14:32:24 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 Terry Wallwork 2010-07-12 14:52:40 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: lxsession
comment: I think it was loggin in when it happened
component: lxsession
crash_function: raise
executable: /usr/bin/lxsession
global_uuid: 8c74c15d97f37041c1d8362a45eeba8decfa12fb
kernel: 2.6.33.6-147.fc13.i686
package: lxsession-0.4.4-1.fc13
rating: 4
reason: Process /usr/bin/lxsession was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 Terry Wallwork 2010-07-12 14:52:42 UTC
Created attachment 431194 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-07-16 14:32:24 UTC
Thanks for your bug report. I forwarded it upstream as https://sourceforge.net/tracker/?func=detail&aid=3030576&group_id=180858&atid=894869

Feel free to add yourself to the upstream bug report in order to follow any changes. Even if you don't, will be notified once this bug is resolved in Fedora. If I need more information, I will get back to you.

I'm now closing the bug UPSTREAM because this is where further investigation should take place.

Comment 4 Christoph Wickert 2010-07-17 17:04:37 UTC
I'm aware of that fix, I will apply it once there is a statement from upstream on bug 614608.