Bug 129184 - Cannot launch Calc if Writer has a recoverable file
Summary: Cannot launch Calc if Writer has a recoverable file
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-04 15:31 UTC by david.cortes.rivera
Modified: 2019-12-10 23:22 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description david.cortes.rivera 2019-12-04 15:31:32 UTC 
If I have a recoverable file from Writer (that would trigger the recovery dialog upon start up) and try to open a .csv file with Calc, Calc will not start if I choose to discard the temporary file.

Steps to reproduce:
* Launch Writer.
* Write something on it, without saving the document.
* Terminate Writer abruptly.
* Try to open a CSV file with Calc.
* In the recovery dialog from Writer, choose to discard the file.

Expected behavior: should launch Calc with the CSV file opening dialog.

Actual behavior: Calc is not launched.

Version: 6.3.1.2
Build ID: 1:6.3.1-1
CPU threads: 16; OS: Linux 5.2; UI render: GL; VCL: kde5; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Xisco Faulí 2019-12-10 16:05:10 UTC 
I can't reproduce it in

Versió: 6.3.3.2
ID de la construcció: 1:6.3.3-0ubuntu0.18.04.1~lo1
Fils de CPU: 4; SO: Linux 4.15; Renderitzador de la IU: per defecte; VCL: gtk3; 
Configuració local: ca-ES (ca_ES.UTF-8); Llengua de la IU: ca-ES
Calc: threaded

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 2 david.cortes.rivera 2019-12-10 20:52:19 UTC 
Solved in 6.3.3-3.
Comment 3 Xisco Faulí 2019-12-10 23:22:04 UTC 
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.