Firefox 3 b5 crashes xorg when loading ubuntuguide.org in ubuntu 8.04 with compiz enabled

Bug #222277 reported by kcufdnim
10
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Hardy by tam
linux-restricted-modules-2.6.24 (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Hardy by tam
xorg (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Hardy by tam

Bug Description

Binary package hint: firefox-3.0

Visiting the following site on 2 consecutive occasions caused Firefox to crash and I was logged out of my x session
http://ubuntuguide.org/

This bug seems to affect nvidia 8xxx series cards and only occurs when nvidia-glx-new drivers are enabled with compiz. A temporary fix is posted which suggested updating the libwfb.so library with a newer one provided from nvidia. The bug is most likely a product of firefox's gecko engine and compositing. This bug will also occur in swiftfox or any derivative of firefox.

Environment: Ubuntu 8.04 LTS 32/64 bit
Firefox version: 3 b5
Firefox Installed plugins: Adobe flash player

ProblemType: Bug
Architecture: i386
Date: Sat Apr 26 11:57:38 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
Package: firefox-3.0 3.0~b5+nobinonly-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-16-generic i686

Revision history for this message
kcufdnim (dmcarlier) wrote :
Revision history for this message
Linux Is Pure Pwnage (nospam5555) wrote :

I visited the web page and received no problems. You are running an i686 but I am running an i386 so I am guessing that has something to do with it maybe. You are using a 32 bit. I am using an x86 machine. Might help the developers out. ;)

Revision history for this message
kRYPT (krypt) wrote :

I can confirm this bug. Loading that webpage in FireFox causes X to crash.

My architecture is x86_64.

Also using nvidia non-free module, same version of firefox.

Upgraded from Gutsy (which was also upgraded from the version before).

Revision history for this message
danc (danc) wrote :

I can confirm that I have the same issue, I am using the Linux 2.6.24-16-generic i386 version of Ubuntu 8.04

So far only happens on
http://ubuntuguide.org/wiki/Ubuntu:Feisty

Revision history for this message
kRYPT (krypt) wrote :

Here is dmesg output from the first time I attempted to view the above page using ff3b5 on 8.10:

[89686.865040] Xorg[7943]: segfault at ff01e59dff rip 7f9d1f75c6f3 rsp 7fff2ba3d760 error 4
[89686.955612] compiz.real[8176] trap stack segment rip:40fee0 rsp:7fff6cf97e60 error:0

and then I tried to do it again:

[89796.820596] Xorg[15415]: segfault at ff0080f627 rip 7f363ed8015b rsp 7fff4afd6d80 error 4
[89796.861793] compiz.real[15653] trap stack segment rip:40fee0 rsp:7fff6794d7e0 error:0

(arch: x86_64 2.6.24-16-generic)

Revision history for this message
tam (aznoohwee85) wrote :

I can also confirm this bug.

--Workaround

Disable desktop effects, but seems related to Compiz and nvidia-glx-new.

Revision history for this message
tam (aznoohwee85) wrote :

Completed a GDM backtrack and have isolated the crash to a glx function call, namely wfbRasterizeTrapezoid().

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fdabb07f6e0 (LWP 7784)]
0x00007fdab68446cb in wfbRasterizeTrapezoid () from /usr/lib/xorg/modules//libwfb.so

(gdb) backtrace full
#0 0x00007fdab68446cb in wfbRasterizeTrapezoid () from /usr/lib/xorg/modules//libwfb.so
No symbol table info available.
#1 0x00007fdab704b38f in _nv000745X () from /usr/lib/xorg/modules/drivers//nvidia_drv.so
No symbol table info available.
#2 0x000000000050f411 in miTrapezoids ()
No symbol table info available.
#3 0x00007fdab704af34 in _nv000731X () from /usr/lib/xorg/modules/drivers//nvidia_drv.so
No symbol table info available.
#4 0x0000000000518384 in ?? ()
No symbol table info available.
#5 0x000000000044eaaf in Dispatch ()
No symbol table info available.
#6 0x0000000000436b9d in main ()
No symbol table info available.

tam (aznoohwee85)
Changed in firefox-3.0:
status: New → Confirmed
Revision history for this message
tam (aznoohwee85) wrote : Re: Firefox 3 beta 5 crashes gdm when loading a specific web page in ubuntu 8.04 with compiz enabled

I have solved the problem from Nick B.'s suggesting to a related problem in Firefox 3 in this thread.

https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/212648

It also references this thread which provides an updated libwfb from nvidia which resolves this issue.

http://www.nvnews.net/vbulletin/showthread.php?t=112098

To temporily fix the problem download the updated libwfb and then copy it over to your /usr/lib/xorg/modules directory, and then create a new symbolic link to libwfb.

$ wget http://people.freedesktop.org/~aplattner/wfb/Linux-x86_64/libnvidia-wfb.so.173.08
$ mv libnvidia-wfb.so.173.08 /usr/lib/xorg/modules/
$ sudo ln -sf /usr/lib/xorg/modules/libnvidia-wfb.so.173.08 /usr/lib/xorg/modules/libwfb.so

Restart xorg and everything should function normally. Enjoy!

Revision history for this message
kRYPT (krypt) wrote :

Temporary fix above worked for me (x86_64). Page now loads without issue.

Revision history for this message
kRYPT (krypt) wrote :

I take that back. It only appears to fix it.

