Opening severial tabs in firefox (x86-64) and closing them 1 at a time will cause the Xorg server to get a signak 11 and abort. Not every close tab trigers this, but I have severial Xorg logs where it has happened and can recreate it all to often, 6 crahses today. If additional info needed I will try to provide it, I have tried to run ff from the CmdLine redirecting sdtout & errout to a file but the file is empty after crash.
Created attachment 156606 [details] Most current Xorg log following crash
xgl-maint will probably ask you to provide more details.
Created attachment 157153 [details] Copy of Xorg-log from after firefox -> x-server abort.
Anyone looking at this at all??? Opened a month ago and only comment is from FF maintainer. I have applided all updates via yum update through today 2007-07-21 and on the 3rd "close tab" X crashed again. Back to FC6, and FF 1.5.*
Sorry for delay, but currently we have around 500 open bugs just for gecko-related apps, so we are dancing as fast as we can, but it is certainly as you (or we) would like to.
This really is an X bug anyway. I just don't know what to re-assign it to.
Of course, you are right -- we usually go for different drivers, so this is our beloved xorg-x11-driver-nv. Oh well :-(
Should I test with the NVIDA Binary driver to confirm its an NV problem? Is there anything I can do to pin the problem portion of the code down (debug options traces etc)? I have the time, just need direction on what to do.
Sure, you can try it, if it works it could be interesting datapoint, but don't even bother to send us the logs from binary-only nVidia driver -- they are useless to us.
Seems to be reported also in the Novell bugzilla as https://bugzilla.novell.com/show_bug.cgi?id=211314 and somebody mentioned this for Fedora (don't if he has already filed the bug here in the Bugzilla).
And there is the upstream bug for this as well https://bugs.freedesktop.org/show_bug.cgi?id=7205. Novell bug has been actually patched and there five patches attached to the bug (I will reattach them to our bugzilla as well). The comments are very detailed and thoroughfull (all 132 of them).
Created attachment 159984 [details] first upstream patch Actually, there are only two patches in the upstream bug, so I will rather apply these.
Created attachment 159985 [details] second upstream patch
*** This bug has been marked as a duplicate of 220629 ***