Ubuntu
seamonkey package

The program 'seamonkey-2.0-bin' received an X Window System error.

Bug #582816 reported by yamo on 2010-05-19

This bug report is a duplicate of: Bug #575160: seamonkey 2.0 crashes with 'RenderBadPicture' diagnostics. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	seamonkey (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: seamonkey

Hi,

After a long time seamonkey 2.0.4 crash with this message :The program
'seamonkey-2.0-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 6196042 error_code 158 request_code 148 minor_code 7)

Tags:

Revision history for this message

yamo (stephane-gregoire) wrote on 2010-05-19:

Sorryr for this short bug report, I had many trouble with timeout errors on launchpad.

$ uname -a
Linux eeepc 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux

$ dpkg -l seamonkey | grep ii
ii seamonkey 2.0.4+nobinonly-0ubuntu1 The Seamonkey Internet Suite

$ cat /proc/version_signature
Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04 LTS
Release: 10.04
Codename: lucid

Revision history for this message

yamo (stephane-gregoire) wrote on 2010-05-19:

back trace created after reading this page : https://wiki.ubuntu.com/Backtrace Edit (67.3 KiB, text/plain)

I've removed the line after the crash, I would marked past attachment as obsolete or removing it..

yamo (stephane-gregoire) on 2010-05-19

tags:

added: lucid

Revision history for this message

Micah Gersten (micahg) wrote on 2010-05-21:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 575160, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.