I visited the page no problem, but the next application I launched (KLibido) caused the same type of crash (Xorg dies, gdm restarts), although oddly enough it left nothing in dmesg..

Revision history for this message
tam (aznoohwee85) wrote :

I am unable to replicate the bug using klibido, perhaps its a different problem with the nvidia drivers. Try running a backtrace and see if the same library is causing the problem.

https://wiki.ubuntu.com/X/Backtracing

tam (aznoohwee85)
Changed in xorg:
status: New → Confirmed
tam (aznoohwee85)
description: updated
Revision history for this message
kRYPT (krypt) wrote :

Very strange, now I can't replicate it either and everything seems fine (even after visiting a bunch of sites that people have seen trigger this bug).

I'll report back if I see it again (hopefully with a stack trace, thanks for the pointer).

tam (aznoohwee85)
Changed in linux-restricted-modules-2.6.24:
status: New → Confirmed
Revision history for this message
Bob (loosen) wrote :

I have the same problem when launching klibido, it seems to happen when I log in for the first time, start firefox, go to a website and then launch klibido.

Revision history for this message
Nikola Borisof (nikola-borisof) wrote :

The fix suggested by tam broke my X. I had to reinstall nvidia drivers....

Revision history for this message
tam (aznoohwee85) wrote :

Nikola, make sure you have actually downloaded the file. Its possible that you had an incomplete download, or even were running a different version of the restricted drivers. This fix again only applies to the nvidia-glx-new drivers.

In the future you can always drop back to the X terminal (ctrl+alt+f1) and then link back the original library.

$ sudo ln -sf /usr/lib/xorg/modules/libnvidia-wfb.so.169.12 /usr/lib/xorg/modules/libwfb.so

instead of libnvidia-wfb.so.173.08

And your X should function as normal without having to reinstall the nvidia drivers.

Revision history for this message
Nikola Borisof (nikola-borisof) wrote :

Tam,

I think the library downloaded ok.

nikola@nikola-laptop:/usr/lib/xorg/modules$ ls -l *nvidia*
-rw-r--r-- 1 root root 275292 2008-04-10 18:11 libnvidia-wfb.so.169.12
-rw-r--r-- 1 nikola nikola 284560 2008-04-25 20:53 libnvidia-wfb.so.173.08
nikola@nikola-laptop:/usr/lib/xorg/modules$

I do use nvidia-glx-new 169.12+2.6.24.12-1

If you have any suggestion or you want any log files just let me know.

Revision history for this message
tam (aznoohwee85) wrote :

Ah I believe I see your problem, the file is owned by your local user instead of by root. Try this

$ sudo chown root /usr/lib/xorg/modules/libnvidia-wfb.so.173.08

and then recreate the symbolic link using sudo and let me know if it works.

Revision history for this message
Nikola Borisof (nikola-borisof) wrote :

No...

I tried this it doesn't fly...

I found this in the syslog:

May 1 20:49:34 nikola-laptop gdm[6877]: CRITICAL: gdm_config_value_get_bool: assertion `value->type == GDM_CONFIG_VALUE_BOOL' failed

Hope this helps. Let me know what else info to provide.

Revision history for this message
John Vivirito (gnomefreak) wrote : [Bug 222277] Re: Firefox 3 b5 crashes xorg when loading ubuntuguide.org in ubuntu 8.04 with compiz enabled

>
> Nikola Borisof wrote:
>
> > No...
> >
> > I tried this it doesn't fly...
> >
> > I found this in the syslog:
> >
> > May 1 20:49:34 nikola-laptop gdm[6877]: CRITICAL:
> > gdm_config_value_get_bool: assertion `value->type ==
> > GDM_CONFIG_VALUE_BOOL' failed
> >
> > Hope this helps. Let me know what else info to provide.
> >

Please follow the instructions at https://wiki.ubuntu.com/MozillaTeam/Bugs
 to obtain a backtrace of your crash, only one person did it and it
didnt tell us much of anything we have the new instructions up for
firefox-3.0 if you are not the original report please file a seperate
bug and include backtrace. We are only able to use one backtrace/crash
per bug as it gets too confusing due to a number of different reasons
can cause simular crash. Just because its the same site that is crashing
doesnt mean that you are suffering from same issues.

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

Revision history for this message
nanjil (kumarchi) wrote :

I have the same bug. (i386 / nvidia 8600 gt card) . This was a new computer build and I initially though it either it was memory aor the ubuntu release is unstable.

is there any work around? like e.g if it is due to compiz how i can remove it? I have no desk top effects and still it crashes when i visit ubuntuguide.org (strange!!) . when i had desktop efects it was wildly crashing

Revision history for this message
John Vivirito (gnomefreak) wrote :

nanjil no at this moment ther eis not a work around but the problem is with the 8xxx series cards i had one of our X guys take a look and test it for me he was on a 8600 nvidia using th -glx-new drivers. This either a driver issue or a module issue from kernel. Im pretty positive its not a module issue because you saw this on both kernels in hardy since release time. Im going to leave this in his hands but i will ping him monday if its not on holiday.
Subscribing tjaalton to bug report for further triage.
Can you please try this with epiphany and some none xulrunner-1.9 browsers its still possible that xulrunner is causing an issue with drivers but main fault is still drivers as they should beable to handle the usage from the 8xxx cards and it fails to do so from what i can tell!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.