Bug 612361 - [abrt] crash in imsettings-lxde-0.108.0-3.fc13: set_engine: Process /usr/bin/imsettings-lxde-helper was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in imsettings-lxde-0.108.0-3.fc13: set_engine: Process /usr/bin/...
Status: CLOSED DUPLICATE of bug 603582
Alias: None
Product: Fedora
Classification: Fedora
Component: imsettings
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:69d73207e236183ca9ff39a0bea...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-08 01:08 UTC by Corey Welton
Modified: 2010-07-08 02:32 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-07-08 02:32:31 UTC


Attachments (Terms of Use)
File: backtrace (6.26 KB, text/plain)
2010-07-08 01:08 UTC, Corey Welton
no flags Details

Description Corey Welton 2010-07-08 01:08:10 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: imsettings-lxde-helper
component: imsettings
crash_function: set_engine
executable: /usr/bin/imsettings-lxde-helper
global_uuid: 69d73207e236183ca9ff39a0beaa1d95be3f3d6a
kernel: 2.6.33.5-124.fc13.x86_64
package: imsettings-lxde-0.108.0-3.fc13
rating: 4
reason: Process /usr/bin/imsettings-lxde-helper was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.  I simply started LXDE after installing

Comment 1 Corey Welton 2010-07-08 01:08:12 UTC
Created attachment 430210 [details]
File: backtrace

Comment 2 Corey Welton 2010-07-08 02:02:58 UTC
Sorry, that was not clear -- the abrt submitter is a bit lacking in that dept.

To clarify -- I had IME stuff installed before, using it with Xfce and had just installed LXDE to poke around.  first time I booted into LXDE, its imsettings helper caused the above crash. 

If it helps/matters any, I use the pinyin input method editor.

Comment 3 Akira TAGOH 2010-07-08 02:32:31 UTC

*** This bug has been marked as a duplicate of bug 603582 ***


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