Bug 680313 - [abrt] lxsession-edit-0.1.1-4.fc13: __libc_message: Process /usr/bin/lxsession-edit was killed by signal 6 (SIGABRT)
Summary: [abrt] lxsession-edit-0.1.1-4.fc13: __libc_message: Process /usr/bin/lxsessio...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: lxsession-edit
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL: https://sourceforge.net/tracker/?func...
Whiteboard: abrt_hash:0b4f2a2752f57562e4c0a720bb5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-25 02:06 UTC by flashl
Modified: 2011-03-06 19:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-06 19:35:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (26.17 KB, text/plain)
2011-02-25 02:07 UTC, flashl
no flags Details

Description flashl 2011-02-25 02:06:59 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 26799 bytes
cmdline: lxsession-edit
component: lxsession-edit
Attached file: coredump, 2490368 bytes
crash_function: __libc_message
executable: /usr/bin/lxsession-edit
kernel: 2.6.35.11-83.fc14.i686.PAE
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)
time: 1298592521
uid: 500

How to reproduce
-----
1.  Open, modified, and closed desktop appearance widget
2.
3.

Comment 1 flashl 2011-02-25 02:07:01 UTC
Created attachment 480907 [details]
File: backtrace

Comment 2 Christoph Wickert 2011-02-25 20:30:45 UTC
You mean you changed something in lxappearance while lxsession-edit was opened? Does it crash every time you do this?

Comment 3 flashl 2011-02-25 21:31:51 UTC
Sorry unable to reproduce.  Keystrokes = preferences-->Customize Look and Feel-->Widget.

Comment 4 Christoph Wickert 2011-03-06 19:35:14 UTC
I don't really get your description, nevertheless I have forwarded the crash report to the developer at https://sourceforge.net/tracker/?func=detail&aid=3201521&group_id=180858&atid=894869

Further investigation of this crash should take place upstream. Feel free to subscribe to that bug report in order to get notified of changes. I will get back
to you if I need more information and notify you if the crash was fixed in
Fedora.


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