Bug 599924 - [abrt] crash in imsettings-0.108.0-2.fc13: imsettings_monitor_add_file: Process /usr/libexec/im-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in imsettings-0.108.0-2.fc13: imsettings_monitor_add_file: Proce...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: imsettings
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:04a689180fbea4f036aaeac2197...
: 575433 579413 611265 (view as bug list)
Depends On:
Blocks: 607506
TreeView+ depends on / blocked
 
Reported: 2010-06-03 21:01 UTC by cornel panceac
Modified: 2010-07-13 20:39 UTC (History)
5 users (show)

Fixed In Version: imsettings-0.108.0-4.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 607506 (view as bug list)
Environment:
Last Closed: 2010-07-13 07:54:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (14.03 KB, text/plain)
2010-06-03 21:01 UTC, cornel panceac 		no flags Details
imsettings log (946 bytes, text/x-log)
2010-06-04 03:19 UTC, cornel panceac 		no flags Details
View All

Description cornel panceac 2010-06-03 21:01:16 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/im-settings-daemon
component: imsettings
crash_function: imsettings_monitor_add_file
executable: /usr/libexec/im-settings-daemon
global_uuid: 04a689180fbea4f036aaeac21972d3bc7e3d0e98
kernel: 2.6.33.4-95.fc13.i686.PAE
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 cornel panceac 2010-06-03 21:01:18 UTC 
Created attachment 420423 [details]
File: backtrace
Comment 2 Akira TAGOH 2010-06-04 01:47:26 UTC 
can you upload $HOME/.imsettings.log as well?
Comment 3 cornel panceac 2010-06-04 03:19:46 UTC 
Created attachment 421107 [details]
imsettings log

of course, here it is.
Comment 4 Akira TAGOH 2010-06-24 09:36:33 UTC 
Thanks. fixed in imsettings-0.108.0-4.fc13.
Comment 5 Fedora Update System 2010-06-24 09:42:22 UTC 
imsettings-0.108.0-4.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/imsettings-0.108.0-4.fc13
Comment 6 Fedora Update System 2010-06-24 09:56:02 UTC 
imsettings-0.108.0-4.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/imsettings-0.108.0-4.fc12
Comment 7 Fedora Update System 2010-06-24 16:34:42 UTC 
imsettings-0.108.0-4.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update imsettings'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/imsettings-0.108.0-4.fc13
Comment 8 Akira TAGOH 2010-06-29 02:31:08 UTC 
*** Bug 579413 has been marked as a duplicate of this bug. ***
Comment 9 Akira TAGOH 2010-06-29 02:33:42 UTC 
*** Bug 575433 has been marked as a duplicate of this bug. ***
Comment 10 Akira TAGOH 2010-07-05 01:50:59 UTC 
*** Bug 611265 has been marked as a duplicate of this bug. ***
Comment 11 BIGuban 2010-07-05 15:11:30 UTC 
Package: imsettings-0.108.0-3.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
it`s happen when I login my profile
Comment 12 Akira TAGOH 2010-07-06 01:28:44 UTC 
Please try the testing package above and add your comment with your karma there to speed up pushing the update to stable.
Comment 13 Fedora Update System 2010-07-13 07:54:02 UTC 
imsettings-0.108.0-4.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 14 Fedora Update System 2010-07-13 20:39:04 UTC 
imsettings-0.108.0-4.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.