Ubuntu
libreoffice package

func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26

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

Bug Description

I'm starting libreoffice with an docx document and it immediately crashes outputting the following text on console. The file opens fine on a different computer with an older libreoffice version.

func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26

This as been fixed upstream at https://bugs.documentfoundation.org/show_bug.cgi?id=118373 and reported also by other users at https://forum.ubuntuusers.de/topic/upgrade-von-16-04-nach-18-04-libreoffice-oeffn/

Description: Ubuntu 18.04.2 LTS
Release: 18.04

libreoffice:
  Installiert: 1:6.0.7-0ubuntu0.18.04.2
  Installationskandidat: 1:6.0.7-0ubuntu0.18.04.2
  Versionstabelle:
 *** 1:6.0.7-0ubuntu0.18.04.2 700
        700 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages
        100 /var/lib/dpkg/status
     1:6.0.3-0ubuntu1 700
        700 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages

Revision history for this message
AZ (m-dev) wrote :

Workaround: disable OpenCL software emulation and Java Runtime in Options.

Revision history for this message
Olivier Tilloy (osomon) wrote :

That error message and the crash are most likely unrelated (according to the upstream bug report, the error message is harmless). But I see that your architecture is i386, and you mention that disabling java in the options fixes the problem, so the issue is most likely bug #1699772.
OpenJDK 11 is being backported to Ubuntu 18.04 (see bug #1814133), and this crash has been confirmed to be fixed with it, so if everything goes well you should soon be getting an update that will fix the crash.

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

Other bug subscribers

Remote bug watches

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