Bug 601609 - [abrt] crash in imsettings-0.108.0-2.fc13: IA__g_convert_with_fallback: Process /usr/libexec/im-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in imsettings-0.108.0-2.fc13: IA__g_convert_with_fallback: Proce...
Alias: None
Product: Fedora
Classification: Fedora
Component: imsettings   
(Show other bugs)
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:2f9cf38cdaa05e629cd7b152429...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-08 10:15 UTC by walid bahgat
Modified: 2011-01-05 11:21 UTC (History)
2 users (show)

Fixed In Version: imsettings-1.0.0-1.fc15
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-01-05 11:21:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (28.56 KB, text/plain)
2010-06-08 10:15 UTC, walid bahgat
no flags Details

Description walid bahgat 2010-06-08 10:15:51 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/im-settings-daemon
component: imsettings
crash_function: IA__g_convert_with_fallback
executable: /usr/libexec/im-settings-daemon
global_uuid: 2f9cf38cdaa05e629cd7b1524292b2260b7fea09
package: imsettings-0.108.0-2.fc13
rating: 4
reason: Process /usr/libexec/im-settings-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 walid bahgat 2010-06-08 10:15:54 UTC
Created attachment 422131 [details]
File: backtrace

Comment 2 Akira TAGOH 2010-06-09 04:42:29 UTC
Can you upload a core file as well? it's unlikely to segfault there unless the memory is corrupted or something failed during gathering the information.

Comment 3 Akira TAGOH 2011-01-05 11:21:23 UTC
The problematic code causing this issue isn't in imsettings-1.0.0-1.fc15 anymore. so closing.

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