Programs on Linux do crash occasionally (just like any other OS).
Luckily they very rarely take the whole system with them though (unlike
some other OSes).
I've seen OOo get into some odd states occasionally. Usually when this
happens, I open a terminal session if the GUI isn't frozen, or hit
CTRL-ALT-F1 to get to a basic console (hit ALT-F7 to get back to the
GUI). From there I run "ps -aux" and look for anything related to OOo.
Sometimes I'll see more than one session of "soffice" running, which
is usually an indicator there's trouble somewhere. Then I run "sudo
kill XXXX" where the XXXX is the PID of the soffice instances. If that
doesn't do the trick, then "sudo kill -9 XXXX" almost always does.
I have seen fewer issues since Java was better supported under 64bit
though. But that might just be coincidence.
Shawn
Richard Carter wrote:
Hi Mark,
Thanks for your reply. Yes, as far as I could tell, the whole of the
application was locked up. Thanks for the tip on "kill -9" : I'll try
to remember it for next time.
Robin
On Wed, Jan 7, 2009 at 3:37 PM, Mark Carlson <[email protected]
<mailto:[email protected]>> wrote:
On 1/7/09, Richard Carter <[email protected]
<mailto:[email protected]>> wrote:
> HI Folks,
>
> I just installed openoffice 2.0 on my system (debian 4.0, amd64)
kpackage.
> But when I open openoffice writer it wouldn't close in spite of:
clicking
> the close button on the top left corner of the window; clicking
on close in
> the drop-down menu; pressing alt-f4; shutting down and restarting the
> computer. I eventually got it closed using the "X Kill Window
Termination
> Tool". I then purged openoffice.
>
> The take-home message is ---- don't use openoffice 2.0 with
debian 4.0 and
> amd64.
>
> Robin
That's too bad. I noticed a similar but opposite problem with MS Word
2007. If you double-click the menu in the top-left, the program
crashed without saving any changes :-(. Unfortunately it was often a
double-whammy if you are trying to do a "save as..." and accidently
double-click!
Was the entire OpenOffice Writer application unresponsive when you
were trying to close it? Usually a "kill -9" will kill the
application, unless the application is stuck in the kernel (shows up
as in "D" state when doing a "ps -ax".
-Mark C.
_______________________________________________
clug-talk mailing list
[email protected] <mailto:[email protected]>
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
------------------------------------------------------------------------
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
