FS#28441 - The new nvidia driver causes a bug in Gnome-shell
Attached to Project:
Arch Linux
Opened by Nassim K. (blueicefield) - Wednesday, 15 February 2012, 09:07 GMT
Last edited by Ionut Biru (wonder) - Friday, 23 March 2012, 08:22 GMT
Opened by Nassim K. (blueicefield) - Wednesday, 15 February 2012, 09:07 GMT
Last edited by Ionut Biru (wonder) - Friday, 23 March 2012, 08:22 GMT
|
Details
Description:
It's seems that the new nvidia driver causes a bug in Gnome-shell when trying to use the search field in the activities menu. Additional info: * package version(s) : 295.20-1 * Log : Feb 15 09:53:06 localhost kernel: [ 456.887463] gnome-shell[2530]: segfault at 10 ip 00007f969c7b4c0f sp 00007f96712ea6d8 error 6 in libnvidia-tls.so.295.20[7f969c7b4000+3000] Steps to reproduce: - Go to the "Activities" menu - Enter something in the search field. Note : Sorry for my english. |
This task depends upon
Closed by Ionut Biru (wonder)
Friday, 23 March 2012, 08:22 GMT
Reason for closing: Fixed
Additional comments about closing: nvidia 295.33
Friday, 23 March 2012, 08:22 GMT
Reason for closing: Fixed
Additional comments about closing: nvidia 295.33
http://www.nvnews.net/vbulletin/showthread.php?t=174049
-
It seems to be caused by old cache files in ~/.nv/GLCache .. removing or renaming that directory fixes it.
-
For me this solved the problem for a moment but a bit later it reappeared.
So, laptop : geforce 7000M + nvidia 295.20 + gnome shell 3.2 = ok.
Desktop : GT210 + nvidia 295.20 + gnome shell 3.2 = crash.
Only nouveau works pretty quick on my desktop :/
deleteing ~/.nv didnt help
And writing in the search field reloads gnome with some letters, like "o", not all letters.
Architecture: i686
IgnorePkg = nvidia nvidia-utils
Please don't close this ticket until upgraded packages which fix the issue are pushed to the main repos so that those of us watching this bug will be notified that it's time to update. Thanks!
work: NVIDIA GT218 [Quadro NVS 300] + latest gnome 3 WORKS
home: NVIDIA 8800GT + latest gnome 3 is CRASHING
The workaround was to downgrade to 290.10-3 and ignore nvidia updates.
Downgrading to 290.10-3 is no longer possible with the just released kernel 2.6.8 (unless you downgrade to the previous kernel, I guess):
[ 560.243808] nvidia: disagrees about version of symbol module_layout
[ 564.246530] nvidia: disagrees about version of symbol module_layout
[ 587.550190] nvidia: disagrees about version of symbol module_layout
Forced to use 295.20-2 which exhibits an X crash bug.
This is really broken, and regardless of an "upstream bug" this probably shouldn't be closed as it is affecting multiple facets of Arch (e.g. gnome-shell and xbmc and being unable to properly run the current kernel with this driver).
The problematic file seems to be ~/.local/share/recently-used.xbel. Deleting this file fixes the issue for a while, but later it appears again. The solution is to empty the file (echo > ~/.local/share/recently-used.xbel) and lock it with chattr (sudo chattr +i ~/.local/share/recently-used.xbel). It's probably a good idea to back it up first.
Update: 295.20-3 doesn't seem to fix the issue for me.
Making the file immutable is a workaround for this specific bug, any threaded usage of OpenGL will trigger the bug, this is not gnome-shell specific.
Things are moving a little upstream.
http://www.nvnews.net/vbulletin/showpost.php?p=2532350&postcount=8
"NVIDIA internally filed bug 941836 to track this issue."
Looks like it is related to a crash on fork call.
http://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/nvidia&id=54fa181fb4d549d1ebf8ab2db554d20c8736224f
Meanwhile, the workaround presented by @vladev seems to work just fine.
Edit: Spoke too soon, subsequent testing shows I can still produce a crash by playing a movie twice (crashes on stop). I might lodge another bug regarding this as it's not strictly the same issue.
if i set locale to de_DE@euro (iso8859-15) gnome-shell crashed at startup. dmesg shows "[ 373.697042] gnome-shell[1624]: segfault at c ip b539cea3 sp b2590b8c error 6 in libnvidia-tls.so.295.20[b539c000+3000]"
the error occurs with 295.20-2 as well as 295.20-3. setting locale to utf8 works fine.
same bug?