Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] LibreOffice crashes on startup on Debian Buster

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
abhikpal
Posts: 6
Joined: 2016-08-30 08:29

[SOLVED] LibreOffice crashes on startup on Debian Buster

#1 Post by abhikpal »

Hi,

I'm having some issues with LibreOffice (Build ID: 1:6.1.5-3+deb10u3)
on Debian Buster.

Code: Select all

$ uname -a
Linux euler 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux
In particular:

- Writer, Impress, Draw crash immediately on opening and I get the
"Document recovery dialog."

- Calc opens but crashes the moment I try to insert text.

Some meta-info:

- I upgraded to Debian Buster when it came out. Previously I was on
stretch (stable with backported kernel) and these issues were not
present.

- I have currently resolved to using the AppImage from the LibreOffice
website. The issues are not present there.

Debugging I have done so far:

- Created a new user test account to debug, the issue is not present
in the new account.

- Reset my LibreOffice profile (from my own account).

- Tried disabling hardware acceleration.

- Tried disabling Java (as recommended here:
https://ask.libreoffice.org/en/question ... r-crashes/
and here:
https://askubuntu.com/questions/927859/ ... s-on-start).
This did not solve the issue.

- libreoffice-gtk2 isn't installed on my system so the solution
described here:
https://ask.libreoffice.org/en/question ... 90-solved/
doesn't apply.

- running libreoffice in safemode and resetting the profile doesn't
help. Here's the output I see on the terminal:

Code: Select all

$ libreoffice --safe-mode
Warning: failed to read path from javaldx
xkbcommon: ERROR: Key "<LFSH>" added to modifier map for multiple modifiers; Using Lock, ignoring Shift
Application Error
- the issue seems similar to
https://ask.libreoffice.org/en/question ... -on-linux/
however, no solution is provided on that thread.


As a workaround, I am currently using the AppImage version from the
LibreOffice website which doesn't have any of the aforementioned
issues.

How do I further debug this issue? If it's being caused only on my
user account how do I isolate the source of the error? If requested, I
can post more debugging info.

Any help would be appreciated! Thanks for taking the time to help :)
Last edited by abhikpal on 2019-11-11 22:51, edited 1 time in total.

User avatar
ruwolf
Posts: 632
Joined: 2008-02-18 05:04
Location: Banovce nad Bebravou
Has thanked: 39 times
Been thanked: 28 times

Re: LibreOffice crashes on startup on Debian Buster

#2 Post by ruwolf »

Does the new (functional for LibreOffice) user use the same keyboard configuration as the old (crashing LibreOffice) user?

User avatar
pylkko
Posts: 1802
Joined: 2014-11-06 19:02

Re: LibreOffice crashes on startup on Debian Buster

#3 Post by pylkko »

What java engine or development kit are you using? How did you install LibreOffice? Have you thereafter uninstalled java?

What happens if you try to reinstall the metapackage that should try to pull all the dependancies?

Code: Select all

sudo apt -y install libreoffice

abhikpal
Posts: 6
Joined: 2016-08-30 08:29

Re: LibreOffice crashes on startup on Debian Buster

#4 Post by abhikpal »

Sorry for ghosting this thread. I didn't get the time to look into this more. I recently did fresh install of debian but the issue persists. Libre office worked right after installation but now that I have installed other software I need, the same issue has popped up.
Does the new (functional for LibreOffice) user use the same keyboard configuration as the old (crashing LibreOffice) user?
Yes. Both use the keyboard layout "English (US)"
What java engine or development kit are you using? How did you install LibreOffice? Have you thereafter uninstalled java?
I am using the libreoffice that came pre-installed with debian and I have not done anything (manually) to my java config. Here's the version details:

Code: Select all

java -version
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment (build 11.0.5+10-post-Debian-1deb10u1)
OpenJDK 64-Bit Server VM (build 11.0.5+10-post-Debian-1deb10u1, mixed mode, sharing)
What happens if you try to reinstall the metapackage that should try to pull all the dependancies?
I tried that on my older installation, but that doesn't resolve the issue. I really think it's an issue with my particular (user-level) configuration as Libre Office seems to work fine when I create a new user.

User avatar
sunrat
Administrator
Administrator
Posts: 6437
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 467 times

Re: LibreOffice crashes on startup on Debian Buster

#5 Post by sunrat »

abhikpal wrote:
What happens if you try to reinstall the metapackage that should try to pull all the dependancies?
I tried that on my older installation, but that doesn't resolve the issue. I really think it's an issue with my particular (user-level) configuration as Libre Office seems to work fine when I create a new user.
How did you remove it? To remove configuration files:

Code: Select all

apt purge libreoffice*
If you don't use purge, config files are retained which may be the source of your issue.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

abhikpal
Posts: 6
Joined: 2016-08-30 08:29

Re: LibreOffice crashes on startup on Debian Buster

#6 Post by abhikpal »

How did you remove it? To remove configuration files:
Oh, should have clarified. By "older installation" I meant the installation I had before wiping my computer entirely. The new installation is my new debian installation and I hadn't changed any libreoffice configuration. Moreover, running

Code: Select all

    apt purge libreoffice*
tries to remove packages like gnome so I am reluctant of running it.

abhikpal
Posts: 6
Joined: 2016-08-30 08:29

Re: LibreOffice crashes on startup on Debian Buster

#7 Post by abhikpal »

After some digging around I managed to resolve my issue. Posting it here to document it. Relevant information: I use zsh and the anaconda python distribution. So in my shell config I modify the path to point to the anaconda's python interpreter instead of the default python. The precise issue was that I had accidentally set the path in my .zprofile instead of .zshrc and hence libreoffice was trying to use the anaconda's python interpreter. I discovered the issue by looking at /var/log/messages and noticed logs of the form:

Code: Select all

Nov 12 00:30:39 hostname kernel: [26175.151824] audit: type=1400 audit(1573515039.345:361): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/encodings/__pycache__/__init__.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.152050] audit: type=1400 audit(1573515039.345:362): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/__pycache__/codecs.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.152719] audit: type=1400 audit(1573515039.345:363): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/encodings/__pycache__/aliases.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.153029] audit: type=1400 audit(1573515039.345:364): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/encodings/__pycache__/utf_8.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.153547] audit: type=1400 audit(1573515039.349:365): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/encodings/__pycache__/latin_1.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.153837] audit: type=1400 audit(1573515039.349:366): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/__pycache__/io.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.154014] audit: type=1400 audit(1573515039.349:367): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/__pycache__/abc.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.154509] audit: type=1400 audit(1573515039.349:368): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/__pycache__/_bootlocale.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.154837] audit: type=1400 audit(1573515039.349:369): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/__pycache__/site.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 12 00:30:39 hostname kernel: [26175.155081] audit: type=1400 audit(1573515039.349:370): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/username/.bin/anaconda3/lib/python3.7/__pycache__/os.cpython-37.pyc" pid=20503 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
The issue was fixed by moving the offending path modification from .zprofile to .zshrc.

Post Reply