Writer closes when finished loading without error

Bug #1704893 reported by Sondra Kinsey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I attempt to open a document in LibreOffice Writer, by any method, I am shown a loading dialog with a progress bar. The progress bar advances to about 95%, then disappears, and nothing happens.

I have tried launching LibreOffice Writer by several methods:
- Start LibreOffice, click "Create/Writer Document"
- Open a filetype associated with LibreOffice Writer in a file browser
- Launch libreoffice --writer in a terminal (This outputs nothing)

I have confirmed via ps -A that LibreOffice is truly closed, and not merely invisible.

Things I tried, with no difference:
- sudo apt-get install --reinstall libreoffice-writer
- rm ~/.config/libreoffice
- cp -a /usr/lib/libreoffice/share ~/.config/libreoffice/4/user

This is a fresh install of LibreOffice on a fresh install of Lubuntu.

Other LibreOffice applications, such as Calc, work fine.

I believe the same problem may have been reported at
- https://askubuntu.com/questions/129383/libreoffice-not-opening
- https://askubuntu.com/questions/697309/unable-to-open-libreoffice-writer?rq=1
Nothing there helped me.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libreoffice-writer 1:5.3.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: i386
CurrentDesktop: LXDE
Date: Mon Jul 17 20:22:50 2017
InstallationDate: Installed on 2017-07-05 (12 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sondra Kinsey (sondra.kinsey) wrote :
Revision history for this message
dino99 (9d9) wrote :
Changed in libreoffice (Ubuntu):
status: New → Invalid
Revision history for this message
Sondra Kinsey (sondra.kinsey) wrote :

I can reproduce this bug on Ubuntu 16.04.3 LTS and libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2.
Ubuntu 16.04.3 doesn't reach end of life until April 2021
https://wiki.ubuntu.com/Releases
https://www.ubuntu.com/info/release-end-of-life

Changed in libreoffice (Ubuntu):
status: Invalid → New
Revision history for this message
dino99 (9d9) wrote :

The JournalErrors.txt above have lot of "xfce4-notifyd[6564]: Theme parsing error: gtk-widgets.css"

is it still happening ?

When you said 'fresh install' does that mean you are not reusing a shared old /home which can contain old borked settings ?

Have you added external sources / custom settings ?

Note that no one else have met that issue on launchpad; so something is unusual on your installion.

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Revision history for this message
Olivier Tilloy (osomon) wrote :

@Sondra: is this problem still happening? Or have you managed to get libreoffice writer to start?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]

Changed in libreoffice (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Sondra Kinsey (sondra.kinsey) wrote :

@Olivier Tilloy: I continue to experience this problem on various systems. It's been a while since I tested with fresh installations, and I _was_ preserving various ~/.config files between those. I did not, however, preserve anything in ~/.config/libreoffice, and removing this directory has no effect.

The gtk theme warnings show up for virtually all GTK apps and have to do with obsolete features of the GTK theme. They don't cause problems for any other app and I don't think they're the problem since I just crashed LibreOffice again using this command:
    GTK_THEME=adwaita libreoffice testfile.docx
with LibreOffice 5.4.6.2 40m0(Build:2) on Lubuntu 17.10.

Changed in libreoffice (Ubuntu):
status: Expired → New
Revision history for this message
Olivier Tilloy (osomon) wrote :

@Sondra: can you please try the following? From a terminal, run `libreoffice --writer --backtrace`.

Once the crash happens, you should see a (gdb) prompt, please type "t a a bt" and share the output here. Thanks!

Revision history for this message
Sondra Kinsey (sondra.kinsey) wrote :

The attached file is the result of running this command:
$ rm -Rf ~/.config/libreoffice; libreoffice --calc --backtrace; rm -Rf ~/.config/libreoffice; libreoffice --help --backtrace

$ libreoffice --help results in this output:
terminate called after throwing an instance of 'com::sun::star::uno::DeploymentException'
$ libreoffice --calc results in this output:
I18N: Operating system doesn't support locale ""
I18N: Operating system doesn't support locale "en_US"
Fatal exception: Signal 11
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f85d1385568]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c5d6)[0x7f85d13ae5d6]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f85d0fbff20]
/usr/lib/libreoffice/program/libuno_cppu.so.3(uno_type_any_assign+0x705)[0x7f85ca666dc5]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2948148)[0x7f85d3f14148]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2948eea)[0x7f85d3f14eea]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0xcb)[0x7f85d3f0947b]
/usr/lib/libreoffice/program/libmergedlo.so(+0x29a1d95)[0x7f85d3f6dd95]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x125)[0x7f85d3f6f345]
/usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x1a0)[0x7f85d42bba00]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cf11dd)[0x7f85d42bd1dd]
/usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f85d42bd240]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f85d3301fe5]
/usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560ecfdc278b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f85d0fa2b97]
/usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560ecfdc27ca]

