Bug 831666
Summary: | [abrt] gnome-settings-daemon-3.4.2-1.fc17: config_set_large_print: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | costi | ||||||||||||
Component: | gnome-settings-daemon | Assignee: | Bastien Nocera <bnocera> | ||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 17 | CC: | bnocera, javlopez22, masao-takahashi, mclasen, mkasik, rstrode, yasmin.rmz | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | x86_64 | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | abrt_hash:8c495770f0df6dc69465bc0c59cf9bc00c312ab2 | ||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2013-07-31 20:44:02 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
costi
2012-06-13 14:36:00 UTC
Created attachment 591524 [details]
File: backtrace
Created attachment 591525 [details]
File: maps
Created attachment 591526 [details]
File: dso_list
Created attachment 591527 [details]
File: build_ids
Created attachment 591528 [details]
File: var_log_messages
I have encountered this problem after upgrading to f17. There are many SEGFAULT's in the next packages. gnome-settings-daemon gnome-panel udisks2 shutdown ---> raise kernel panic colord gnome-shell like this segfault ............ error 4 in glibc-2.15.xxxxxxxxxx Isn't it? Now I have solved the problem as follows. 1. upgrade gcc-4.7.0-5.fc17.i686 to gcc-4.7.0-7.fc17.i686 2. regenerate glibc-2.15-46.fc17.i686 and install it. 3. regenerate glib2-2.32.3-1.fc17.i686 and install it. 4. regenerate above packages. Then, segfault's are disappeared. Perhaps gcc-4.7.0-5 has serious problems, I think. Fix filed here: https://bugzilla.gnome.org/show_bug.cgi?id=678133 This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |