FS#19005 - [seamonkey] crashes with RenderBadPicture X error
Attached to Project:
Arch Linux
Opened by Michal Svoboda (pht) - Friday, 09 April 2010, 05:10 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 28 September 2010, 14:58 GMT
Opened by Michal Svoboda (pht) - Friday, 09 April 2010, 05:10 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 28 September 2010, 14:58 GMT
|
Details
Since some pacman -Syu a couple of weeks ago seamonkey would
start crashing at purely random times while browsing with
the pesky RenderBadPicture X error. I've tracked this issue
down to an incompatible version of the 'cairo' library.
Seamonkey (and mozilla in general) ships with its own (stable, tested, holy, etc) version of cairo. You can switch between the bundled and system version with the --enable-system-cairo (or so) in mozconfig. I've found out that removal of this parameter and thus usage of the internal cairo library fixes the issue. So please change the mozconfig in the package build source in this manner. Alternatively, if you wish, pursue the issue and fix the system cairo (the one that's installed with pacman). |
This task depends upon
Closed by Jan de Groot (JGC)
Tuesday, 28 September 2010, 14:58 GMT
Reason for closing: Fixed
Additional comments about closing: 2.0.8-2 builds with internal cairo.
Tuesday, 28 September 2010, 14:58 GMT
Reason for closing: Fixed
Additional comments about closing: 2.0.8-2 builds with internal cairo.
1) fetch seamonkey from abs
2) edit the mozconfig and remove the --enable-system-cairo line
3) makepkg, go get a coffee
4) install the created package with pacman
The work around still works but the latest update of seamonkey still has the problem. It does appear to be the system cairo being out of date vs the new Seamonkey(s) expecting to use their up to date cairo 1.9.10??? & for a while both our i686 cairo 1.8.10-1 & x86_64 cairo 1.8.10-1 were showing as out of date (no bug report allowed??) In the last few days the out of date status has now gone away again & I can't see anything in testing repo?. Seems till cairo is updated or Seamonkey's mozconfig file is amended it will need recompiling each update.
FYI back then when I was researching the problem I spoke with seamonkey people (on IRC) and they specifically told me that using any version of cairo but theirs is "unsupported and at your own risk".
Please tell me if you wanna heed their advice or continue shipping broken software for whatever (purity?) reasons.
(1/1) upgrading seamonkey [###################] 100%
$ sudo pacman -Q seamonkey
seamonkey 2.0.6-1
$ /usr/bin/seamonkey
The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 1508862 error_code 158 request_code 148 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.)
I'll continue to use the arch build & report any further crashes
$ /usr/bin/seamonkey --sync
The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 4347541 error_code 158 request_code 148 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.)
$ /usr/bin/seamonkey --sync
A constantly crashing browser in the name of principle is silly.
Thanks so much!! I've upgraded & included your new cairo from testing. I'll make sure I report any probs. with seamonkey. This is a classic example of "The Wisdom of Crowds" (James Surowiecki) & a pleasure to watch. Thanks again to all.
I'm so sorry & I truly appreciate all that everyone has done to try to resolve this:-( So below is the lastest: the error msg is often there just after some usage, but seamonkey hasn't actually crashed.
On other occasions (like paste below) seamonkey "actually" crashes.
The recompiled one, leaving out the system cairo?? I haven't been able to generate the error msg nor crash it......... yet:-)??
Thanks again.
[............]$ sudo pacman -Q cairo seamonkey
cairo 1.10.0-1
seamonkey 2.0.7-1
[............]$ seamonkey
The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 1864944 error_code 158 request_code 148 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.)
[............]$
Just updated again & ............. apologies to all.The testing cairo still doesn't seem to help??
[ ~]$ sudo pacman -Q cairo seamonkey
cairo 1.10.0-1
seamonkey 2.0.8-1
[ ~]$ seamonkey
The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 2659224 error_code 158 request_code 148 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.)
[ ~]$