[nvidia-glx] nVidia drivers + Firefox + wiki.ubuntu.com = X server crash

[Dario Teixeira]

Binary package hint: nvidia-glx

This bug happens with 100% reproducibility. If the nVidia propreitary drivers are installed, using Firefox to view some pages in the Ubuntu wiki causes the X server to crash. The problem does not happen with the nv driver, so I'm flagging the affected package as nvidia-glx rather than Firefox. Here is an example of a page which always crashes my X server:

https://wiki.ubuntu.com/BerylOnFeisty

[Sense Egbert Hofstede (sense)]

Thank you for your report, but it doesn't contain every piece of information we need to solve the problem. Could you please post this(almost immediately after a crash):
-/var/log/Xorg.0.log
-/etc/X11/xorg.conf
-The output of dmesg(you can use 'dmesg > dmesg.txt' to put it into a textfile)
-The output of 'sudo dmidecode'
-

[Sense Egbert Hofstede (sense)]

I hit the button to early by accident.

...-The output of lspci

[Sense Egbert Hofstede (sense)]

And I forgot also to ask if you're using feisty or edgy(or maybe dapper) and what type of video card you have.

[Dario Teixeira (darioteixeira)]

I am attaching all the info you requested. If there is anything else, please ask!

My nVidia graphics card is a GeForce FX 5500, and I am running Kubuntu Feisty, from a clean install (I think there is a feature missing from Launchpad: one would assume that if a bug is reported from inside "Ubuntu -> Releases -> 7.04", it would automatically be flagged as occurring in Feisty).

Anyway, thanks for your quick response. Feisty has been nothing but trouble so far; Firefox, in particular, worked fine in Edgy, but now refuses to run more than 5 minutes without crashing. And if using the nVidia drivers, it often takes the whole X server with it when it crashes...

Please see also the following bug report: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/108929

[Dario Teixeira (darioteixeira)]

It would be nice if launchpad allowed more than one file to be attached with the same message. It doesn't, at least not with Konqueror... (and I can't use Firefox because of the bug)

[Scott Kitterman (kitterman)]

It doesn't matter what browser you use. It's one file at at time.

[Sitsofe Wheeler (sitsofe)]

Dario:
If your BIOS has an option, does disabling cool 'n quiet make any difference?

[Sitsofe Wheeler (sitsofe)]

Setting to needsinfo pending repoly from Dario.

[Dario Teixeira (darioteixeira)]

My BIOS has no such option.

Note that in the meantime I have reinstalled Edgy (bug 108929 rendered my machine unusable). However, the same problems with nVidia + Firefox also occur in Edgy, so if you need any specific info please ask.

The interim solution to this particular bug was to disable the proprietary nVidia drivers and use plain old "nv". It's slow, but stable.

[Sitsofe Wheeler (sitsofe)]

Dario:
Hmm. Does disabling RenderAccel (as described here: http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-d.html ) make any difference?

[Dario Teixeira (darioteixeira)]

Hi,

I have added the 'Option "RenderAccel" "false"' to the relevant portion of my xorg.conf file, but it didn't make any difference: Firefox still crashes on certain sites, bringing the entire X server down with it.

But again note that this problem only happens with the nVidia proprietary drivers.

[Sitsofe Wheeler (sitsofe)]

Setting back to unconfirmed. Punting from xorg -> linux-restricted-modules-2.6.20 because this only happens with the nvidia binary drivers.

[isaac (ubuntu-brisbanelinux)]

I am getting the same issue.

I can reproduce with Firefox+Nvidia binary drivers, although my kernel version is different.

I am using Ubuntu Edgy.

Linux daru 2.6.17-11-386 #2 Fri May 18 23:37:00 UTC 2007 i686 GNU/Linux

[isaac (ubuntu-brisbanelinux)]

I am also using twinview

[Sitsofe Wheeler (sitsofe)]

issac:
Can you indicate whether this happens with a Gutsy liveCD ( http://cdimage.ubuntu.com/daily-live/current/ ) too?

[wolfger (wolfger)]

Over 5 months without a response. I hate to mark a bug that's been worked on this much as "invalid", but clearly no further progress will be made until a response is received. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!