FS#8120 - gtk2.12 makes Firefox crash

Attached to Project: Arch Linux
Opened by spiorf (spiorf) - Tuesday, 25 September 2007, 16:35 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 16 October 2007, 08:18 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan de Groot (JGC)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description: Firefox crashes when starting a download and when opening preferences
This is related to gtk 2.12, because downgrading to 2.10 fixes it. And this happens only with the default theme, or with a theme that draws widgets using gtk. Fully skinned themes are ok.


Additional info:
* package version(s) : firefox 2.0.0.7 and gtk2 2.12.0
* config and/or log files etc.


Steps to reproduce:
Upgrade to gnome 2.20 and to gtk 2.12
open firefox with default theme
start a download or open preferences.

This task depends upon

Closed by  Roman Kyrylych (Romashka)
Tuesday, 16 October 2007, 08:18 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Tuesday, 25 September 2007, 17:07 GMT
What GTK theme engine do you use?
Comment by spiorf (spiorf) - Wednesday, 26 September 2007, 11:07 GMT
Right, it could be that! i use the aurora gtk engine
Comment by PhrAok (PhrAok) - Wednesday, 26 September 2007, 12:38 GMT
i use glory-simplex (pixbuf gtk engine) and i have same bug with firefox but not only, swiftweasel, flock too.
Comment by Jan de Groot (JGC) - Wednesday, 26 September 2007, 13:34 GMT
And if you change your theme engine to something like clearlooks or mist, does it occur there too?
Comment by Benjamin Alldritt (coyote) - Wednesday, 26 September 2007, 15:39 GMT
I'm currently using clearlooks and I am having the same firefox crashes (along with other GTK programs such as Pidgin). Most of the time I am just browsing and it will crash unexpectedly. If left alone after these crashes, x-server may restart or pieces of the kde desktop will crash. I checked on other mail lists and found that these problems are coming from gtk 2.12.
Comment by PhrAok (PhrAok) - Thursday, 27 September 2007, 07:50 GMT
Now for me, if i change for clearlooks = no crashes
Comment by Jan de Groot (JGC) - Friday, 28 September 2007, 09:20 GMT
For those who have crashes, is the Adobe Reader plugin installed?
Comment by Benjamin Alldritt (coyote) - Friday, 28 September 2007, 16:01 GMT
No, Adobe Reader is not installed on my machine. Is there any way to collect data on these programs up until they crash?
Comment by Benjamin Alldritt (coyote) - Wednesday, 03 October 2007, 03:03 GMT
Just as an update, it appears Pidgin is fixed possibly after the last update to 2.2.1.
Firefox still crashes in 2.0.0.7 and the latest nightly. This is also with no Firefox add-ons.
Crashes occur with Print Preview and normal browsing in both.
Comment by (N/A) (wantilles) - Thursday, 04 October 2007, 21:27 GMT
I tried to reproduce any of the above two special cases here (preferences & downloads) and I cannot reproduce the crash.

Also tried to reproduce the bug with preferences in Thunderbird 2.0.0.6 and Sunbird 0.5 (I assume they share a lot of code with Firefox), again with no luck.

Although to be fair, I should note that I am running the "-branded" versions of all three programs from the AUR repository. Their only difference is official-branding enabled.

Pidgin 2.2.1 also seems to run fine.

The above are for X86_64 but may prove helpful.

I haven't tried Gnome 2.20 on i686 yet.
Comment by Yan Brodeur (neodreams) - Friday, 05 October 2007, 17:07 GMT Comment by Benjamin Alldritt (coyote) - Sunday, 07 October 2007, 20:11 GMT
Sorry for bugspam, how do you apply the patch? Does it require simply adding a line to a certain gtk2 pkgbuild?
Comment by Gultyaev Alexey (hokum) - Monday, 15 October 2007, 08:00 GMT
  • Field changed: Percent Complete (100% → 0%)
Patch in gtk 2.12-2 didn't help. After pressing "print" or when jumping out saving file dialog firefox crashes
Comment by Jan de Groot (JGC) - Monday, 15 October 2007, 08:21 GMT
It's a bug in all these mozilla applications. Bugfix is here:

https://bugzilla.mozilla.org/attachment.cgi?id=279879

https://bugzilla.mozilla.org/show_bug.cgi?id=389801

Workaround is to switch to a theme like clearlooks or mist for now.

Loading...