Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#58448 - libreoffice-fresh /usr/bin/oosplash: No such file or directory
Attached to Project:
Arch Linux
Opened by Simon Morris (bubba_169) - Friday, 04 May 2018, 06:58 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 08 May 2018, 13:34 GMT
Opened by Simon Morris (bubba_169) - Friday, 04 May 2018, 06:58 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 08 May 2018, 13:34 GMT
|
DetailsWith the latest updates I get /usr/bin/oosplash: No such file or directory when trying to launch libreoffice 6.0.3-2 from the command line. Libreoffice was installed using the libreoffice-fresh package from the repos and is running on KDE. The desktop icons do nothing. Using lowriter to launch writer works fine.
|
This task depends upon
Closed by Eli Schwartz (eschwartz)
Tuesday, 08 May 2018, 13:34 GMT
Reason for closing: Works for me
Additional comments about closing: OP request: "No longer happening after system reinstall"
Tuesday, 08 May 2018, 13:34 GMT
Reason for closing: Works for me
Additional comments about closing: OP request: "No longer happening after system reinstall"
All the entry points in /usr/bin for libreoffice do are re-execute /usr/lib/libreoffice/program/soffice
So lowriter would be the same as libreoffice --writer, which, both of them run the "soffice" shellscript wrapper which itself just fancily invokes oosplash. So I don't know why this would fix anything.
But... Libreoffice opens just fine for me. I don't know why it would be looking in /usr/bin for you. *Unless* you're not using the packaged files. If the libreoffice wrapper you're using is running "soffice" from /usr/bin instead of /usr/lib/libreoffice/ then it would try to find oosplash in /usr/bin too. Which is obviously an issue.
Thanks for your comment though eschwartz. I feel like I've learned something :)