firefox with gtk-qt-engine dies mentioning RenderBadPicture and a failed assertion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox-3.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
gtk-qt-engine (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: firefox
firefox is extremely unstable on my intrepid at the moment. It dies repeatedly without any discernible common cause. When started from the command line, the error messages look like this:
QPixmap: Invalid pixmap parameters
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 3484417 error_code 176 request_code 152 minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Locking assertion failure. Backtrace:
#0 /usr/lib/
#1 /usr/lib/
#2 /usr/lib/
#3 /usr/lib/
#4 /usr/lib/
#5 /usr/lib/
#6 /usr/lib/
#7 /usr/lib/
#8 /usr/lib/
#9 /usr/lib/
#10 /usr/lib/
#11 /usr/lib/
#12 /usr/lib/
#13 /usr/lib/
#14 /usr/lib/
#15 /usr/lib/
#16 /usr/lib/
#17 /usr/lib/
#18 /lib/tls/
#19 /usr/lib/
I wonder whether this might be related to gtk-qt-engine. Reasons for this:
My firefox worked all right on hardy with KDE 3.5. http:// ubuntuforums. org/showthread. php?p=5739519 however mentions the issue on hardy with KDE 4.1. So KDE 4.1 might be somehow involved.
The backtrace mentions quite a lot of QT 4 methods.
My firefox had general problems with widgets; the tabs lost their frames after a mouse over highlight, the scrollbars would occasionally display only half a knob, and after scrolling I had a high chance of widgets within the page getting rendered with no border. All of this went away when I changed my GTK engine.
I've changed my GTK engine to Raleigh, and so far things seem to work. The problem is that with seemingly random failures, you can never be sure that the issue is really resolved.