Description: BASIC Macros that invoke executuables via the shell function throw a "BASIC runtime error. File not found." Same macros work fine in the current (K)Ubuntu 7.3.7.2 package. (I haven't previously run LibreOffice as a snap or flatpak.) Steps to Reproduce: 1. Execute a macro with this shell command: shell("/usr/bin/konsole",2) 2. 3. Actual Results: Macro editor launches, highlighting the "shell" line of the macro, and a box shows the error message: BASIC runtime error. File not found. Expected Results: The software should have launched the desired application, in this case konsole (but, in my use case, a LibreOffice program). Reproducible: Always User Profile Reset: Yes Additional Info: I hope that, when Ubuntu ships 7.5, this will be gone. Maybe it's an artifact of using snap or flatpak -- something I haven't done with LibreOffice before. Best of luck, and thanks for all you do to make LibreOffice great!
Hi Steve, thanks for the report and the kind words! I can confirm that a macro of the type: Sub Main shell("/usr/bin/konsole",2) End Sub ... will run in LibreOffice installed from debs but gives a BASIC runtime error from the Snap. Rerpoduced with: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: 81bce3cd17f5e01886721863a4fa0d99f91033a6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I checked the permissions granted to the snap (everything allowed except for Bluetooth devices). snap version snap 2.58.2 snapd 2.58.2 series 16 ubuntu 20.04 kernel 5.15.0-67-generic As a workaround, please install from debs: https://www.libreoffice.org/download/download-libreoffice/ Similar issue on ask.libreoffice: https://ask.libreoffice.org/t/shell-function-crashes/43866
Dear Steve Sibelman, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug is still present in the latest *snap* of LibreOffice, v. 24.8.5.2, per my testing today. The E-mail I received 3/4/25 from the bugzilla-daemon asks me to verify whether it's a problem with the latest version from libreoffice.org, but that's irrelevant as this is an issue with the snap version. Or with snap itself. It seems likely this particular problem arises from the sandboxing/isolation that enclose snaps. Possibly, editing the "connections" of the libreoffice snap could resolve the problem. Sadly, I'm not knowledgeable in that area.