Libreoffice Will Not Start as User, But Does as Root

English
#1

In CLI $ libreoffice – nothing. Just goes back to CLI. # libreoffice – starts just fine. I’ve deleted everything in my user directory related to LO, including ~/.config/libreoffice, but no change. Turned off selinux, no change. Tried $ libreoffice --safe-mode – same as normal, nothing.

rpm -qi libreoffice-writer

Name : libreoffice-writer
Epoch : 1
Version : 7.1.8.1
Release : 8.el9
Architecture: x86_64
Install Date: Tue 10 Jan 2023 02:57:28 PM PST
Group : Unspecified
Size : 11826878
License : (MPLv1.1 or LGPLv3+) and LGPLv3 and LGPLv2+ and BSD and (MPLv1.1 or GPLv2 or LGPLv2 or Netscape) and Public Doma
in and ASL 2.0 and MPLv2.0 and CC0
Signature : RSA/SHA256, Wed 16 Nov 2022 08:20:41 AM PST, Key ID 05b555b38483c65d
Source RPM : libreoffice-7.1.8.1-8.el9.src.rpm
Build Date : Thu 20 Oct 2022 10:40:19 AM PDT
Build Host : x86-03.stream.rdu2.redhat.com
Packager : builder AT centos.org
Vendor : CentOS
URL : libreoffice DOT org/
Summary : LibreOffice Word Processor Application
Description :
The LibreOffice Word Processor application.

Help gives me the help index, so I did this. As root it runs fine but the tools across the top are invisible. Running as a user it fails to run whether on writer, calc, base, etc.

#2

menu:Help>About…
Click the copy button near “Version information”, edit your original posting and paste.

#3

Please fix question tagging; base is for questions related to the database interface component. By using wrong tags, your question will not reach the competent contributors and may remained unanswered for a long time. Looks like a generic question, so correct tag is common.

#4

rpm {-q|–query} [select-options] [query-options]
May I ask, which options you selected and which not?

#5

ajlittoz: Ty

Villeroy: Just simply what I posted. -qi for query|info.

#6

Oh, sorry. I was too sure that -i means “install” and -qi “install with selectable options”. Well, the packager is cent.os. Are you sure that this package is prepared to run under your operating system?

#7

Sure. I’m running CentOS Stream 9.1, and I installed using the package manager. I tried to mark this with a Linux tag but it didn’t take.

I deinstalled, purged, deleted everything LibreOffice in my user account, but after reinstall this still happens. LibreOffice is freaky busted.

#8

The cent.os package seems to be busted.
Purge the package and try the rpms from Download LibreOffice | LibreOffice - Free Office Suite - Based on OpenOffice - Compatible with Microsoft
It installs to /opt with user profile in ~/.config/libreoffice/4/user/

#9

Thanks, but it works just as good as the distro version. No change.

Nightmare. What if root stops working?

Here’s the strace of the new version:

BTW: # rpm --import /home/bill/src/LibreOffice_7.4.4_Linux_x86-64_rpm.tar.gz.asc
error: /home/bill/src/LibreOffice_7.4.4_Linux_x86-64_rpm.tar.gz.asc: key 1 not an armored public key.

Edit: Ok this is getting creepy.

I created a new user, blank slate. He can run libreoffice just fine. So then I copied old user’s .local and .config dirs over to new user’s home dir and changed owner to new user. He could still run LO.
So then I copied over every single dir, complete, from old user to new user and changed owner. New user could STILL run LO but old user can’t.
How is this possible? Is LO prejudiced against old user?

#10

A user name with some special characters maybe? Non-UTF8 system encoding? Some bug with inability to access home directory?

#11

I don’t think anything inside LibreOffice checks for the actual user.
.
My best guess would be to check the security settings. I think SE-linux is active under CentOS. Maybe only new users get a current profile to be allowed to run LibreOffice.

#12

Whelp, it turns out that as I shut down the machine, a window in the back of everything… way in the back… was the document recovery dialog. It was there. It just didn’t show up in the Task Manager! When I rebooted LO now works like it should. I got my doc recovery and did that and now everything works.

Somehow that doc recovery ended up in back of everything (prob on last boot) -but- also decided to not appear in the Task Manager somehow.

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.