Hello @ll, we got a report on the de@discuss list, which seems to be reproducible on GNU/Linux (or better: Debian-based systems). I have also reported it to our QA list, where it was confirmed as well (see https://lists.freedesktop.org/archives/libreoffice-qa/2016-May/009589.html and its follow-ups) ... ;) Steps to reproduce: 1. download https://media-cdn.ubuntu-de.org/forum/attachments/41/20/8285598-no-border-no-nation.ods 2. open it in Calc 3. click on the image to get the handler 4. drag the right bottom handler to resize it. On my system (Debian Testing AMD64), this leads nearly immediately to a system freeze, where I have to switch to a VT to kill the soffice.bin ... :( The problem is, that still after killing the process with "kill -9 $PID" the system will not free the whole RAM / swap / whatever, so the system still seems to be blocking somewhere ... :( So be warned ... ;) Tested with: LO Version: 4.3.7.2 Build-ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba (no freeze, but I was only able to resize the image at the right handler. All others leads to a vanishing image) Version: 4.4.1.2 Build-ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Gebietsschema: de_DE (same as 4.3.7.2) Version: 4.4.6.2 Build-ID: 008d5d0ddffba0b82de2a2c36a65b9cba0a6b328 Gebietsschema: de_DE.UTF-8 (freeze) Version: 5.0.0.5 Build-ID: 437e4abdf9e72fd0a6e6f8697a0e659bc77f9b10 Gebietsschema: de-DE (de_DE.UTF-8) (freeze) Version: 5.0.6.3 Build-ID: 490fc03b25318460cfc54456516ea2519c11d1aa Gebietsschema: de-DE (de_DE.UTF-8) These are the versions, which I have installed parallel to Debian's own version (following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel/Linux) Additionally, I tested it with Debian's own version Version: 5.1.3.2 Build-ID: 1:5.1.3-1 CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; Gebietsschema: de-DE (de_DE.UTF-8) , which also nearly freezes the whole system ... :( I then tried to get a backtrace or even a strace, but alas to no avail ... :( IMHO this freezes the system much harder than without them ... :( Sorry for the inconvenience and have a nice evening Thomas.
I Can't reproduce Win10x64 Version: 5.1.3.2 (x64) Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Please test enable/disable Menu/Tools/Options/LibreOffice/View - Graphics Output -> Use OpenGL for ...
Hello m.a.riosv, *, (In reply to m.a.riosv from comment #1) > I Can't reproduce Win10x64 > Version: 5.1.3.2 (x64) > Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b > CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; sorry, forgot to change the hardware entries ... :( > Please test enable/disable > Menu/Tools/Options/LibreOffice/View - Graphics Output -> Use OpenGL for ... Debian's Version (5.1.3.2) has the first OpenGL option (Use OpenGL for all rendering) enabled, all parallel installed versions not. It seems, that this option is not the culprit, or what do you think? Should I retest it with disabled/enabled option? Do you need some more information? If so, feel free to ask :) Have a nice day Thomas.
I confirm the same hard freeze using the test document provided by the reporter, thackert@nexgo.de with LibreOffice Versión: 5.1.3.2 Id. de compilación: 644e4637d1d8544fd9f56425bd6cec110e49301b on Debian 8.4 x64 derivative MX-Linux.
Note: the version I used was downloaded directly from LibreOffice. It is not the Debian provided backport.
Hello Richard, *, (In reply to Richard from comment #3) > I confirm the same hard freeze using the test document > provided by the reporter, thackert@nexgo.de > with LibreOffice Versión: 5.1.3.2 > Id. de compilación: 644e4637d1d8544fd9f56425bd6cec110e49301b > on Debian 8.4 x64 derivative MX-Linux. thanks for confirming :) As you have confirmed this bug, I hope it is OK to set its status to new. If not, feel free to change it to something else ... ;) Have a nice afternoon Thomas.
Tried again on LibO-5.1.4.2_x64 release direct from LibO site, installed on Debian 8.5 base x64 with Xfce4.12.2 with similar result: Moving the bottom right corner of the image in the test document: https://media-cdn.ubuntu-de.org/forum/attachments/41/20/8285598-no-border-no-nation.ods froze up my system --couldn't get to another tty, mouse moved but no reponse, could not change to another app nor were there any other indications of activity. Rebooted with Ctrl-RSEISUB.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear *, (In reply to QA Administrators from comment #7) <snip> > If the bug is present, please leave a comment that includes the information > from Help - About LibreOffice. thank you very much for the reminder, but - alas - this bug is still reproducible with OS: Debian Testing AMD64 LO: Version: 6.1.0.2 Build-ID: b3972dcf1284967612d5ee04fea9d15bcf0cc106 CPU-Threads: 4; BS: Linux 4.16; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded Sorry for not testing it with other LO versions like master or so, but I have not enough time at the moment to restart my system again ... :( HTH Thomas.
We can confirm this bug on two different systems. Both are running very recently updated Arch Linux. System 1: workstation, 64 GB ram libreoffice-still 6.1.6-1 Linux 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux System 2: Thinkpad laptop, 16 GB ram libreoffice-still 6.1.5-5 Linux 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux Reproducibility: 100% The steps to reproduce are the same as OP. Resizing a PNG or JPG image by dragging image handles results in instant system freeze. On single CPU laptop, the only way to recover is to restart the whole system. On multi-CPU workstation, we can kill soffice.bin. Temporary workaround we found: anchor image to cell, and resize using "fit to cell".
In our testing, this doesn't affect just resizing of "a special image." We are seeing this upon dragging resize handles for all png or jpg images, and it happens 100% of the time.
Dear Thomas Hackert, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I can't confirm it on LO 7.4.2.3 in LXLE (x64) Focal distro. I resized the image without any hangs or crash. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 1; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.20.04.1~lo1 Calc: threaded
No freeze for me either. As the last reproduction was in 2019, let's close. If someone can still repro with 7.4, this can be set back to NEW.