LO just bails/crashes on launch

[kevin gunn]

using puritine2 click, with latest ubuntu-pd, LO launch displays a window briefly and then exits(crashes?) immediately

[Christopher Townsend (townsend)]

Kevin,

Could you please attach ~/.cache/upstart/application-legacy-puritine_libreoffice-startcenter_0.0-.log?

Thanks!

[Christopher Townsend (townsend)]

Hmm, this is happening on my phone now too. According to the logs, this is why it's failing:

/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory

libGL.so.1 is in the libgl1-mesa-glx package which is installed in the chroot. I then run 'ldconfig.real -p | grep libGL.so.1' and it doesn't list it. So I try to run ldconfig.real and it still doesn't work.

Not sure what is going on and why this has changed...

[Christopher Townsend (townsend)]

My puritine chroot was hosed, so I reinstalled the click and still see this libGL.so error.

I fixed this by doing "sudo proot -S ~/.cache/libertine-container/puritine/rootfs ldconfig.real -f /usr/lib/arm-linux-gnueabihf/mesa/ld.so.conf", but now I see a different error:

[Java framework] Error in function createSettingsDocument (elements.cxx).^M
javaldx failed!^M
Warning: failed to read path from javaldx^M

I know this stuff worked before and the puritine 0.2 click has not changed in some time, so I'm unsure of what has changed.

[Will Cooke (willcooke)]

Subscribing Bjoern to see if he has any ideas for troubleshooting. Please reach out to me or him if we can help.

[Björn Michaelsen (bjoern-michaelsen)]

a/ What build of LibreOffice is this? What was the last version that worked?
b/ The Java stuff is likely a red herring.
c/ Just a note to be aware: LibreOffice can do quite a bit of dlopen'ing ...

[Björn Michaelsen (bjoern-michaelsen)]

Ah, one more tip: Try setting the "SAL_USE_VCLPLUGIN" env var to "gen" to see if it help (this forces LibreOffice to ignore the gtk plugin and uses the old and trusty X11-only backend.

[kevin gunn (kgunn72)]

wanted to answer bjoern to the best of my ability
a) the LO used is equivalent to what it is in the vivid archive - Chris said he's seen it work, I've actually never seen it launch/work on ARM.

so this is interesting using SAL_USE_VCLPLUGIN=gen actually allowed the LO splash to display for just a second, then bailed.

Is there a particular log i can look up to see where it's bailing ?

[Björn Michaelsen (bjoern-michaelsen)]

@kevin: please provide an exact package version. e.g. even on vivid we released with 1:4.4.2-0ubuntu1 but (security)-updated to 1:4.4.6~rc3-0ubuntu1

As for logs, both:

> strace /usr/lib/libreoffice/program/soffice.bin

and installing libreoffice-dbg and running /usr/lib/libreoffice/program/soffice.bin under gdb and providing a backtrace would be helpful.

[kevin gunn (kgunn72)]

also here's the full log from that attempt.

[kevin gunn (kgunn72)]

before i forget confirmed the LO version is 4.4.6~rc3-0ubuntu1

[Stephen M. Webb (bregma)]

It looks like /etc/ld.so.cache is missing from the Puritine container. You can try this as a temporary workaround.

(1) Log in to the device using 'adb shell' or ssh.
(2) run the command 'ldconfig -v -r ~/.cache/libertine-container/puritine/rootfs'

[kevin gunn (kgunn72)]

attached is strace, just to be sure this is how i got it...i installed strace into the puritine container, then i logged onto the puritine shell, ran strace /usr/lib/libreoffice/programs/soffice.bin, hope that seems right

[kevin gunn (kgunn72)]

note: if it matters i had added the ld cache from comment #11

(gdb) run
Starting program: /usr/lib/libreoffice/program/soffice.bin
warning: Could not load shared library symbols for 87 libraries, e.g. /usr/lib/arm-linux-gnueabihf/libfakeroot/libfakeroot-sysv.so.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for 2 libraries, e.g. /opt/click.ubuntu.com/com.ubuntu.puritine/0.2/libertine-data/libertine-container/puritine/rootfs/lib/arm-linux-gnueabihf/libnss_compat.so.2.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for 2 libraries, e.g. /opt/click.ubuntu.com/com.ubuntu.puritine/0.2/libertine-data/libertine-container/puritine/rootfs/lib/arm-linux-gnueabihf/libnss_nis.so.2.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
no suitable windowing system found, exiting.
[LWP 4623 exited]
[Inferior 1 (process 4623) exited with code 01]
(gdb)

[Björn Michaelsen (bjoern-michaelsen)]

> open("/opt/click.ubuntu.com/com.ubuntu.puritine/0.2/libertine-data/libertine-container/puritine/rootfs/opt/click.ubuntu.com/com.ubuntu.puritine/0.2/libertine-data/libertine-container/puritine/rootfs/usr/lib/libreoffice/program/libvclplug_gtklo.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/opt/click.ubuntu.com/com.ubuntu.puritine/0.2/libertine-data/libertine-container/puritine/rootfs/opt/click.ubuntu.com/com.ubuntu.puritine/0.2/libertine-data/libertine-container/puritine/rootfs/usr/lib/libreoffice/program/libvclplug_genlo.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> write(2, "no suitable windowing system fou"..., 45) = 45

A quick look in:

 https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/8231265/+files/libreoffice-gtk_4.4.6%7Erc3-0ubuntu1_armhf.deb

shows at least libvclplug_gtklo.so to be there. Seems something is preventing dlopening these libs in the container?

[Stephen M. Webb (bregma)]

So, the links in /etc/alternatives are pretty messed up in the puritine container. To fix them to the point where LO starts, use the following commands.

$ sudo ln -sf /home/phablet/.cache/libertine-container/smw/rootfs/usr/lib/arm-linux-gnueabihf/mesa/ld.so.conf ../libertine-container/puritine/rootfs/etc/alternatives/arm-linux-gnueabihf_gl_conf
$ sudo proot -S ~/.cache/libertine-container/puritine/rootfs ldconfig.real -f /usr/lib/arm-linux-gnueabihf/mesa/ld.so.conf

This will rebuild the dynamic linker cache inside the container to include the Mesa GL libraries. LO will get past the startup problems (I then get messages associated with incompletely insdtalled dependency packages like libgdk-pixbuf2.0-0 and Java framework errors).

[Christopher Townsend (townsend)]

I have an updated puritine click package that should fix this issue. Please test and let me know.

https://chinstrap.canonical.com/~townsend/puritine/com.ubuntu.puritine_0.3_armhf.click

Thanks!