Bug 116123 - FILESAVE : LibO freeze when saving a REPORT
Summary: FILESAVE : LibO freeze when saving a REPORT
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.4.5.1 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-01 16:48 UTC by Paul AMIET
Modified: 2018-03-08 11:45 UTC (History)
1 user (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 Paul AMIET 2018-03-01 16:48:10 UTC
Hi
My odb file points to an EXCEL file containing the data.
I can write SELECT requests as usual
I can create a report based on a request
I can adjust the formatting of the report to get an ods file instead of an odt file (default)
I can run the report and it gives me the expected results
BUT
when I save the modified report, LibO freezes.
I must crash LibO and after the recovery process is done, of course the report is not at the good version.

What can I try ?
Thanks
Comment 1 Alex Thurgood 2018-03-06 08:19:05 UTC
No repro with 

Version: 6.1.0.0.alpha0+ (own daily build from master)
Build ID: 9122f4598450d8a96e63fb29cc8166a6ae09587a
CPU threads: 4; OS: Mac OS X 10.13.3; UI render: default; 
Locale: fr-FR (fr_FR.UTF-8); Calc: group

using a simple Excel 2013 xlsx file as the datasource.


@Paul : please provide detailed step-by-step instructions and a sample ODB and Excel file with which we can try and reproduce the behaviour you report.

Setting to NEEDINFO, please set back to UNCONFIRMED once you have provided the requested information.
Comment 2 Paul AMIET 2018-03-07 14:04:13 UTC
I upgraded LibO from 5.4.5.1 to Version: 6.0.2.1
Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
Threads CPU : 8; OS : Mac OS X 10.11.6; UI Render : par défaut; 
Locale : fr-FR (fr.UTF-8); Calc: group
I can't reproduce the problem.
So I close the case.
Comment 3 Xisco Faulí 2018-03-08 11:45:23 UTC
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.