[Regression] 295.17 / 295.20 segfault when searching in gnome3

[rapsure]

I too am experiencing this problem on a Geforce 7600GT but not on my Geforce 9600GT. I sure hope this issue gets resolved promptly. I'll generate a dump when I have time.

[Dragoran]

Originally Posted by Bevan

For me removing the ~/.nv folder solved the problem only for a short moment. A bit later it reappeared

OK, now it happened again for me too.

I have disabled the DiskCache completely and removed ~/.nv ... for now it works lets see for how long.

[Dragoran]

Originally Posted by Dragoran

OK, now it happened again for me too.

I have disabled the DiskCache completely and removed ~/.nv ... for now it works lets see for how long.

Happening again ... so not sure what is causing this.

[dudez]

Originally Posted by rapsure

I too am experiencing this problem on a Geforce 7600GT but not on my Geforce 9600GT. I sure hope this issue gets resolved promptly. I'll generate a dump when I have time.

My other machine that wasn't crashing with 295.20 has a Geforce 9600GT as well, but it started crashing moments ago, so just wondering what could it be..

[GerBra]

Hi, i've had a similar problem with old $HOME/.nv Files. Here Firefox doesn't start anymore, it only show the windowmanager frames. Cause my $HOME is NFS-based and other things were upgraded before this error, i need a lot of time to come to the nvidia driver as the reason.
.nv here wasn't created during WM+nvidia start, this Dir is created on my setup first from FF start (maybe OpenGL rendering...)

IMHO nvidia linux devs should move the .nv directory to $HOME/.cache. This could be a faster solution to similar problems. I use Archlinux as distro and on our bbs I always advise users with so like "Voodoo" problems
a) create a new user
b) if the problem disappears with the new user the reason is mostlikely in $HOME of the old user. So next advise is to clear/move all caches...

But when programs violate <g> in user's $HOME and scatter their files mostly direct under $HOME in (own) hidden dirs this cache clearing is often useless...

[Dragoran]

The problem here has nothing to do with NFS based homedirs neither with the location of the cache.

[sandipt]

I am trying to reproduce this issue but no luck. You all are using fresh installed distro OR applied new updates for gnome3/gnome-shell ? Who all reporting this issue please attach logs by running nvidia-bug-report.sh as root user.

[Dragoran]

Originally Posted by sandipt

I am trying to reproduce this issue but no luck. You all are using fresh installed distro OR applied new updates for gnome3/gnome-shell ? Who all reporting this issue please attach logs by running nvidia-bug-report.sh as root user.

No i am using an up2date F16 x86_64 setup i.e:

gnome-shell-3.2.2.1-1.fc16.x86_64
mutter-3.2.2-1.fc16.x86_64
cogl-1.8.2-2.fc16.x86_64
clutter-1.8.4-1.fc16.x86_64

Bug report is attached the to first post.

[enigmatichus]

Originally Posted by sandipt

I am trying to reproduce this issue but no luck. You all are using fresh installed distro OR applied new updates for gnome3/gnome-shell ? Who all reporting this issue please attach logs by running nvidia-bug-report.sh as root user.

I'm using an up to date Arch Linux i686 setup with 3.2.6-2-ARCH kernel and following packages:
gnome-shell 3.2.2.1-1
mutter 3.2.2-2
xorg-server 1.11.4-1 (xorg)
clutter 1.8.4-1
cogl 1.8.2-1
nvidia 295.20-1
nvidia-utils 295.20-1
For me bug occurs when searching in overview mode for specific pattern, for instance gnome-shell crashes whenever I start the search typing a "b" but not an "a".

[powered_by_tux]

Experiencing the same problem using 295.20 with a GeForce 9600 GT on Arch Linux x86_64.

When it does occur, it helps to delete the history of recently opened documents. Also, if you happen to have this gnome-shell extension installed and a crash occurs, you may have trouble logging in again. In this case, switch to a tty, login with your regular user account and run the following command to manually delete the history... or you disable this extension and delete the respective file.

echo "" > ~/.local/share/recently-used.xbel

Installed software:

linux 3.2.6
gnome-shell 3.2.2.1
mutter 3.2.2
cogl 1.8.2
clutter 1.8.4

Attached a log created with nvidia-bug-report.sh as root-user.

[dudez]

ArchLinux/64, up-to-date with all latest updates, linux-3.2.6-2-ARCH, package versions:

Name : gnome-shell
Version : 3.2.2.1-1

Name : mutter
Version : 3.2.2-2

Name : xorg-server
Version : 1.11.4-1

Name : nvidia
Version : 295.20-1

Name : nvidia-utils
Version : 295.20-1

nvidia-bug-report.log.gz

[uau]

Originally Posted by Dragoran

I tried to get a decent backtrace but it seems to work fine when running inside gdb.

Start the program first, then attach gdb to the running process. Looks like the the crash happens when the process forks, probably in a pthread_atfork() handler registered by the nvidia driver.