F25 LibreOffice hung

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

F25 LibreOffice hung

Robert Moskowitz
I had an Office Base database open for a few days (and a couple system
suspends), along with lots of spreadsheets and docs.  Went to close Base
and save the database and now none of the LibreOffice docs are responding.

I thought I found the soffice.bin running and killed it, but it still
seems to be running and I can't see if there is any other related process.

How can I find the process and kill it?  I really don't want to boot...

thanks
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

Samuel Sieb
On 06/14/2017 07:45 PM, Robert Moskowitz wrote:
> I had an Office Base database open for a few days (and a couple system
> suspends), along with lots of spreadsheets and docs.  Went to close Base
> and save the database and now none of the LibreOffice docs are responding.
>
> I thought I found the soffice.bin running and killed it, but it still
> seems to be running and I can't see if there is any other related process.
>
> How can I find the process and kill it?  I really don't want to boot...

That should be the one.  Is it really dead?  Why do you think it's still
running?
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

stan
In reply to this post by Robert Moskowitz
On Wed, 14 Jun 2017 22:45:02 -0400
Robert Moskowitz <[hidden email]> wrote:

> How can I find the process and kill it?  I really don't want to
> boot...

You can find all processes you are running by
ps alx | grep -i [your user name]
I think you should be able to do the same thing with top or one of the
other process viewers by filtering.  It might be that the process is in
an uninterruptable sleep.  I don't think there is a way to end that
without a reboot.

Maybe someone else will have better ideas.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

Robert Moskowitz
In reply to this post by Samuel Sieb


On 06/14/2017 11:28 PM, Samuel Sieb wrote:

> On 06/14/2017 07:45 PM, Robert Moskowitz wrote:
>> I had an Office Base database open for a few days (and a couple
>> system suspends), along with lots of spreadsheets and docs.  Went to
>> close Base and save the database and now none of the LibreOffice docs
>> are responding.
>>
>> I thought I found the soffice.bin running and killed it, but it still
>> seems to be running and I can't see if there is any other related
>> process.
>>
>> How can I find the process and kill it?  I really don't want to boot...
>
> That should be the one.  Is it really dead?  Why do you think it's
> still running?

The windows are still showing on my desktop (Xfce).  But I can't switch
to them.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

Robert Moskowitz
In reply to this post by stan


On 06/14/2017 11:28 PM, stan wrote:

> On Wed, 14 Jun 2017 22:45:02 -0400
> Robert Moskowitz <[hidden email]> wrote:
>
>> How can I find the process and kill it?  I really don't want to
>> boot...
> You can find all processes you are running by
> ps alx | grep -i [your user name]
> I think you should be able to do the same thing with top or one of the
> other process viewers by filtering.  It might be that the process is in
> an uninterruptable sleep.  I don't think there is a way to end that
> without a reboot.
>
> Maybe someone else will have better ideas.

I found three listed:

0  1000 19985     1  20   0  49204  1144 unix_s Sl   ?          0:00
/usr/lib64/libreoffice/program/oosplash --calc
file:///home/rgm/data/excel/htt/expenses-2016.xls
0  1000 20012     1  20   0  49204  1132 unix_s Sl   ?          0:00
/usr/lib64/libreoffice/program/oosplash --calc
file:///home/rgm/data/excel/htt/expenses-2016.xls
0  1000 20024     1  20   0  49204  1124 unix_s Sl   ?          0:00
/usr/lib64/libreoffice/program/oosplash --calc
file:///home/rgm/data/excel/htt/expenses-2016.xls

killed those, but still see the windows.

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

stan
On Wed, 14 Jun 2017 23:39:00 -0400
Robert Moskowitz <[hidden email]> wrote:


> I found three listed:
>
> 0  1000 19985     1  20   0  49204  1144 unix_s Sl   ?          0:00
> /usr/lib64/libreoffice/program/oosplash --calc
> file:///home/rgm/data/excel/htt/expenses-2016.xls
> 0  1000 20012     1  20   0  49204  1132 unix_s Sl   ?          0:00
> /usr/lib64/libreoffice/program/oosplash --calc
> file:///home/rgm/data/excel/htt/expenses-2016.xls
> 0  1000 20024     1  20   0  49204  1124 unix_s Sl   ?          0:00
> /usr/lib64/libreoffice/program/oosplash --calc
> file:///home/rgm/data/excel/htt/expenses-2016.xls
>
> killed those, but still see the windows.

Two things.

