Firefox freeze under KDE

Bug #48314 reported by Gertjan
18
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
High
Mozilla Bugs
gtk-qt-engine (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox

Running dapper 6.06 LTS with - as far as I can tell, the latest apt-get upgrades. Firefox almost immediately freezes (and has to be killed) although some times it can take longer. There are lots of messages:

(Gecko:5626): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed

(Gecko:5626): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(Gecko:5626): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion `gdk_window_is_viewable (src)' failed

but I ame not convinced they are related. This may well be a Firefox bug, but it is also reported here:

http://kubuntuforums.net/forums/index.php?topic=5283.msg20768#msg20768

which makes me think it's distro related. I would be happy to run some test but I am not sure which direction to go in.

Gertjan

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Does removing .gtkrc-2.0 fix the problem (hint: don't remove it, rename it so that you can restore it later on if it makes no difference ) ? Is this an upgrade from Breezy? If not, did you keep your old /home around? Thanks for reporting this.

Changed in firefox:
status: Unconfirmed → Needs Info
Revision history for this message
Gertjan (gertjan-hofman) wrote :

Hi Vassilis,

The problem seems to have dissapeared with an apt update/upgrade. Unfortunately I don't know which package upgrade (could have been Firefox itself) resolved the issue.

This was a clean install of Dapper. Yes, I kept my old home directory and presumed this was related. I created news users from scratch and for a while was convinced the freezing went away when logged in as those users. That was premature celebration - firefox still froze.

I will check if those other 'users' still freeze Firefox, but if not I have to assume it really did dissapear with an update. Strangely no other users reported this issue.

Cheers

Gertjan

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Sorry for not replying. I have a hunch as to what caused this (namely, your .gtkrc directory) but I'm going to have to close this since you said it has been fixed. Please reopen if it appears again. Thanks for taking the time to report this!

Changed in firefox:
status: Needs Info → Fix Released
Revision history for this message
Maciej Słojewski (mslonik) wrote :

Dear Vassilis & Gertjan,

I hope that at least one of you will read this message.

I can confirm this bug. It is present on my PC running Kubuntu 6.06. At first it was present on the version 1.5.dfsg+1.5.05-0ubuntu6.06.1. The following lines were visible under terminal:

(Gecko:5626): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion `gdk_window_is_viewable (src)' failed

(Gecko:5626): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `pixbuf != NULL' failed

(Gecko:5626): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample: assertion `pixbuf != NULL' failed

(Gecko:5626): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf !=NULL' failed

(Gecko:5626): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed

(Gecko:5626): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed

(Gecko:5626): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (
object)' failed

Plenty of time. Finally memory share error has occured.

Then I decided to update firefox to the latest packet: 1.5dfsg+1.5.0.7-0ubuntu6.06.6. It didn't improve much. Now I can see the following lines:

(Gecko:6299): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion `gdk_window_is_viewable (src)' failed

(Gecko:6299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `pixbuf != NULL' failed

(Gecko:6299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample: assertion `pixbuf != NULL' failed

(Gecko:6299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed

(Gecko:6299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed

(Gecko:6299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed

(Gecko:6299): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

It would be nice if I can help somehow. At the moment I am able to repeat the problem any time. Nevertheless I will look for a solution by doing some updates to other packets. Any help with that will be appreciated.

Kind regards,
Maciej Słojewski

Revision history for this message
Maciej Słojewski (mslonik) wrote :

Dear Vassilis,

Your question was:

"Does removing .gtkrc-2.0 fix the problem (hint: don't remove it, rename it so that you can restore it later on if it makes no difference ) ? Is this an upgrade from Breezy? If not, did you keep your old /home around? Thanks for reporting this."

My answers: Yes, removing .gtkrc-2.0 fix the problem. Is this an upgrade from Breezy? Yes, it is. Yes, I've kept my old /home around.

Kind regards,
Maciej Słojewski

Revision history for this message
Maciej Słojewski (mslonik) wrote :

Dear Vassilis,

After logout and login in KDE problem persists. The file .gtkrc-2.0 was recreated and again I can see in the konsole many gecko errors.

Problem is quite serious as firefox dissapears after visiting some encrypted sites (ssl 2.0).

Any ideas how to skip it?

Kind regards,
Maciej Słojewski

Revision history for this message
Vassilis Pandis (pandisv) wrote :

I'm not sure what the problem is ... does it happen with other GTK+ applications as well? Can you get a backtrace of the firefox crash ? To do this, install 'firefox-dbg' and run 'firefox -debug'. When firefox crashes, type 'bt' and then 'thread apply all bt' and attach the output to the bug report.

Changed in firefox:
importance: Medium → Undecided
status: Fix Released → Unconfirmed
Andrew Ash (ash211)
Changed in firefox:
status: Unconfirmed → Needs Info
Revision history for this message
Maciej Słojewski (mslonik) wrote :

Dear All,

I really don't know what else can I do. I've installed the following packets: 'gdb' and 'firefox-dbg'. Then I've run the following code:

maciej@gucek2:~$ firefox -debug
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) bt
No stack.
(gdb) thread apply all bt

Then I've run firefox at another console and reproduced a bug. Unfortunately nothing was recorded by gdb. I need more assistance. As a newbie I'm not able to deal with gdb well.

Revision history for this message
Maciej Słojewski (mslonik) wrote :

Sorry because of my previous post. When I read a little bit of gdb help I've found solution to my previous questions:

maciej@gucek2:~$ firefox -debug
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/lib/firefox/firefox-bin -a firefox
[Thread debugging using libthread_db enabled]
[New Thread -1220602176 (LWP 6345)]
[New Thread -1222988880 (LWP 6348)]
[New Thread -1243853904 (LWP 6351)]
[New Thread -1262838864 (LWP 6352)]
[New Thread -1274418256 (LWP 6353)]
[New Thread -1282810960 (LWP 6354)]

(...)

Then I was able to reproduce a bug. The gdb code is attached to this message. I hope that it will shed some light on a problem.

What else can I do? How else can I help?

Regards,
Maciej

Revision history for this message
Vassilis Pandis (pandisv) wrote :

I'm going to confirm this bug and raise its importance. There have been several issues related to GTK apps crashing under KDE after upgrading which can be solved by deleting .gtkrc-2.0 . This is could probably not be a firefox problem, so I'm adding a gtk-qt-engine task.

Changed in firefox:
importance: Undecided → High
status: Needs Info → Confirmed
David Farning (dfarning)
Changed in firefox:
assignee: nobody → mozillabugs
Revision history for this message
Alexander Sack (asac) wrote :

So who still sees this and in which version of firefox?

Changed in firefox:
status: Confirmed → Needs Info
Revision history for this message
Maciej Słojewski (mslonik) wrote :

In the meantime I've made massive upgrade of my distro 6.06 LTS -> 6.10. Now I have Firefox ver. 2.0.0.1. The mentioned problem seems to no longer exist.

Kind regards,
Maciej Słojewski

Revision history for this message
Andrew Ash (ash211) wrote :

So can anyone still confirm it?

David Farning (dfarning)
Changed in firefox:
assignee: mozillateam → mozilla-bugs
Revision history for this message
John Vivirito (gnomefreak) wrote :

Closing under firefox due to lack of responses in 30days and have to assume since noone responded its no longer a problem. I am unable to reproduce this in edgy or feisty. If you still see this problem please reopen this bug with more information at hand.

Changed in firefox:
status: Needs Info → Rejected
Revision history for this message
Suzanne Lessack (hippomonke-gmail) wrote :

I'm having the same problem, where Firefox disappears. I'm using Ubuntu Fiesty 7.04 and Firefox 2.0.0.4, and have a fresh install. The error message I receive when running it though a terminal is:

(Gecko:20455): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

I also don't have gtk-qt-engine installed. I'm new to linux, so any help would be greatly appreciated.

Revision history for this message
Ralph Janke (txwikinger) wrote :

Closing under gtk-qt-engine due to 30 day rule. The last comment cannot be gtk-qt-engine related since it is not installed.

Changed in gtk-qt-engine:
status: New → Invalid
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.