@Marcelo Toscani Brandão Do you have a test case we can use to reproduce the crash?
On 07/17/2010 06:41 PM, Marcelo Toscani Brandão wrote: > In fact, it seems a lot worse now. > Crashing more often. > > > (seamonkey-2.0-bin:24634): Gdk-WARNING **: XID collision, trouble ahead (this > message repeats hundred of times) > > (seamonkey-2.0-bin:24634): Gdk-WARNING **: XID collision, trouble ahead > > (seamonkey-2.0-bin:24634): Gdk-WARNING **: XID collision, trouble ahead > > (seamonkey-2.0-bin:24634): Gdk-WARNING **: XID collision, trouble ahead > deliver mode: 0 > 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 983073 error_code 172 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.) > > -- seamonkey 2.0 in Lucid crashes with 'RenderBadPicture' diagnostics https://bugs.launchpad.net/bugs/575160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
