Re: SM 2.0.4 Crash in Ubuntu Linux

2010-05-12 Thread Lou
NoOp wrote: On 05/07/2010 07:54 PM, Lou wrote: NoOp wrote: For some reason Lou's msg got caught in my filters& I didn't see the original. Anyway, it's a known issue and being worked on: https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/575160 [seamonkey 2.0 in Lucid crashes with 'Ren

Re: SM 2.0.4 Crash in Ubuntu Linux

2010-05-07 Thread NoOp
On 05/07/2010 07:54 PM, Lou wrote: > NoOp wrote: >> >> For some reason Lou's msg got caught in my filters& I didn't see the >> original. Anyway, it's a known issue and being worked on: >> >> https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/575160 >> [seamonkey 2.0 in Lucid crashes with 'Re

Re: SM 2.0.4 Crash in Ubuntu Linux

2010-05-07 Thread Lou
NoOp wrote: For some reason Lou's msg got caught in my filters& I didn't see the original. Anyway, it's a known issue and being worked on: https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/575160 [seamonkey 2.0 in Lucid crashes with 'RenderBadPicture' diagnostics] Thanks for the link

Re: SM 2.0.4 Crash in Ubuntu Linux

2010-05-07 Thread NoOp
On 05/07/2010 03:14 AM, Daniel wrote: > Lou wrote: >> I recently installed Kubuntu 10.04 Lucid Lynx and Seamonkey2 from the >> repositories. I'm getting random crashes, with the following error shown >> in the terminal: >> -- >> The program 'seamonkey-2.0-bin' received an X Window Syste

Re: SM 2.0.4 Crash in Ubuntu Linux

2010-05-07 Thread Daniel
Lou wrote: I recently installed Kubuntu 10.04 Lucid Lynx and Seamonkey2 from the repositories. I'm getting random crashes, with the following error shown in the terminal: -- The program 'seamonkey-2.0-bin' received an X Window System error. This probably reflects a bug in the program.

SM 2.0.4 Crash in Ubuntu Linux

2010-05-06 Thread Lou
I recently installed Kubuntu 10.04 Lucid Lynx and Seamonkey2 from the repositories. I'm getting random crashes, with the following error shown in the terminal: -- The program 'seamonkey-2.0-bin' received an X Window System error. This probably reflects a bug in the program. The erro