Bug 57024 - Libreoffice Calc crashes opening ODS from previous version
Summary: Libreoffice Calc crashes opening ODS from previous version
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-12 17:53 UTC by Scott Johnson
Modified: 2013-10-25 15:16 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
GDB Log Trace for LibreOffice Calc Crash (17.98 KB, text/plain)
2012-11-12 17:53 UTC, Scott Johnson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Johnson 2012-11-12 17:53:46 UTC
Created attachment 69952 [details]
GDB Log Trace for LibreOffice Calc Crash

Using the latest version of Libreoffice Calc on Ubuntu 11.04, I created a file to track my Timekeeping (Timekeeping2012.ods). It is around 184K in size.

Now, I've upgraded to Ubuntu 12.10 with Libreoffice 3.6. When I attempt to open my ods file, I get a crash. Attached is a gdb log trace of the crash.
Comment 1 Julien Nabet 2012-11-12 22:06:59 UTC
Could you tell what's your precise LO version?
Could you attach the file so we can try to reproduce?
If not, could you install debug symbols for the bt? (see http://wiki.documentfoundation.org/BugReport#How_to_get_a_backtrace_.28on_Linux.29)
Comment 2 Roman Eisele 2012-11-14 18:04:16 UTC
(This is a Calc issue, so let us set the Component field accordingly.)
Comment 3 Mathis Ahrens 2012-12-20 12:04:08 UTC
A possible workaround FWIW: I saw the same symptoms, removed Ubuntu's libreoffice* packages (which had version 3.6.2~rc2-0ubuntu3, 64bit) and installed the latest 3.6.4 instead.
No more crashes when opening the same file as before.
Comment 4 Kohei Yoshida 2013-01-29 21:14:49 UTC
Scott, The gdb backtrace doesn't give us the whole stack trace unfortunately.  Is there anyway you can attach Timkeeping2012.ods to this bug report?
Comment 5 Scott Johnson 2013-03-12 15:32:56 UTC
(In reply to comment #4)
> Scott, The gdb backtrace doesn't give us the whole stack trace
> unfortunately.  Is there anyway you can attach Timkeeping2012.ods to this
> bug report?

Hm, I'd rather not attach it, since it contains some personal information. I would be willing to send it to you, though, if you would respect my privacy and keep it to yourself and developers within your group (i.e. not post it publicly).

Would this be acceptable?
Comment 6 QA Administrators 2013-09-24 02:01:19 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 7 QA Administrators 2013-10-25 15:16:55 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO