Bug 125102 - LO crashes upon trying to save a file
Summary: LO crashes upon trying to save a file
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.5.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-03 10:35 UTC by Christian Lehmann
Modified: 2019-06-04 15:23 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
screen video showing cursor flickering in 'Name' field. (1.48 MB, video/mp4)
2019-05-03 10:38 UTC, Christian Lehmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Lehmann 2019-05-03 10:35:51 UTC
Description:
I have a file open in Writer or Draw or Impress. (The bug does not seem to happen in Base and Calc.)

From the File menu, I choose one of the following:
- Close
- Save as

or if it is a new (untitled) file:
- Save.

In all these cases, either #a or #b happens:

a) "Due to an unexpected error, LibreOffice crashed."

For the crashes, crash reports have been automatically sent for several weeks now, including several in the past hour.

b) The saving window appears.
- I put the cursor in the field 'Name'.
- I try to overwrite the name offered there, e.g. 'untitled'.
- The cursor hops wildly in the field, repeating in an endless loop the characters I am typing until I hit 'save'.
- The document is then saved with that wild name.

The difference between the events #a and #b appears to depend on various factors: Number of repetitions of attempts, executing the operation by key shortcuts (crashes) or with the mouse (occasionally works).

Cp. Bug 120050


Steps to Reproduce:
1. Have a file open.
2. Hit CTRL-SHIFT-S.
3. Specify file name.

Actual Results:
If it has not crashed up to that point, the cursor in the 'Name' field flickers upon typing and repeats characters in endless loop.

Expected Results:
It should be possible to normally type in the field and save the file.


Reproducible: Always


User Profile Reset: No



Additional Info:
I will try to submit a screen recording.
Comment 1 Christian Lehmann 2019-05-03 10:38:27 UTC
Created attachment 151154 [details]
screen video showing cursor flickering in 'Name' field.

The screen video enclosed (sorry, I am not versed in these things) shows a first attempt at saving the text, which appears to be succeeding. I interrupt this one and make a second attempt, putting the cursor at the end of the name field. Hitting 'delete' once deletes the entire text that was there. Then I type, and the characters in the field flicker until I hit 'save'. Then LO closes.
Comment 2 Oliver Brinzing 2019-05-03 17:10:30 UTC
not sure if this can help, but with LO 6.1.6 some problems with file dialog
have been fixed, e.g.:

- crash: use of "com.sun.star.ui.dialogs.FolderPicker" crashes (tdf#123502) 
- gtk3_kde5, kde5: Crash when minimizing file save dialog (tdf#123077)
Comment 3 Christian Lehmann 2019-05-04 09:37:00 UTC
Thanks for the hint. I will try that (although 6.1.6 is not yet recommended as a stable version).

Meanwhile I can report that LO Writer also crashes in the following situation:
- Have a document open.
- Hit the shortcut CTRL-o to open another document.
Here the same message as above appears, and one may send an automatic error report. I did this twice in the last few minutes, just in case anybody among the developers would be interested.

The generalization seems to be that any file operations may lead to a breakdown of LO if they are triggered while a document is open.
Comment 4 Xisco Faulí 2019-05-09 08:51:52 UTC
Hello Christian,
LibreOffice 6.1.6 as been announced as final this week.
Could you please download it from https://www.libreoffice.org/download/libreoffice-fresh/ and retest this bug ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 Christian Lehmann 2019-05-10 19:41:59 UTC
LO 6.1.5.2 installed under Kubuntu 18.04, KDE Plasma 5.12.7.
LO 6.1.6.3 installed under Ubuntu 18.04.2.
The file operations which, if called while an LO file is open, guarantee crash of LO 6.1.5, appear to work well with LO 6.1.6.

It may be noted, however, that this is a very serious bug with which LO 6.1.5 should no longer be distributed.
Comment 6 QA Administrators 2019-05-14 03:02:53 UTC Comment hidden (obsolete)
Comment 7 Xisco Faulí 2019-05-14 09:09:07 UTC
(In reply to Christian Lehmann from comment #5)
> LO 6.1.5.2 installed under Kubuntu 18.04, KDE Plasma 5.12.7.
> LO 6.1.6.3 installed under Ubuntu 18.04.2.
> The file operations which, if called while an LO file is open, guarantee
> crash of LO 6.1.5, appear to work well with LO 6.1.6.
> 
> It may be noted, however, that this is a very serious bug with which LO
> 6.1.5 should no longer be distributed.

What happens if you install LibreOffice 6.1.6.3 under Kubuntu? Does it crash ?
OTOH, support for KDE5 has been implemented in LibreOffice 6.2.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 8 Christian Lehmann 2019-06-04 15:16:51 UTC
Some requests for information take a little bit longer to comply ...
I have now installed LO 6.2.4.2 on Kubuntu 18.04.2 LTS. It appears that both problems (crash if one triggers a file operation by hitting a key, and flickering text entry field) are gone.
Comment 9 Xisco Faulí 2019-06-04 15:23:28 UTC
(In reply to Christian Lehmann from comment #8)
> Some requests for information take a little bit longer to comply ...
> I have now installed LO 6.2.4.2 on Kubuntu 18.04.2 LTS. It appears that both
> problems (crash if one triggers a file operation by hitting a key, and
> flickering text entry field) are gone.

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.