Description: Preparation: 1) Enter a column of values 2) Select all populated cells and 3) Data->define range, give it a name On another sheet ("sheet two"): 1) Select a range of cells in a column 2) Data->Validity->Cell Range 3) Enter then name given previously Testing: 1) On "sheet two", enter value by selecting from the dropdown Result : ok, works as expected 2) In another cell manually enter a partial value Result: "Invalid value" message box. But "OK" button does not close the Message box, must use ESC to regain control. 3) After a value has been selected via drop down, that value may be manually entered in a different cell and will auto-complete. 4) After a) manually entering a partial value that was not previously entered, b) dropping down the list, c) again entering a partial value LibreOffice Calc hangs and is completely unresponsive to mouse or keyboard. I have only been able to recover from this by restarting the PC. (finding the process id and "kill -9 the_pid" seems to work, but I'm nervous about side effects or killing the wrong process.) On restart, it is necessary to go through the document recovery, but after recovery reference to the defined cell range is lost - drop down shows "#N/A". It is necessary to again select and name the cells to be used for validating and populating the drop down. ------------ Version: 6.1.5.2 Build ID: 1:6.1.5-3+deb10u4~bpo9+1 CPU threads: 12; OS: Linux 4.9; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group threaded Running Debian 9.11 Steps to Reproduce: See description Actual Results: See description Expected Results: See description Reproducible: Always User Profile Reset: No Additional Info: See description
I have just tried this on Windows 7 with LO 6.2.0.3 and was not able to get it to misbehave.
And sometimes simply clicking on the dropdown list multiple times, or clicking on and off the dripdown causes the cursor to change to a cross and the program to irrevocably hang.
6.1 branch is EOL (idem for 6.2 branch), could you give a try to last stable LO version 6.3.4? Of course, if you use Debian 9 which corresponds to Stretch, you'll have to use testing repository to retrieve last stable LO version and its dependencies. IMHO, stable Debian is more for servers which use mature versions with security backports, not for Office work. (I use Debian testing)
I'd love to, but trying 6.2 is not in the cards any time soon. Too many things listed here to risk killing my ability to get real work done: https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html Tried backports - apt refuses. "Unable to correct problems, you have held broken packages" This is a rabbit hole which I have been down without success too often to mess with now. I suppose at some future point when I can afford the possibility of being down for a couple of days I will update and upgrade everything. Not this week. Meanwhile, it would be interesting to know if this was a "known to be fixed in 6.2" bug, or a 'Works in Windows but not Linux" bug. I have tried to search here but have not been able to find any other reference to this particular behavior.
I understand your point of view. Let's put it back to unconfirmed. Personally, I don't want to spend time about a bug which is perhaps already fixed in a recent LO version. => uncc myself
Hello m ferdman, To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Resetting the user profile did not change the behavior. Still an issue. Changed back to "UNCONFIRMED".
Using appimages is an easy way to test different versions: https://libreoffice.soluzioniopen.com/
(In reply to Buovjaga from comment #8) > Using appimages is an easy way to test different versions: > https://libreoffice.soluzioniopen.com/ Indeed. Setting to NEEDINFO until the reported give us feedback on the latest version
Dear m feldman, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
Dear m feldman, 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