@djoow Thanks for the command line workaround:
$ /usr/lib/libreoffice/program/soffice.bin
This saved me some trouble, because I had to switch to trusty Xubuntu for LibreOffice while my PureOS-based Librem 15 was wrecked. This is getting ridiculous, and I agree with @anon10067017 that the rolling release scheme is not very stable because there’s insufficient testing, a point I’ve made before. Looks like Debian “testing” should be renamed Debian “untested”.
Thanks to @Ricky for the link to the AppArmor bug report and the incredibly hostile response. They tried to kill the messenger, who brought news of their buggy programming that wrecked an untold number of people’s systems. Nobody’s perfect, and bugs exist, but that’s why we TEST.
I started to dig into apparmor and its complex documentation, but I couldn’t even install apparmor-utils because of broken packages that are unfixable at the moment. Talk about a Catch-22!
I was afraid to purge apparmor like @McShine did, because of unknown side effects and vulnerabilities, but the direct command line invocation of LibreOffice works fine without messing with apparmor.
Maybe it’s time for Purism to dump the continuous rolling release and move to a release schedule that gives more time for testing, such as monthly or bimonthly. Even every 2 weeks would be an improvement. Thoughts?