## Environment Info
$ apt show libreoffice-calc |grep -i Version
Version: 1:6.0.7-0ubuntu0.18.04.10
$ lsb_release -d
Description: Ubuntu 18.04.3 LTS
$ java --version
openjdk 11.0.6 2020-01-14
OpenJDK Runtime Environment (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1, mixed mode, sharing)

Revision history for this message
Sondra Kinsey (sondra.kinsey) wrote :

I have the same results after upgrading via the libroffice ppa

$ apt show libreoffice-calc |grep -i Version
Version: 1:6.3.5~rc2-0ubuntu0.18.04.1~lo1
$ unopkg --version
unopkg Version 3.3
$ libreoffice --version
terminate called after throwing an instance of 'com::sun::star::uno::DeploymentException'
$ libreoffice --help
terminate called after throwing an instance of 'com::sun::star::uno::DeploymentException'

Revision history for this message
Sondra Kinsey (sondra.kinsey) wrote :
Download full text (30.8 KiB)

Reading back through this thread just now makes me realize that I may have conflated two different bugs. My initial report was that Writer alone was not working, now I can't get any part of LibreOffice working.

Some internet searching suggests my current bug was reported elsewhere:
* https://askubuntu.com/q/1212480/396228
* https://bugs.archlinux.org/task/61701 - This one was resolved by deleting ~/.config/libreoffice

The Ask Ubuntu question indicates that it may have to do with AppArmor.

Here's dmesg output after running soffice --version

[98292.382412] audit: type=1400 audit(1585057205.348:220): apparmor="ALLOWED" operation="open" info="Failed name lookup - disconnected path" error=-13 profile="libreoffice-soffice" name="upper/usr/lib/libreoffice/program/services" pid=15308 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=999 ouid=0
[98292.387909] audit: type=1400 audit(1585057205.352:221): apparmor="ALLOWED" operation="open" info="Failed name lookup - disconnected path" error=-13 profile="libreoffice-soffice" name="usr/share/drirc.d" pid=15309 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=999 ouid=0
[98292.389480] audit: type=1400 audit(1585057205.356:222): apparmor="ALLOWED" operation="open" info="Failed name lookup - disconnected path" error=-13 profile="libreoffice-soffice" name="usr/share/drirc.d" pid=15309 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=999 ouid=0
[98292.396759] audit: type=1400 audit(1585057205.360:223): apparmor="ALLOWED" operation="open" info="Failed name lookup - disconnected path" error=-13 profile="libreoffice-soffice" name="usr/share/drirc.d" pid=15309 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=999 ouid=0
[98292.396768] audit: type=1400 audit(1585057205.360:224): apparmor="ALLOWED" operation="open" info="Failed name lookup - disconnected path" error=-13 profile="libreoffice-soffice" name="usr/share/drirc.d" pid=15309 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=999 ouid=0
[98292.403985] audit: type=1400 audit(1585057205.368:225): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/lubuntu/.cache/mesa_shader_cache/index" pid=15309 comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=999 ouid=999
[98292.407321] audit: type=1400 audit(1585057205.372:226): apparmor="ALLOWED" operation="open" info="Failed name lookup - disconnected path" error=-13 profile="libreoffice-soffice" name="usr/share/drirc.d" pid=15309 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=999 ouid=0

$ strace soffice --version
execve("/usr/bin/soffice", ["soffice", "--version"], 0x7ffe4bddfd48 /* 58 vars */) = 0
brk(NULL) = 0x5576089d2000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=92180, ...}) = 0
mmap(NULL, 92180, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7eff60264000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.