Bug 44863 - Calc EDITING: when recovered after crash, impossible to enter into cells
Summary: Calc EDITING: when recovered after crash, impossible to enter into cells
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.0 Beta2
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-17 07:02 UTC by sasha.libreoffice
Modified: 2015-01-06 18:29 UTC (History)
4 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 sasha.libreoffice 2012-01-17 07:02:42 UTC
Steps to reproduce:
0. Start Calc
1. send KILL signal to soffice.bin
2. start Calc second time
3. agree all steps of recovery
4. enter something in cell and press enter
Expected: entered value appears in cell
Actually: nothing appears in cell
This behaviour remains until restart of Calc of switch to another Seet of spreadsheet.

Produced in LibO 3.5.0 beta 1 on Fedora 64 bit
Comment 1 Eike Rathke 2012-01-17 11:15:11 UTC
Confirmed. Though happens only on a new yet unsaved document.
Comment 2 Petr Mladek 2012-01-23 10:14:14 UTC
It does not happen when the document is saved with autosafe. So, it affects only people that worked on the document very shortly.
Comment 3 QA Administrators 2014-06-25 17:37:59 UTC
Please read this message in its entirety before responding.

Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed.

If you have time please do the following:
1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer).
2) If it is present please leave a comment telling us what version of LibreOffice and your operating system.
3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System

Please DO NOT
1) Update the version field
2) Reply via email (please reply directly on the bug tracker)
3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage

There are also other ways to get involved including with marketing, UX, documentation, and of course developing -  http://www.libreoffice.org/get-help/mailing-lists/. 

Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Comment 4 Joel Madero 2015-01-06 18:29:36 UTC
Tested on:
Ubuntu 14.04
LibreOffice 4.4 beta 2

Cannot reproduce the problem. Marking as WFM.


If anyone can reproduce this on 4.4 or newer, please set back to UNCONFIRMED so we can get verification that it's still an issue. Thank you!