Download it now!
Bug 130902 - FILEOPEN Calc crashes when opening an .ods file created by itself
Summary: FILEOPEN Calc crashes when opening an .ods file created by itself
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: KDE
  Show dependency treegraph
 
Reported: 2020-02-24 15:15 UTC by szotsaki
Modified: 2020-10-04 03:50 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 szotsaki 2020-02-24 15:15:57 UTC
I have an .ods file which I created with Calc. When I try to open it Calc immediately shows the recovery window (funnily, first with no document then after a retry with the current document).

Excel opens it.

Could you please give me a private address to where I can send the document?

Version: 6.4.0.3
Build ID: 40(Build:3)
CPU threads: 8; OS: Linux 5.5; UI render: default; VCL: kf5; 
Locale: hu-HU (hu_HU.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Xisco Faulí 2020-02-25 09:08:50 UTC
(In reply to szotsaki from comment #0)
> I have an .ods file which I created with Calc. When I try to open it Calc
> immediately shows the recovery window (funnily, first with no document then
> after a retry with the current document).
> 
> Excel opens it.
> 
> Could you please give me a private address to where I can send the document?
> 
> Version: 6.4.0.3
> Build ID: 40(Build:3)
> CPU threads: 8; OS: Linux 5.5; UI render: default; VCL: kf5; 
> Locale: hu-HU (hu_HU.UTF-8); UI-Language: en-US
> Calc: threaded

Sure. could you please send it to me?
OTOH, Does it crash if you launch libreOffice from console with 'SAL_USE_VCLPLUGIN=gen soffice' ?
Comment 2 szotsaki 2020-03-04 22:42:43 UTC
Document is sent in e-mail and as I wrote there it doesn't crash with the setting 'SAL_USE_VCLPLUGIN=gen soffice'. Thank you for the hint!
Comment 3 Michael Weghorn 2020-03-05 18:33:34 UTC
Xisco asked me to test, but I could not reproduce; the document opens just fine for me with


Version: 7.0.0.0.alpha0+
Build ID: 950e1aec0a984ce40a5038331f491272b51d41fa
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5;
Locale: en-GB (en_GB.UTF-8); UI-Language: en-US
Calc: threaded

and also the LibreOffice version shipped in Debian testing:

Version: 6.4.1.2
Build ID: 1:6.4.1-1
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5;
Locale: en-GB (en_GB.UTF-8); UI-Language: en-US
Calc: threaded
Comment 4 szotsaki 2020-03-06 09:52:45 UTC
Hmm, how can I help debugging this without recompiling the whole suit? Is there an environmental variable to set logging categories and levels run-time like Qt logging facility?
Comment 5 Michael Weghorn 2020-03-06 12:07:28 UTC
(In reply to szotsaki from comment #4)
> Hmm, how can I help debugging this without recompiling the whole suit? Is
> there an environmental variable to set logging categories and levels
> run-time like Qt logging facility?

Can you try a daily debug master build (which also has more log output enabled) from [1] ?

The SAL_LOG variable can be used to further tweak what to print, s. [2], but it's probably non-trivial to know what to set it to...

Also, a backtrace might help and [3] describes how to get one.

[1] https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@86-TDF-dbg/
[2] https://wiki.documentfoundation.org/Development/GeneralProgrammingGuidelines#Assertions_and_Logging
[3] https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Comment 6 QA Administrators 2020-09-03 04:03:14 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2020-10-04 03:50:45 UTC
Dear szotsaki,

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-FollowUp