Description: Attempting to install LibreOffice 7.1 on Ubuntu 20.04 fails when processing ibobasis7.1-images_7.1.0.2-2_amd64.deb, hanging my computer, rendering it unusable (even after waiting an hour) and requiring a hard reboot. Steps to Reproduce: 1. On Ubuntu 20.04, downloaded and extract LibreOffice_7.1.0.2_Linux_x86-64_deb.tar.gz. 2. Follow the installation instructions in its readme file: go to the DEBS subdirectory and run: dpkg -i *.deb Actual Results: The dpkg output looked plausible for libobasis7.1-base to libobasis7.1-graphicfilter, but when processing libobasis7.1-images_7.1.0.2-2_amd64.deb, dpkg hung, and took most of the rest of my OS down with it. I could still use my Window manager to switch to other applications, but doing things (like running programmes at a shell prompt, loading a new webpage in Firefox, or reading an email in Mutt) just hung, too. At the shell running dpkg, Ctrl+C didn't do anything, and Ctrl+Z didn't give a prompt either. Nor did Ctrl+Alt+F1 react. To be able to use my computer again, I had to first shut it down by holding down the power button. Expected Results: libobasis7.1-images_7.1.0.2-2_amd64.deb installs, and dpkg continues on to libobasis7.1-impress. Or it fails and gives an error message. Reproducible: Always User Profile Reset: No Additional Info: This was repeatable. I initially wondered if it was insufficient disk space, so freed up several Gb, but it did it again. It's now hung on me 4 times, always at the the -images deb.
Did you download deb.tar.gz from tdf ? (see https://dev-builds.libreoffice.org/pre-releases/deb/x86_64/) Did you check hash of the file corresponded?
Sorry, I don't know what ‘tdf’ is. I downloaded it from the page that's linked to by the ‘RC2 is available’ promo that's currently at the top of this bugs page, clicking on the ‘Download Version 7.1.0’ button. That's currently linking to https://www.libreoffice.org/donate/dl/deb-x86_64/7.1.0/en-GB/LibreOffice_7.1.0.2_Linux_x86-64_deb.tar.gz Though my Firefox history claims it was actually downloaded from: https://mirrors.ukfast.co.uk/sites/documentfoundation.org/tdf/libreoffice/_testing_/7.1.0/deb/x86_64/LibreOffice_7.1.0.2_Linux_x86-64_deb.tar.gz sha256sum reports 58ee5bfd8265c7fcfb9f39929077d6672261d37b4896ce19184c00bf4a2a0da6, which matches the value shown on the page linked from ‘info’ under the download button.
Thank you for your quick feedback. Sorry about "tdf", it means "The Document Foundation" (official devs of LibreOffice, see https://en.wikipedia.org/wiki/The_Document_Foundation). René: even if the user is on Ubuntu, as deb expert, any thoughts/hints here?
Did you try later with new LO version?
Dear Smylers, 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 Smylers, 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