Bug 789824
| Summary: | [abrt] dconf-0.10.0-1.fc16: gvs_tuple_is_normal: Process /usr/libexec/dconf-service was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ghsweepe <ghsweepe> | ||||||||||
| Component: | dconf | Assignee: | Matthias Clasen <mclasen> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 18 | CC: | allison.karlitskaya, awilliam, campbell.bain, hughsient, jreznik, mclasen, rstrode | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i686 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:1fff558aaf3940455337bfe49109b57d7916fa8b | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-01-30 00:40:25 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
ghsweepe
2012-02-13 04:37:28 UTC
Created attachment 561353 [details]
File: smolt_data
Created attachment 561354 [details]
File: backtrace
Created attachment 561355 [details]
File: maps
Created attachment 561356 [details]
File: event_log
Can you explain why this was nominated for common bugs inclusion, and provide more detail about the bug and how to trigger it? I don't recall seeing this one. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers No response to query, so dropping nomination. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping upgraded from fedora 17 while watching a movie recvd a lot of notifications of crashes involving dconf dconf-daemon does not appear to be running I do have an applet that changes the background, may have something to do with it backtrace_rating: 4 Package: dconf-0.14.1-3.fc18 Architecture: x86_64 OS Release: Fedora release 18 (Spherical Cow) So you still hit this one? Have you cloned this bug? If not, just setting version to Fedora 18 would be enough. Thanks. Fixed upstream: http://git.gnome.org/browse/glib/commit/?id=998c6e65cf18aee626b9982347c29b4b09f2c097 could anyone experiencing this bug attach the core file from /var/spool/abrt/ mentioned in the abrt message? glib2-2.34.2-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/glib2-2.34.2-2.fc18 Package glib2-2.34.2-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glib2-2.34.2-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-1104/glib2-2.34.2-2.fc18 then log in and leave karma (feedback). glib2-2.34.2-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |