(sorry, I forgot to put this on the list)
Martin Gisser wrote:
>
> Razvan Cristian Oprea wrote:
> >
> > I've just had a most terrifying experience. Trying to open an Ms Excel document
> > with Staroffice 5.0 under KDE (SuSE 6.0), my computer, rock stable before, got
> > frozen. Ms Windows frozen like I mean... The only think he could recognize was
> > the reset button. I thought it was an accident. So after the cold reboot, I
> > tried again with the same document. The same thing happened: a message from
> > Staroffice, telling me that an error has occured and that my documents have
> > been saved. After that, only silence.
> > I rebooted again and this time, using YaST, I have changed susewm and startx
> > led me into fvwm2 (I thought may be KDE could have a bug). On this third time,
> > my computer died before even being able to deliver me an error message.
> >
> > So, the error is reproductible. And it shouldn't froze no matter what. If I
> > would want to open a fish can with Staroffice and it shouldn't freeze my
> > system!!! Staroffice is hence really dangerous considering the type of access
> > he has to my computer's resources! How is it all this possible??
> >
>
> Have you tried to start Staroffice from an xterm?
>
> I had such a problem with Gimp. Since then, when I want to do some special image
> processing, I start Gimp from an xterm. And when this Gimp bug happens, I get
> something like "division by zero, abort [y/n]?" on the xterm. Then I just type n
> and on it goes...
>
> :-)
> Martin
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
