Upon opening CALC the user is presented with a dialog box stating that CALC had crashed the previous time even though it hadn't. This is repeatable. Here are the steps to replicate the action: 1. open an existing spreadsheet or a new spreadsheet. 2. fill in one or more cells with any data 3. copy or cut one or more cells to another location of cells 4. close the spreadsheet; you may save it or not. 5. open CALC and you should get the notification dialog box asking the user if s/he wants to submit a crash report. I found that if I opened the GEDIT editor after closing the spreadsheet and typing some random data into it and then copied and pasted within the GEDIT document, that subsequent opening of CALC will not cause the notification dialog box to appear. I could be wrong but it appears that any cut and paste action within CALC will cause this notification box to appear unless the user opens a different application and does copy and paste operations within that application.
Upon additional testing I found that the act of copying or cutting data is the culprit. Pasting the data has no affect on the outcome of this bug.
With the steps outlined, not reproducible in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4e4a31ac7d920c71e26ca4acd18c11ec2bd015bb CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Perhaps, there may be more specific setup required to reproduce the issue.
It is possible that this has been corrected in a subsequent version. This is the version information that I am currently using and noticed the issue: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL
Created attachment 184204 [details] video demonstrating the issue on CALC in order to demonstrate how this bug can be reproduced I have made a screen recording of the bug.
I don't repro with Version: 7.4.0.2 / LibreOffice Community Build ID: 1512ce97d7ed39dce3121f7e15651fd8895f950e CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Neither with Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ad085990b8073a122ac5222e5220f8f1d6826dcf CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Please try: Help - Restart in Safe Mode - Reset to Factory settings and check that 2 options from there. And try to reproduce again this bug.
I've restarted in safe mode and reset to factory settings and checked the two boxes and I am still able to reproduce on: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL My system environment is Fedora 36 server edition with the Cinnamon version 5.2.7 desktop. I have a mirrored disk that I use to practice upgrading my operating system before going live. I used it to upgrade to Fedora 37 server edition and installed the latest version of LibreOffice version 7.4.3.2. I was not able to reproduce on that system. Maybe this is some strange artifact of Fedora 36 or Cinnamon version 5.2.7. I tried this on various live Linux distributions and I am not able to reproduce the behavior. I can only conclude that it is probably some interaction between Fedora 36 or the desktop and LibreOffice. In any event, this is more of an annoyance than anything else as it does not prevent the usage of the product. The worst that seems to happen is that an error dialog box is presented to the user that is out of context to the reality of the product integrity. I'll be upgrading to Fedora 37 next weekend and test it at that time. If I see a re-occurrence of this behavior I'll open a new bug report. In the meantime I appreciate that you looked into this.
Thanks Howard. 1) Could you please try running LO from the command line, to see if any interesting messages pop up? For example with the command: libreoffice7.4 --calc (or if that does not work: https://help.libreoffice.org/latest/he/text/shared/guide/start_parameters.html) 2) Have you tried actually sending the crash report, so we have a link to a backtrace? 3) Can you reproduce with copying in a different component, e.g. Writer?
Hi, Stephane I tried what you asked and here are the results 1. I initiated LibreOffice from the command line and the only message I got was: javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx 2. When I am able to reproduce the behavior with CALC, I tried to send a crash report but no report was sent so I have no URL to report. 3. I launched Libre Writer and did a small copy and exited as with CALC. Then I relaunched Writer and everything opened as normal. I did the same with Draw and everything worked as normal. However, I launched CALC and did the copy and exited. Then I launched Writer and got the error dialog. Same thing happened with Draw. This seems to happen only with a copy from CALC.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Howard Feldman from comment #8) > Hi, Stephane > > I tried what you asked and here are the results > > 1. I initiated LibreOffice from the command line and the only message I got > was: > > javaldx: Could not find a Java Runtime Environment! > Warning: failed to read path from javaldx > > 2. When I am able to reproduce the behavior with CALC, I tried to send a > crash report but no report was sent so I have no URL to report. > > 3. I launched Libre Writer and did a small copy and exited as with CALC. > Then I relaunched Writer and everything opened as normal. I did the same > with Draw and everything worked as normal. > > However, I launched CALC and did the copy and exited. Then I launched > Writer and got the error dialog. Same thing happened with Draw. > > This seems to happen only with a copy from CALC. Try 2 things and repeat what Stephane have told you to do: - go to Tools - Options - Advanced and check "Use a Java runtime". If it is already checked see what is the location of tthe Java (it mustbe shown under the box). - go to Tools - Options - Advanced and check "Send crash reports to The Document Foundation"
Created attachment 184229 [details] screenshot of Tool->Options->Advanced menu I attempted to try the two things but I didn't see a path to the Java runtime even though the box was checked. Also, there was no "Send crash reports to the Document Foundation" In case I missed something I have attached a screenshot of my Advance dialog box.
(In reply to Howard Feldman from comment #11) > Created attachment 184229 [details] > screenshot of Tool->Options->Advanced menu > > I attempted to try the two things but I didn't see a path to the Java > runtime even though the box was checked. > > Also, there was no "Send crash reports to the Document Foundation" > > In case I missed something I have attached a screenshot of my Advance dialog > box. It's seems you don't have have on your computer OR LibreOffice don't see it. For crash report it's in another window, my mistake: Tools - Options - General
okay I see the "send crash reports ..." checkbox but it is already checked. I was able to locate a JRE that had been installed with Pycharm by JetBrains. I added it to my calc environment in the advanced dialog box and it recognized it. I restarted calc by the command line and this time it did not report anything (before it reported that it couldn't find the JRE) Now when I try to reproduce the error I do not get the crash dialog box and the program goes directly to the spreadsheet as expected. So, for now, everything seems to be working as expected and I'm assuming that adding the JRE solved the issue. If there is anything else that you want me to try let me know. If not, thanks for all your help.
I spoke too soon. I had a minimized calc window open when I tried the tests. I closed the window and retried and got the crash dialog box. This time I was able to upload the crash report and it's url is: https://crashreport.libreoffice.org/stats/crash_details/090fc25f-ac9d-4445-b3a9-442b2a7da6f5 I hope this helps
Thank you for the crash report! Looks like bug 151673 might be back?
I just took a look at bug 151673 ( https://bugs.documentfoundation.org/show_bug.cgi?id=151673) and it appears to be the same bug. Here is another data point to try: 1. open or create a spreadsheet 2. select and copy some cells onto the clipboard 3 open another application such as gedit. 4. select and copy some random text in the other application to the clipboard 5. close the spreadsheet 6 open Libre Calc. You will see that the program opens as normal without a crash notification. From all of my testing here is my conclusion: The act of copying some cells to the clipboard and closing the spreadsheet and then reopening Libre Calc without some other application copying to the clipboard will cause a crash notification. Note: that pasting is not necessary. Also note that I have only tried this reliably on the latest release of LibreOffice 7.4.3.2 on Fedora 36 (server edition) with a Cinnamon desktop. When I have time I will attempt to repeat this on Fedora 37 with a Cinnamon desktop and report the results but that might not be for a few days.
okay I found some bandwidth and was able to try this on Fedora 37. This version has been upgraded from Fedora 36 and originally was taken from a mirrored copy of the Fedora 36 I am currently running. The process of upgrading from 36 to 37 also upgraded my Cinammon desktop to 5.4.12 from 5.2.7. I tried the steps again to reproduce the bug but was unable. Both my Fedora 36 and Fedora 37 are running LibreOffice 7.4.3.2 Hope this helps.
Howard, I consider this is working now for you and the bug can be closed.
Let me explain about my last comment. My current daily driver is Fedora 36 with a Cinnamon desktop. The issue still exists on that system. I have a mirrored system that I upgraded from Fedora 36 to Fedora 37 and the process of upgrading caused an upgrade of the Cinnamon desktop to the latest version. The issue went away on that system. I intend to upgrade my daily driver this weekend so my ability to be able to troubleshoot this issue will be limited. I would have no problems with closing this as the occurrence causes a minor annoyance but does not negatively impact the functionality of product. Just understand, however, that the issue has not been fixed and I suspect that it will pop back up sometime in the future.
Julien, any thoughts on this elusive one?
(In reply to Stéphane Guillou (stragu) from comment #20) > Julien, any thoughts on this elusive one? On pc Debian x86-64 with master sources updated today + gtk3 rendering, I don't reproduce this. I just wonder if a "normal" install of JRE via repo packages would help. I mean, it's quite weird you've got to select manually the path of JRE because LO can't find it automatically.
As per the suggestion I installed java and selected it in the Advanced panel and the issue still exists.
(In reply to Howard Feldman from comment #22) > As per the suggestion I installed java and selected it in the Advanced panel > and the issue still exists. How did you install JRE? I mean in comment 13, you indicated "a JRE that had been installed with Pycharm by JetBrains". In my previous comment, I meant installing JRE via distrib repository. I may be wrong but it seems to me that LO should be able to detect automatically Java after having cleaned LO profile (https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile). Anyway, let's reopen this one and see if someone may confirm the pb or not.
Thanks for your response. I installed the JRE by issuing the command line statement: sudo dnf install java-17-openjdk.x86_64 To be on the safe side, as I got a little confused about all that I've done to try to troubleshoot this, I restarted in Safe mode, selected Reset to factory settings and checked the two boxes beneath. Then applied and I restarted. I opened Tools->Options->Advanced and saw that LO had picked up my newly installed JRE. The vendor was listed as Red Hat, Inc and the version number is 17.0.5 I tried to copy some cells and closed Calc. Then I reopened Calc and the Crash dialog box appeared. In Comment 6 I expressed that I thought that this bug might be an issue with the Cinnamon desktop. So, I installed an XFCE desktop and tried to reproduce the bug. I was able to reproduce it repeatably. I haven't tried any other desktop. My guess is that we can eliminate any strangeness with the desktop as a cause. This may be out of bounds but would it be possible to try to engage the user who first reported it at bug 151673 (only a few months ago) and have that user try my simple test to see if he can reproduce the error? Just a thought.
Howard: thank you for this new feedback. So now, we're sure everything is ok about Java, we can move on. Carl: would it be possible you give a try to this one? Indeed, nobody could reproduce this one for the moment, it might be due to the fact that it would require a specific config.
Sorry about the delay. Holidays... Anyway, I am still on my Linux Mint 20.1 Mate edition machine, LO 7.4.2.3, and can now reliably reproduce the bug. If I open a spreadsheet, or csv file in Calc, and copy something, it doesn't matter if I paste it anywhere, the next time I open a spreadsheet I get the crash message. While a document is still open, if I open others I don't get the message. If I don't copy, but close all documents, then next time I open one, I don't get the message. If I open one, do nothing but highlight one cell and Ctrl-C, then close the document, the next time I open any LO document, I get the crash message.
No problem about the delay. You have just mirrored everything that I experienced. Since I am running with a Fedora base and you are using a Debian base it seems to be distribution agnostic. I will be upgrading my system to Fedora 37 sometime this weekend and that will probably update my desktop Cinnamon version. I will try LO again and if anything significant happens I'll report the results. I made a virtualbox stripped down version of my existing Fedora / Cinnamon setup and can reliably reproduce the bug so I can troubleshoot this with anyone who needs to. Alternatively, I can upload the virtual machine to anyone's site who wants it.
Can't reproduce with Fedora 36 and Cinnamon 5.2.7 and LO 7.3.7 (in a Quickemu VM): Version: 7.3.7.2 Build ID: 30(Build:2) CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But I can with the same and LO 7.4.3.2: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same crash signature: https://crashreport.libreoffice.org/stats/crash_details/51e2aff8-88ce-4cc3-b7f6-cf908e2aaf2d With stock GNOME 42.4, I can't reproduce: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded So seems DE-dependent.
I just finished installing different DE's on my virtual Fedora 36 installation and here is a summary of my results: I was able to reliably reproduce the bug on: Cinnamon 5.2.7 LXDE XFCE Deepin I was NOT able to reproduce the bug on: OpenBox KDE Plasma (X11) version 5.26.4 KDE Plasma (Wayland) version 5.26.4 GNOME Classic version 42.4 GNOME (X11) version 42.4 GNOME(Wayland) version 42.4 I also upgraded my system over the weekend to Fedora 37 which upgraded my Cinnamon version to Cinnamon 5.4.12 and the bug remains on that version as well. Hope this helps
I tried gtk and gen rendering and can't reproduce this. I don't have XFCE and LXDE, don't know Deepin and Cinnamon is specific Mint I think. => uncc myself.
The backtraces in comment #28 and comment #14 do look like the problem of bug 151673 which should have been fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=05b2bfc289df8712097cc1e640bf7d3bc6b86a84 to worth a retest I feel. If there is still a problem I would speculate its a clipboard management. The way cut and paste works generally is that an application doesn't really do anything when you "copy" into the clipboard except announce that there is something that can be got from the clipboard in various formats and only does something when you "paste" to provide the data in some specific format. This is great until you copy something into the clipboard, exit the app and then try and paste what you put into the clipboard. Traditionally what you wanted to paste is gone, because the providing app is gone. Nowadays when you exit the app after copying into the clipboard some part of the host desktop will query the clipboard and "paste" from it for some (or all) formats it provides and become a new clipboard provider. So there is a delicate time during app exit when it might be asked to honor its promise to provide copied data in a bunch of formats, some of which might not be asked for in routine cut and paste.
Howard, please test in a recent master build to see if it is not reproducible anymore: https://dev-builds.libreoffice.org/daily/master/current.html
(In reply to Stéphane Guillou (stragu) from comment #32) > Howard, please test in a recent master build to see if it is not > reproducible anymore: > https://dev-builds.libreoffice.org/daily/master/current.html Thanks for the effort. Unfortunately, the issue still remains. I have installed the version of LibreOffice that was suggested in comment #32 and it fails on the same desktops as before: Cinnamon LXDE XFCE I could not try Deepin due to technical difficulties with the desktop once it was launched. The following desktops were tried and as before there was no issue: OpenBox KDE Plasma (X11) GNOME Classic GNOME (X11) GNOME(Wayland)
Here is an update to the issue I originally reported. I have just upgraded my OS to Fedora 38 from Fedora 37. I still remain at the Cinnanon 5.6.8. desktop environment. As part of my upgrade I removed my prior version of LibreOffice(7.4.3.2) and installed the latest version available(7.5.3.2). I ran through a few tests and this os/desktop environment/LibreOffice version seems to have fixed the issue I originally reported. If nothing had been done to correct the problem then I suspect that the issue will pop up at some future time. However, for the time being, I am not seeing the issue. Thanks to all the people involved in bringing this issue to a successful completion.
This looks like a duplicate of bug 157042 *** This bug has been marked as a duplicate of bug 157042 ***
(In reply to Xisco Faulí from comment #35) > This looks like a duplicate of bug 157042 > > *** This bug has been marked as a duplicate of bug 157042 *** Actually the issue is fixed in LibreOffice 7.5.x because the problematic commit was reverted in that branch -> https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7-5&qt=grep&q=optimize+ConfigurationProperty%3A%3Aget() Putting it back to RESOLVED WORKSFORME