Or perhaps the implementation/build in the Ubuntu 2.0 version? Reason for question is that like Wladimir I experience no such crashes when using the standard mozilla SeaMonkey versions (running from a home folder) or the builds from https://launchpad.net/~seamonkey2/+archive/seamonkey2 or even 2.0.5 from https://launchpad.net/~seamonkey2/+archive/seamonkey2-pre
Note: the question is not intended to insult nor state that one build is better than the other. I'm simply stating that I've not experienced the same in the other builds. The key problem is that I can't get any details from such a crash in order to provide useful information for debugging when running the Ubuntu 2.0 version. Further, the crash typically only occurs under heavy daily use (as far as I can tell), so it becomes a catch-22 situation; run, crash, possibly lose valuable work, restart. I'm happy to _try_ to help troubleshoot (I have mirrored ~/.mozilla machines), but without any crash details the best I could possibly report is as provided in comment #4. If you can provide detailed steps on how you'd like me to test I'll be happy to give it a try - the only way that I can thing of is to run SM in gdb mode. That's slow, but may work? Suggestions? -- 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
