I've been updating my raspberry pi that is used to show a presentation soon as it boots up, to display some basic information on loop. I need to update past version 7.2.4 due to hitting another bug (#128715) that has been fixed where the presentation stops looping after short time on 32bit OSes I've installed a fresh copy of Raspbian Bullseye to make sure it's not a configuration change I've made. By default Raspbian/Debian Bullseye ships with 7.0.4 but this has the forementioned bug, so I've installed 7.4.5 from the bullseye backports. But now I've hit another problem. When I do the following command to start Impress `loimpress --nologo --show show.odp` Impress opens but the actual presentation looks to be started behind the current window or isn't quite visualable correctly. I can only see one entry on the LXDE taskbar. Pressing Alt+Tab shows the extra window for the actual presenting but selecting it doesn't always make it show. If I keep messing with Alt+Tab and clicking the Impress program, eventually it'll show the Presentation. Even if I wait 30 minutes without messing with Alt+Tab, it'll never show. If I open the file normally, then do start slideshow it runs as expected. OS: Raspbian Bullseye 32bit armhf Device: Raspberry Pi 3B
Thanks for the report. I could not reproduce on Ubuntu 20.04 with GNOME 3.36.8 and a single display. I tried LO 7.4.7, 7.5.5 and a recent master build at 24.2 alpha0+. Can you please: - update to 7.5.5 and see if you still have the issue - if so, share the whole version info from Help > About - possibly share an example document - and let us know if you have more than one display. Do you see the same problem when starting the presentation in app, with F5?
How do I install 7.5.5? I couldn't find arm builds of LibreOffice.
Hm looks like only sid has the most recent version: https://packages.debian.org/sid/libreoffice Unfortunately, 7.4 won't see further updates, and we don't provide armhf builds at TDF. Can you answer the other questions, and forget about an update for now?
I'll need to setup the environment again, I moved to arm64 and it solved the issue with LibreOffice I was having #128715. I may also try installing the backports like I mentioned on the arm64 to see if it's a 32bit/64bit thing.
Thank you, let us know how you go!
Dear FingerlessGloves, 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 FingerlessGloves, 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