This display doesn't show the parent process ID for the PID.  It might
be that the parent of these threads is what is displaying the windows
as it waits for their output to update them.  Use this command to look
for the PPID, and kill it as well (if it isn't 1, :-)  )
ps -eF --headers | grep [user name]
It won't show the process status, like the earlier command, where we
knew that they were sleeping threads.

Another possibility is that the windows are artifacts at this point.
When you killed the process, it didn't clean up after itself, and left
the windows. What happens if you log your user out of X, and then log
back in?
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

Robert Moskowitz


On 06/15/2017 12:13 AM, stan wrote:

> On Wed, 14 Jun 2017 23:39:00 -0400
> Robert Moskowitz <[hidden email]> wrote:
>
>
>> I found three listed:
>>
>> 0  1000 19985     1  20   0  49204  1144 unix_s Sl   ?          0:00
>> /usr/lib64/libreoffice/program/oosplash --calc
>> file:///home/rgm/data/excel/htt/expenses-2016.xls
>> 0  1000 20012     1  20   0  49204  1132 unix_s Sl   ?          0:00
>> /usr/lib64/libreoffice/program/oosplash --calc
>> file:///home/rgm/data/excel/htt/expenses-2016.xls
>> 0  1000 20024     1  20   0  49204  1124 unix_s Sl   ?          0:00
>> /usr/lib64/libreoffice/program/oosplash --calc
>> file:///home/rgm/data/excel/htt/expenses-2016.xls
>>
>> killed those, but still see the windows.
> Two things.
>
> This display doesn't show the parent process ID for the PID.  It might
> be that the parent of these threads is what is displaying the windows
> as it waits for their output to update them.  Use this command to look
> for the PPID, and kill it as well (if it isn't 1, :-)  )
> ps -eF --headers | grep [user name]
> It won't show the process status, like the earlier command, where we
> knew that they were sleeping threads.
>
> Another possibility is that the windows are artifacts at this point.
> When you killed the process, it didn't clean up after itself, and left
> the windows. What happens if you log your user out of X, and then log
> back in?

ps -eF --headers | grep rgm|grep libre
rgm       1989  1923  0 49269    52   0 Jun08 ?        00:00:02
/usr/lib64/libreoffice/program/oosplash --calc
rgm       2004  1989  0 1203439 94488 0 Jun08 ?        00:23:38
/usr/lib64/libreoffice/program/soffice.bin --calc --splash-pipe=5
rgm      21775 16594  0  2683   980   0 00:46 pts/4    00:00:00 grep
--color=auto libre

2004, I tried to kill before...

And 1989 was the magic ticket.  Killed it and the windows disappeared
and 2004 and 21775 disappeared.

So now I have to add this to my tricks list for the next time....

And I really hate logging out, almost as bad as rebooting.  I have 19
Firefox windows, all with lots of tabs, 4 Thunderbird windows. Lots of
Leafpads and some xml stuff opened in Geany and a QEMM image...

Too painful to restart everything.  Even with recovery.  Will be enough
now recovering the 10 open LIbre office windows...

Again thanks
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

stan
In reply to this post by stan
On Wed, 14 Jun 2017 21:13:03 -0700
stan <[hidden email]> wrote:

> Another possibility is that the windows are artifacts at this point.
> When you killed the process, it didn't clean up after itself, and left
> the windows. What happens if you log your user out of X, and then log
> back in?

If this is the case, there might be a lock file that the program checks
to see if it is already running.  If the lock file hasn't been removed,
just like the windows, it won't restart until the lock file is
deleted.  
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

stan
In reply to this post by Robert Moskowitz
On Thu, 15 Jun 2017 00:51:39 -0400
Robert Moskowitz <[hidden email]> wrote:

> ps -eF --headers | grep rgm|grep libre
> rgm       1989  1923  0 49269    52   0 Jun08 ?        00:00:02
> /usr/lib64/libreoffice/program/oosplash --calc
> rgm       2004  1989  0 1203439 94488 0 Jun08 ?        00:23:38
> /usr/lib64/libreoffice/program/soffice.bin --calc --splash-pipe=5
> rgm      21775 16594  0  2683   980   0 00:46 pts/4    00:00:00 grep
> --color=auto libre
>
> 2004, I tried to kill before...
>
> And 1989 was the magic ticket.  Killed it and the windows disappeared
> and 2004 and 21775 disappeared.
>
> So now I have to add this to my tricks list for the next time....
>
> And I really hate logging out, almost as bad as rebooting.  I have 19
> Firefox windows, all with lots of tabs, 4 Thunderbird windows. Lots
> of Leafpads and some xml stuff opened in Geany and a QEMM image...
>
> Too painful to restart everything.  Even with recovery.  Will be
> enough now recovering the 10 open LIbre office windows...

I can see how restarting all that would be disruptive.  Almost like
moving to a new house. :-)

>
> Again thanks

You're welcome, glad it worked out for you.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F25 LibreOffice hung

Tim-163
In reply to this post by Robert Moskowitz
Allegedly, on or about 15 June 2017, Robert Moskowitz sent:

> ps -eF --headers | grep rgm|grep libre
> rgm       1989  1923  0 49269    52   0 Jun08 ?        00:00:02
> /usr/lib64/libreoffice/program/oosplash --calc
> rgm       2004  1989  0 1203439 94488 0 Jun08 ?        00:23:38
> /usr/lib64/libreoffice/program/soffice.bin --calc --splash-pipe=5
> rgm      21775 16594  0  2683   980   0 00:46 pts/4    00:00:00 grep
> --color=auto libre
>
> 2004, I tried to kill before...
>
> And 1989 was the magic ticket.  Killed it and the windows disappeared
> and 2004 and 21775 disappeared.
>
> So now I have to add this to my tricks list for the next time....

For situations like that, I rather like the "killall" command.  Instead
of me having to find all the Firefox, for example, instances that are
jamming, and all their process ids, then issue commands per id (usually
the smallest id takes the lot out, but not always).  I can issue
"killall firefox" a few times, until it dies and I see a "no process
found" response (no more of them to kill).  Though usually once is
enough.  It also takes a "-9" parameter, for the times that you need a
"when I say 'woh' I mean 'woh'!" command.

--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
(always current details of the computer that I'm writing this email on)

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

Windows (TM) [Typhoid Mary]. They refuse to believe that there's
anything wrong with it, but everyone else knows Windows is a disease
that spreads.


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]