[current] Firefox segfualt after exit

grissiom · 03-31-2009, 05:42 AM

Hi all,

I know my question maybe hard to resolve but I seek some hints here. I'm in current, all things up to date. When I quit Firefox, I got a segfault in dmesg:

Code:

firefox-bin[5348]: segfault at a4 ip b6e64e37 sp bfde5770 error 4 in libgdk-x11-2.0.so.0.1400.7[b6e14000+86000]

I reinstalled Fx and gtk+ but with no luck to survive this annoying message. More strange, Fx don't know the segfualt as it start up as usual the next time without asking to restore the previous session. How can I resolve it?

Any hints is welcome

niels.horn · 03-31-2009, 11:14 AM

Have you tried creating a new profile in Firefox?
In the past I have seen issues with corrupted profiles and the solution was creating a new one.

grissiom · 04-01-2009, 10:07 AM

Unfortunately, firefox still segfualts after I remove ~/.mozilla

manwichmakesameal · 04-02-2009, 12:56 PM

That error looks like it's more a problem with X than with Firefox. Do you have any problems with other gtk apps? Have you tried an older version of gtk?

Ilgar · 04-02-2009, 01:06 PM

If you're using some proprietary video drivers like Nvidia's I'd suggest reinstalling them.

grissiom · 04-02-2009, 07:16 PM

Hmm, at least gimp works fine on my box. I don't use proprietary driver. I will launch Fx in a terminal to see what it spiting out...

grissiom · 04-02-2009, 10:50 PM

Hmm, I got the error msg:

Code:

~$ firefox

(firefox-bin:18815): Gdk-CRITICAL **: gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)' failed
/usr/lib/firefox-3.0.8/run-mozilla.sh: line 131: 18815 segfault               "$prog" ${1+"$@"}

It seems that the segfault is only triggered after Fx have run a reasonable long time. If I close the window at once it start up, there is no segfault.

manwichmakesameal · 04-03-2009, 09:43 AM

I noticed that gtk is gtk+2-2.14.7-i486-1 in current, and gtk+2-2.12.12-i486-1 in 12.2. Have you tried reverting to the one for 12.2 and see if you still have the problem?

grissiom · 04-03-2009, 08:53 PM

No, downgrading gtk+ doesn't help...