Red Hat Bugzilla – Bug 758240
Crash during linker resolution - NVIDIA proprietary driver
Last modified: 2013-02-14 02:30:42 EST
libreport version: 2.0.7
comment: Wasn't doing anything, and the shell abruptly crashed. Cannot start it with `gnome-shell --replace` later; it says "Segmentation fault (core dumped)". I've had to switch to fallback mode since the shell doesn't load after login.
reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
time: Tue 29 Nov 2011 12:58:34 PM CST
backtrace: Text file, 104000 bytes
build_ids: Text file, 4594 bytes
dso_list: Text file, 9801 bytes
maps: Text file, 21061 bytes
var_log_messages: Text file, 4186 bytes
Created attachment 538062 [details]
Created attachment 538064 [details]
Created attachment 538065 [details]
Created attachment 538066 [details]
Created attachment 538067 [details]
*** Bug 758622 has been marked as a duplicate of this bug. ***
This crash happens before gnome-shell even starts running when the linker is resolving symbols. Both reports are with the NVIDIA proprietary driver, and I assume it's something related to a corrupted install of the driver.
Not sure how this started, but gnome-shell segfaults every time I try to log in.
OS Release: Fedora release 16 (Verne)
Created attachment 568095 [details]
Backtrace analysis of bugs across components suggests the actual bug might be in component glibc instead of component gnome-shell. You might want to inspect the backtraces from the bugs listed below to find out the correct component.
Bugs which were found to be similar to this bug:
amarok: bug #787608
empathy: bug #748229, bug #760127, bug #760144
mesa-demos: bug #770996
totem: bug #754579, bug #759947, bug #760719
This comment is automatically generated.
*** Bug 760719 has been marked as a duplicate of this bug. ***
*** Bug 754579 has been marked as a duplicate of this bug. ***
*** Bug 760127 has been marked as a duplicate of this bug. ***
*** Bug 759947 has been marked as a duplicate of this bug. ***
*** Bug 748229 has been marked as a duplicate of this bug. ***
*** Bug 760144 has been marked as a duplicate of this bug. ***
*** Bug 770996 has been marked as a duplicate of this bug. ***
*** Bug 817445 has been marked as a duplicate of this bug. ***
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:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.