https://bugs.documentfoundation.org/show_bug.cgi?id=146845
Albrecht Müller <albrecht.muel...@astrail.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|1 |0
Status|NEEDINFO |UNCONFIRMED
CC| |albrecht.muel...@astrail.de
--- Comment #2 from Albrecht Müller <albrecht.muel...@astrail.de> ---
Finding repro steps may be the hard part of this bug. That's why I uploaded
three crash reports together with bug reports (this one, bug 146943 and bug
146944 ) to demonstrate that the bug is there and it happens way to often.
Nevertheless I gave it a try: The crash reported in bug 146944 occurred in a
simple setting and it was easy to create a broken document that makes Writer
report macros that do not exist. But using this document I was not able to
reproduce any crash. See
https://bugs.documentfoundation.org/show_bug.cgi?id=146944#c4 and attachment
177914
I think I better spend my time updating the document I mentioned in bug
https://bugs.documentfoundation.org/show_bug.cgi?id=146958#c2 by information
that helps me to get along with the problem. For example this way:
(1) The user profile should be under version control.
(2) If you happen to see repeating splash screens:
(2a) Trying to abort the process using the task manager may not work. You can
abort it using the resource monitor. Maybe you need several tries to hit the
confirmation button of the resource monitor: Try to hit it in the split second
pause between the splash screens. This makes it unnecessary to restart the
current session to abort the LO Process. You probably will be asked to send a
crash report but this is useless (see Timurs comment
https://bugs.documentfoundation.org/show_bug.cgi?id=146943#c1). Time spent on
trying to find steps to reproduce is wasted as the crash seem to occur at
random for no obvious reason.
(2b) Check if the installed extensions still work. If not (that's usually the
case), try to reinstall them or restore the damaged parts of the user profile
from version control. This is faster than reinstalling the extensions
individually. That's one of the reasons for point (1).
(2c) Starting the recovery process one more time in general works as usual. You
only have to find out what part of your work got lost and to redo it. That's
the same as after any common crash which does not ask you to send a crash
report.
There are other options I did not try yet:
(ad 2b) My Windows installation keeps some previous versions of all directories
and files. I think this is a Windows default. This feature helped me sometimes
to restore contents destroyed by misbehaving applications. Problems of this
approach: At the time you notice the problem it may be too late to use this
mechanism as the version you need may be gone. Comparing the current version
with some previous version by hand is time consuming and error prone. I had not
need to use this backup mechanism as I have the user profile under version
control as proposed in (1).
(ad 2) The cause of the repeating splash screen phenomenon may be some problem
in the user profile. Therefore it might help to figure out what options
(including keyboard shortcuts, toolbars etc.) had been changed with respect to
the defaults, store necessary data and code at some safe place, store some
backup of the user profile, deinstall LibreOffice, delete the user profile,
reinstall LibreOffice, reinstall all extensions, restore the saved data and
code and change all options to the values they had before. Did not try as this
is a lot of work, might cause unexpected side effect and it is not clear if it
will stop the repeating splash screen phenomenon.
As I cannot provide additional useful information I set the bug back to state
'UNCONFIRMED' as you proposed.
--
You are receiving this mail because:
You are the assignee for the bug.
