Bug 803589
| Summary: | [abrt] control-center-3.3.91-1.fc17: _cogl_renderer_free: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michele Baldessari <michele> | ||||||||||||
| Component: | control-center | Assignee: | Control Center Maintainer <control-center-maint> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 17 | CC: | control-center-maint, dieter.kasper, mads, mkasik, rstrode, Stephsother, thomas.citharet | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:48fc1d4e4d77dbd5bdec2a44f41a6c3dd6d61c4a | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2013-07-31 22:16:21 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
Michele Baldessari
2012-03-15 07:22:31 UTC
Created attachment 570196 [details]
File: dso_list
Created attachment 570197 [details]
File: build_ids
Created attachment 570198 [details]
File: smolt_data
Created attachment 570199 [details]
File: maps
Created attachment 570200 [details]
File: backtrace
Backtrace analysis of bugs across components suggests the actual bug might be in component glib2 or clutter, or some other component, instead of component control-center. You might want to inspect the backtrace from the bug listed below to find out the correct component. Bug #803606 from component totem was found to be similar to this bug. This comment is automatically generated. *** Bug 803606 has been marked as a duplicate of this bug. *** right click on sound icon and click on sound preferences backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) It crashed when I tried to open the System Settings. backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) attempted to run gnome configuration backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Tried to install nvidia drivers that failed. I later did a system software update and the control panel now fails to open. backtrace_rating: 3 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I launch Totem Movie Player and immediately get this error. Totem never goes further. I had deleted Totem and Totem-Nautilus, rebooted the laptop and re-installed Totem and Totem-Nautilus. Same results. backtrace_rating: 4 Package: totem-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I click on "System Settings" backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I have seen this when mesa-dri-drivers wasn't installed. Please test if you see correlation between the problem and installing/uninstalling mesa-dri-drivers. This could be related to this bug: https://bugzilla.gnome.org/show_bug.cgi?id=686160. - change X11 config from nvidia to nouveau - reboot - login as user - start 'system-setiing' ==>> crash backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) The problem occured after I've followed the bumblebee installation instructions on https://fedoraproject.org/wiki/Bumblebee and the NVIDIA Optimus installation instruction http://fedoralync.blogspot.fr/2012/07/switching-graphic-card-between-nvidia.html backtrace_rating: 4 Package: control-center-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) idk, sorry backtrace_rating: 4 cmdline: totem '/run/media/stephanie/C_Win/Users/Stephanie/My Documents/My Audio & Sound/sound files/andywhsl.wav' crash_function: _cogl_renderer_free executable: /usr/bin/totem kernel: 3.8.12-100.fc17.x86_64 package: totem-3.4.3-1.fc17 reason: Process /usr/bin/totem was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 ureports_counter: 1 xsession_errors: 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. |