Bug 97549 - Libre Office blocks software update restart even after being force quit
Summary: Libre Office blocks software update restart even after being force quit
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-04 04:14 UTC by MK Bretsch
Modified: 2017-05-02 11:34 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MK Bretsch 2016-02-04 04:14:12 UTC
I've several times had Libre Office block software updates that require restarts, even after being force quit. One shouldn't have to force quit ever, anyway, but something is "reawakening" Libre Office and blocking restart. Tedious! TIA!
Comment 1 Buovjaga 2016-02-10 18:40:06 UTC
Which version of LibO and OS X are you using?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 Julien Nabet 2016-07-03 11:59:07 UTC
2 things you can do:
1) Rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Mac_OS_X). Of course it implies doing the customization again if any, reinstall extensions.
2) Give a try to last stable LO version 5.1.4
Comment 3 Alex Thurgood 2016-09-07 09:28:04 UTC
@MK Bretsch : we need more information on the exact situation.

Are you referring to :
1) LibreOffice version updates ?
2) LibreOffice extension updates ?
3) OSX System updates ?

It is not entirely clear from your post which one you mean. I suspect number 3.

We would need precise and detailed circumstances of when such a situation arises, and how to reproduce it in a systematic way.

There are known instances where a file lock can be obtained on a file by LibreOffice, and this file lock is then not released correctly by LibreOffice, even after a forced kill, but you would need to verify that such is the case on your machine with a latest production release of LibreOffice and report back here.
Comment 4 QA Administrators 2017-03-28 08:18:04 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2017-05-02 11:34:27 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170502