Bug 766125
| Summary: | [abrt] imsettings-1.2.6-1.fc16: __GI___libc_free: Process /usr/libexec/imsettings-daemon was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Wim ten Have <whaveten> | ||||||||||||||||||||
| Component: | imsettings | Assignee: | Akira TAGOH <tagoh> | ||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||
| Version: | 16 | CC: | dakshay, felipevsw, i18n-bugs, jlmeram89, jmj.buckley, kb6tal, mike.cloaked, peljasz, rpiddapa, sarrab1976, sheepdestroyer, tagoh, victor.munteanu, vlademir.segan | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||
| Whiteboard: | abrt_hash:b5282fb123d7b42863f86e6388361f8c183b551a | ||||||||||||||||||||||
| Fixed In Version: | imsettings-1.2.8-1.fc16 | Doc Type: | Bug Fix | ||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2012-02-17 23:50:09 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
Wim ten Have
2011-12-10 12:06:23 UTC
Created attachment 544860 [details]
File: dso_list
Created attachment 544861 [details]
File: maps
Created attachment 544862 [details]
File: backtrace
I logged in! rating: 4 Package: imsettings-1.2.6-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) I don't know if this is a coincidence but after updating to: xfconf-4.8.1-1.fc16.x86_64 and xfwm4-4.8.3-1.fc16.x86_64 This has stopped occurring... This just occurred again so will submit new report via abrt.... #772342 turn on the computer rating: 4 Package: imsettings-1.2.6-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) I am not sure I understand what comment #8 implies? Can you offer a little more explanation. By the way after updating the orc package I have not seen this occurring on my machine so it is possible that the orc package was responsible for this bug as well as a few others related to gstreamer. However I have now not had any recurrence for a week or so. I know the original bug was related to kde but it would be useful to know if the original reporter has seen the problem recently or if it has not recurred. I had just updated the system and rebooted. When I signed back in there was an icon with a problem message. backtrace_rating: 4 Package: imsettings-1.2.6-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 555407 [details]
File: backtrace
Does this issue happen every startup time for you? I want to reproduce this if possible. can you please provide more detailed information such as how many ibus-engines you installed, your locale, current IM configuration etc? To collect the ibus-engine packages, this might helps: $ for i in /usr/share/ibus/component/*; do rpm -qf $i; done|sort|uniq For locale information: $ locale For IM configuration, please attach your $HOME/.imsettings.log Although I have not had a repeat of this issue after updates about a week ago. However for completeness my info that you requested (that may be useful as a comparison with that of Jim) is: [mike@samsung1 ~]$ for i in /usr/share/ibus/component/*; do rpm -qf $i; done|sort|uniq ibus-1.4.0-17.fc16.i686 ibus-m17n-1.3.3-7.fc16.i686 ibus-rawcode-1.3.1.20100707-5.fc16.i686 [mike@samsung1 ~]$ locale LANG=en_GB.UTF-8 LC_CTYPE="en_GB.UTF-8" LC_NUMERIC="en_GB.UTF-8" LC_TIME="en_GB.UTF-8" LC_COLLATE="en_GB.UTF-8" LC_MONETARY="en_GB.UTF-8" LC_MESSAGES="en_GB.UTF-8" LC_PAPER="en_GB.UTF-8" LC_NAME="en_GB.UTF-8" LC_ADDRESS="en_GB.UTF-8" LC_TELEPHONE="en_GB.UTF-8" LC_MEASUREMENT="en_GB.UTF-8" LC_IDENTIFICATION="en_GB.UTF-8" LC_ALL= [mike@samsung1 ~]$ I will also attach my imsettings.log shortly - as I said I have not had a repeat of this since my comments to this report earlier. Created attachment 555526 [details]
imsettings log for mike cloaked
This error appeared when I booted up first time on the day. backtrace_rating: 4 Package: imsettings-1.2.6-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 555597 [details]
File: backtrace
enter on gnome shell and look screen backtrace_rating: 4 Package: imsettings-1.2.6-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 558067 [details]
File: backtrace
in System setting I changed Fallback mode ON, logged out and logged in, changed back to OFF, logged out and in, then this crash backtrace_rating: 3 Package: imsettings-1.2.6-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 559008 [details]
File: backtrace
imsettings-1.2.8-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/imsettings-1.2.8-1.fc16 Package imsettings-1.2.8-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing imsettings-1.2.8-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1545/imsettings-1.2.8-1.fc16 then log in and leave karma (feedback). Booted up. backtrace_rating: 4 Package: imsettings-1.2.7.1-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 561210 [details]
File: backtrace
imsettings-1.2.8-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |