Bug 85993 - Crash when moving a worksheet to a new spreadsheet document.
Summary: Crash when moving a worksheet to a new spreadsheet document.
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-11-07 05:49 UTC by klsu
Modified: 2015-06-10 05:28 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description klsu 2014-11-07 05:49:13 UTC
Steps to reproduce the problem:

1. Starting with an existing workbook with 19 worksheets.
2. Create a new, blank workbook.
3. Switch to the existing workbook, right click on one of the worksheet tabs and select Move/Copy Sheet...
4. Select the Action Move, the To document Untitled1, Insert before Sheet 1, and leave the sheet name as-is.
5. Click OK.

LibreOffice Calc crashes, and when I restart, it must recover both documents. I must copy the sheet to the new document, and then delete it from the old one, to get the desired result.
Comment 1 Terrence Enger 2014-11-08 03:04:56 UTC
I have moved the sheet without any problem in daily dbgutil repository version 2014-11-07 and in 
Version: Build ID: 7bf567613a536ded11709b952950c9e8f7181a4a.
Comment 2 A (Andy) 2014-11-08 11:41:13 UTC
For me not reproducible with LO, Win 8.1.

Can you also reproduce it with a new sample file or is this only linked to a specific file?
Comment 3 Tim Lloyd 2014-11-10 01:01:21 UTC
No problems with XP & LO4.2.0.4. Fedora 21/LO

What operating system are u using?
Comment 4 Julien Nabet 2014-11-11 10:23:47 UTC
Following last comments, I put this one to NEEDINFO.
Comment 5 QA Administrators 2015-06-08 14:28:42 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:

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!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 6 klsu 2015-06-09 23:23:07 UTC
Sorry, I apparently didn't get an email telling me there was a question. I am using Linux. At the time that I found the bug, I was running Mint Petra; however, having no use for a Linux that cannot be upgraded to a new distribution, I have since switched to Xubuntu.

Unfortunately, during the first few hours of trying LO Calc, I discovered (MOD() and DATE()) bugs that result in random incorrect answers caused by improper handling of significant digits. When I reported them, I was informed that these functions require the user to make sure the input to the functions are of a specific format, and that they are therefore not bugs. This means that I must read about the limitations of every function I use and keep notes I can refer to every time I want to use a function. Since computers are supposed to work for users, and not users for computers, this is unacceptable.

In addition, in certain professions, random incorrect answers are worse than crashes or not having the functions at all, because lives or property could be lost. For this reason, I see no reason to consider LibreOffice Calc for serious work. Excel doesn't have these problems. One or both of these problems also exist in OpenOffice Calc, GNumeric, and another fork of OpenOffice I tried (Calligra?). Too bad everyone working on Linux wants to have their own version instead of working together to make one version that works correctly.

You might as well close this bug and wait for someone who is forced to use LibreOffice Calc to find it, if it still exists. I cannot afford to spend time helping programmers fix a spreadsheet that I can't use for calculations.