The force quit applet on the panel freezes everything so I've ditched that but Libre Office is still unresponsive having tried to open a .docx file. I've tried killall -9 in Terminal but it doesn't recognise that. What's the command now? TIA. Bev (Ubuntu 12.04 LTS.)
On 12/12/13 10:28, Bev Nicolson wrote:
The force quit applet on the panel freezes everything so I've ditched that but Libre Office is still unresponsive having tried to open a .docx file. I've tried killall -9 in Terminal but it doesn't recognise that. What's the command now? TIA.
Bev (Ubuntu 12.04 LTS.)
Well, an idea of how to do this in terminal will still be nice while I remind myself never to try opening .docx files, but I've googled some more (chorus of 'you should have done that earlier' - I know, I know) and found System Monitor is a quick-ish way of doing the same thing. Bev.
On 12/12/13 10:39, Bev Nicolson wrote:
On 12/12/13 10:28, Bev Nicolson wrote:
The force quit applet on the panel freezes everything so I've ditched that but Libre Office is still unresponsive having tried to open a .docx file. I've tried killall -9 in Terminal but it doesn't recognise that. What's the command now? TIA.
Bev (Ubuntu 12.04 LTS.)
Well, an idea of how to do this in terminal will still be nice while I remind myself never to try opening .docx files, but I've googled some more (chorus of 'you should have done that earlier' - I know, I know) and found System Monitor is a quick-ish way of doing the same thing.
Never had much joy with Killall myself. I tend to do ps -Af | grep writer which gives something like user 5639 2358 0 11:30 ? 00:00:00 /usr/lib/libreoffice/program/oosplash --writer user 5671 5639 8 11:30 ? 00:00:01 /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5 user 5725 5657 0 11:30 pts/0 00:00:00 grep --color=auto writer The last line is the grep command executing, so ignoring that, you get two processes, #5639 and 5671 I'd then kill them using kill sudo kill 5639 then check to see if the first kill had also killed the second process ps -Af | grep writer returned just something like user 5725 5657 0 11:30 pts/0 00:00:00 grep --color=auto writer but if it hadn't, I'd have used sudo kill 5671 Hope that helps. I personally am quite surprised that Libre Office is hanging opening a .docx file. I don't have a problem. I guess you could try Abiword instead//. Alternatively, you could try, opening a terminal typing libreoffice --writer which will start writer. Open the document in writer. If it hangs, shift focus to the terminal and press ctrl-c. This should kill writer and return to the terminal prompt. If 12.04 hasn't been infected with that awful Unity UI nonsense, and you still have a task bar, you should also be able to right click and then click on "Close" which will shut down misbehaving apps, most of the time, eventually! HTH Steve
On 12 December 2013 11:43, <steve-ALUG@hst.me.uk> wrote:
I personally am quite surprised that Libre Office is hanging opening a .docx file. I don't have a problem.
Ditto, although I don't know which version of LO is shipped with 12.04 (it might be quite old and docx support has improved quite a lot recently). If you're not running a fairly recent version (4.1.3 is the latest, I think), you can update from the LO team's PPA: https://launchpad.net/~libreoffice/+archive/ppa It should just be a question of installing the repository (follow the instructions on that page) then "sudo apt-get update" and "sudo apt-get upgrade" to pull in the latest LO version, although ask for advice first if unsure. Mark -- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) @ 13 Clarke Rd, Milton Keynes, MK1 1LG
On 12/12/13 12:52, Mark Rogers wrote:
On 12 December 2013 11:43, <steve-ALUG@hst.me.uk> wrote:
I personally am quite surprised that Libre Office is hanging opening a .docx file. I don't have a problem. Ditto, although I don't know which version of LO is shipped with 12.04 (it might be quite old and docx support has improved quite a lot recently).
<snip>
I'm using 3.5 which I've just updated to. Ubuntu always seems to be a bit behind on these things but I've never been that confident about updating from anything other than Synaptic as it seems to work better. Bev.
On 12 December 2013 18:03, Bev Nicolson <lumos@gmx.co.uk> wrote:
I'm using 3.5 which I've just updated to. Ubuntu always seems to be a bit behind on these things but I've never been that confident about updating from anything other than Synaptic as it seems to work better.
Updating from a PPA works in the same way (I gave command line examples but Synaptic works the same). It's just a question of adding an extra repository to the list it looks at. Now I would agree that adding random repositories from any source isn't a Good Thing [TM] if you want a stable system, and you shouldn't take the word of someone posting on a mailing list that it's a good idea either. However the LO repository I pointed to is created by the LO team, although it will contain development builds. A better one (also from the LO team) is: https://launchpad.net/~libreoffice/+archive/libreoffice-4-1 .. which holds backported* versions of the 4.1 series of LO for older Ubuntu releases. *Backporting: Taking a version of a package tested and working on a newer version, and making whatever changes are needed (and testing them) to make it run on an older version. -- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) @ 13 Clarke Rd, Milton Keynes, MK1 1LG
On 12-Dec-2013 10:28:21 Bev Nicolson wrote:
The force quit applet on the panel freezes everything so I've ditched that but Libre Office is still unresponsive having tried to open a .docx file. I've tried killall -9 in Terminal but it doesn't recognise that. What's the command now? TIA.
Bev (Ubuntu 12.04 LTS.)
Hi Bev, I't surprising that "it" doesn't recognise the killall command! What happens if, on the terminal, you enter the command which killall ?? You should see /usr/bin/killall or something very similar. If that doesn't come up, then what happens if you use "kill" instead of "killall"? Another issue to take account of is that the name of the program being run, that you want to kill, may not be what you think. Since you are trying to open a docx file, presumably you have launched oowriter (which should be the default for docx). To see what happens, I just launched oowriter from the command line; then ps aux | grep writer gave: ted 25465 0.0 0.1 4164 1516 pts/0 S 10:48 0:00 /bin/sh /usr/lib/openoffice/program/soffice -writer -splash-pipe=5 ted 25479 7.7 5.4 182676 56232 pts/0 Sl 10:48 0:03 /usr/lib/openoffice/program/soffice.bin -writer -splash-pipe=5 so two processes were launched by the command "oowriter". However, I'm no expert on OO itself, so that's probably as far as I can take it! Good luck, Ted. ------------------------------------------------- E-Mail: (Ted Harding) <Ted.Harding@wlandres.net> Date: 12-Dec-2013 Time: 10:53:21 This message was sent by XFMail -------------------------------------------------
participants (4)
-
Bev Nicolson -
Mark Rogers -
steve-ALUG＠hst.me.uk -
Ted.Harding＠wlandres.net