[SOLVED] libreoffice fails to start on a -current clean install
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Alienbob's LibreOffice is not your only option, if you really need it working as soon as possible you could also install from SBo (both binary and source options available).
That said, the new libreoffice packages from Alienbob's repo fixed all the startup/saving problems here (including saving .docx).
Thanks, I've considered that option and downloaded some debs and rpms. Eventually I'll use Ponce's slackbuilds. But for now, calligra is enough. This is something related with mesa. glxgears displays fine, but vkcube (vulkan) spins like crazy. Maybe I enabled/disabled something in the bios when I did a fresh install to an SSD. The desktop is quite old but already supports EFI (so it's not that old). I'll investigate this in my spare time. I'm now at home in a similar desktop that has been upgraded up to the version of -current from 2020/12/8 and libreoffice is working fine...
The new AlienBob packages are working fine here! I've removed raptor2, rasqal and redland. I also removed the icu4c-compat packages and reinstalled slackware's icu4c package (IMPORTANT, I think) before upgrading Libreoffice.
The new AlienBob packages are working fine here! I've removed raptor2, rasqal and redland.
Same here. All is well
Quote:
I also removed the icu4c-compat packages and reinstalled slackware's icu4c package (IMPORTANT, I think) before upgrading Libreoffice.
This is did not do. I am fairly certain that the icu4c-compat package is suppose to be installed in conjunction with the Slackware icu4c package, at least that is what I am doing. In general I leave the icu4c-compat package installed until all of my packages are rebuilt and it's no longer needed.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,070
Rep:
Quote:
Originally Posted by chrisretusn
I am fairly certain that the icu4c-compat package is suppose to be installed in conjunction with the Slackware icu4c package, at least that is what I am doing. In general I leave the icu4c-compat package installed until all of my packages are rebuilt and it's no longer needed.
That's how I handle it too, as per Eric's original instructions:
Quote:
And in the special case of incompatible icu4c, boost and poppler updates, the easiest (short-term) workaround is to install my icu4c-compat, boost-compat and poppler-compat packages. Essentially, these convenience packages wrap the libraries of several older (original Slackware) icu4c, boost and poppler packages.
Applications that depend on these older libraries will keep on running and in the meantime you can wait for the 3rd-party packager to recompile the affected packages (or recompile yourself at your leisure). I update these packages immediately after updates to their Slackware originals. The process takes almost no time, compared with recompiling all the broken stuff.
NOTE: These ‘compat’ packages do not replace Slackware’s own icu4c, boost and poppler packages! They should be installed in parallel.
This is did not do. I am fairly certain that the icu4c-compat package is suppose to be installed in conjunction with the Slackware icu4c package, at least that is what I am doing. In general I leave the icu4c-compat package installed until all of my packages are rebuilt and it's no longer needed.
Yes, you are quite right! I had a momentary brain fade due to Eric's naming of his compat package, and assumed that it included the current slackware libraries, too. It doesn't, and it is not necessary to re-install icu4c.
I've now removed the compat packages as I don't have anything else that depends on them. At least, not that I've found so far...!
Yes, you are quite right! I had a momentary brain fade due to Eric's naming of his compat package, and assumed that it included the current slackware libraries, too. It doesn't, and it is not necessary to re-install icu4c.
I've now removed the compat packages as I don't have anything else that depends on them. At least, not that I've found so far...!
--
Pete
As interesting as it could be, none of that solves my problem! I'm starting to believe that this is a "corner case", probably related to my hardware. Today I've reinstalled slackware -current without multilib (so a clean install). Next, I installed the new libreoffice from AlienBob, but the result is the same: "Application Error". Interestingly, running libreoffice from the console but after su (so, as root) results in
Alienbob's LibreOffice is not your only option, if you really need it working as soon as possible you could also install from SBo (both binary and source options available).
I know. The difference is that on SBos (either Ponce's or 14.2) libreoffice is at version 6, while AlienBob's is on v7. Still, I may try to build libreoffice using SlackBuilds just because... It shouldn't take that long, because technically it's not a full building but just a repackaging of the original binaries. I really hate to fail to understand when something breaks, especially because this only happens in a particular machine. At my home desktop (which is where most of my work is done due to COVID19) everything seems to be OK. Even on a small laptop that I use frequently when in transit (an 13'' Asus VivoBook with a touch screen) everything is working. One may be tempted to attribute the failure to something left from older installations, but that is not the case as I've reinstalled everything on a different medium (an SSD, initially it was an HDD).
I know. The difference is that on SBos (either Ponce's or 14.2) libreoffice is at version 6, while AlienBob's is on v7. Still, I may try to build libreoffice using SlackBuilds just because... It shouldn't take that long, because technically it's not a full building but just a repackaging of the original binaries.
The idea was if you were desperate to have an office suite working ASAP then "libreoffice" from SBo (i.e., the upstream binary repackaging) should just work. There is also "LibreOffice" on SBo if you wanted to build from source (but yes, version 6 also).
As interesting as it could be, none of that solves my problem! I'm starting to believe that this is a "corner case", probably related to my hardware. Today I've reinstalled slackware -current without multilib (so a clean install). Next, I installed the new libreoffice from AlienBob, but the result is the same: "Application Error".
Could you try creating a fresh new user account for testing? Login as that new user, run libreoffice and see what happens? In the OpenOffice past I've had to delete my application profile on numerous occasions to deal with application crashes; LibreOffice has improved in this area but that does not mean this can still be a local profile issue.
Quote:
Interestingly, running libreoffice from the console but after su (so, as root) results in
The added GTK-related messages could be caused by the fact that you are running this as root and not as the normal user. I would not be worried about them.
Could you try creating a fresh new user account for testing? Login as that new user, run libreoffice and see what happens? In the OpenOffice past I've had to delete my application profile on numerous occasions to deal with application crashes; LibreOffice has improved in this area but that does not mean this can still be a local profile issue.
The added GTK-related messages could be caused by the fact that you are running this as root and not as the normal user. I would not be worried about them.
Thanks! I didn't know about the issue between gtk/root as I don't run anything graphics as root. It's good to know that I shouldn't follow that line of research. So gtk stuff is eliminated. I've tried everything: removing ./config/libreoffice, creating a fresh account, reinstalling -current without multilib. In any case libreoffice always failed with the same terse error. Using gdb I could trace problems up to gallium and iris (mesa stuff related to the intel GPU, it's a HD630 in a Core-5 7400). Libreoffice uses OpenCL, but since it doesn't start I can't disable graphics acceleration on it.
After the weekend I'll try to downgrade libreoffice to version 6 (in SlackBuilds) and see what happens!
Quote:
Originally Posted by drgibbon
The idea was if you were desperate to have an office suite working ASAP then "libreoffice" from SBo (i.e., the upstream binary repackaging) should just work. There is also "LibreOffice" on SBo if you wanted to build from source (but yes, version 6 also).
Thanks drgibbon for trying to help! I'm desperate to understand what is going on, not so much running libreoffice itself, as I can do without it (and use calligra). Still, as stated above, I'll try to install libreoffice v6 on Monday to see what happens. I'm curios about the reasons behind such strange behavior. I run slackware on all computers (even kids' and wife's laptops) and I only observed this problem on this particular machine.
Interestingly, while trying to understand this problem, I came across a discussion about Electromagnetic interference on PCs resulting from poorly shielded audio circuits on the motherboard. In this particular desktop the integrated graphics is generating noise in the speakers/headphones. Moving windows around, scrolling or hovering browsers URLs with the mouse is accompanied by white noise!
thanks alienBob,
with a new or existing user i am getting the below on clean slackware64-current, nothing urgent, LibreOffice works on 14.2 and apparently for many on current too
maybe kde is up to something
Code:
$libreoffice
(soffice:22089): Gtk-WARNING **: 14:16:26.502: Theme parsing error: gtk.css:3:33: Failed to import: Error opening file /home/user/.config/gtk-3.0/window_decorations.css: No such file or directory
(soffice:22109): Gtk-WARNING **: 14:16:27.370: Theme parsing error: gtk.css:3:33: Failed to import: Error opening file /home/user/.config/gtk-3.0/window_decorations.css: No such file or directory
Application Error
$libreoffice
(soffice:22089): Gtk-WARNING **: 14:16:26.502: Theme parsing error: gtk.css:3:33: Failed to import: Error opening file /home/user/.config/gtk-3.0/window_decorations.css: No such file or directory
(soffice:22109): Gtk-WARNING **: 14:16:27.370: Theme parsing error: gtk.css:3:33: Failed to import: Error opening file /home/user/.config/gtk-3.0/window_decorations.css: No such file or directory
Application Error
Is kde-gtk-config installed? Since that package include that missing .css file, it might be worth a try re-install/install it?
And see if it's found here usr/share/themes/Breeze/window_decorations.css
thanks MDKIO, yes kde-gtk was installed
i just re-installed the package kde-gtk-config-5.20.4-x86_64-1 and copied over the file you indicated usr/share/themes/Breeze/window_decorations.css to the ~/.config/gtk-3.0/ directory the .css error has disappeared which is nice.
Quote:
$libreoffice
Application Error
must be something wrong on this setup, will study further later
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
