Bug 650792 - [abrt] lxsession-edit-0.1.1-4.fc13: raise: Process /usr/bin/lxsession-edit was killed by signal 6 (SIGABRT)
[abrt] lxsession-edit-0.1.1-4.fc13: raise: Process /usr/bin/lxsession-edit wa...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: lxsession-edit (Show other bugs)
14
i686 Unspecified
low Severity medium
: ---
: ---
Assigned To: Christoph Wickert
Fedora Extras Quality Assurance
https://sourceforge.net/tracker/?func...
abrt_hash:6a08e3dff13440a776a04616d93...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-07 23:02 EST by Anthony
Modified: 2010-11-17 17:05 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-17 17:05:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
File: backtrace (24.36 KB, text/plain)
2010-11-07 23:02 EST, Anthony
no flags Details

  None (edit)
Description Anthony 2010-11-07 23:02:37 EST
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: lxsession-edit
component: lxsession-edit
crash_function: raise
executable: /usr/bin/lxsession-edit
kernel: 2.6.35.6-48.fc14.i686
package: lxsession-edit-0.1.1-4.fc13
rating: 4
reason: Process /usr/bin/lxsession-edit was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. I do not recall how or why this program crashed!
time: 1289184423
uid: 500
Comment 1 Anthony 2010-11-07 23:02:40 EST
Created attachment 458569 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-11-17 17:05:32 EST
Hi Anthony,

thanks for reporting this bug. I have forwarded your report to the developers at 
https://sourceforge.net/tracker/?func=detail&aid=3111073&group_id=180858&atid=894869
Further investigation will take place in the LXDE bugtracker. If I have any questions, I will get back to you. I will let you know once this issue is resolved in Fedora.

Note You need to log in before you can comment on or make changes to this bug.