Bug 1163211 - LibreOffice 6.4 crashes when file selection dialog window is opened in KDE
Summary: LibreOffice 6.4 crashes when file selection dialog window is opened in KDE
Status: RESOLVED WORKSFORME
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: LibreOffice (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-09 17:13 UTC by Angelos Skembris
Modified: 2020-02-20 15:04 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angelos Skembris 2020-02-09 17:13:48 UTC
With the latest version of Calc (6.4.0.3), I cannot insert an image in a spreadsheet in KDE. Program crashes instantly once "Insert -> Image" is selected from the drop-down menu. This crash also occurs when opening a dialog box using "Save As", or other cases.  

Steps to reproduce:

1. Open any Libreoffice Calc spreadsheet (even a new one).
2. Select "Insert -> Image" from the drop-down menu.

The problem seems to lie in the VCL plugin:

/usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libreoffice/program/libvclplug_qt5lo.so: undefined symbol: _ZN9QtPrivate12argToQStringE11QStringViewmPPKNS_7ArgBaseE, version Qt_5

I have reported this bug in TDF's bugzilla:

https://bugs.documentfoundation.org/show_bug.cgi?id=130352

I have downloaded TDF's RPM packages and everything seems to work fine (although the GTK dialog boxes are used), so it seems that this is a packaging issue.

Let me know if additional information is needed.
Comment 1 Wolfgang Bauer 2020-02-19 18:24:34 UTC
(In reply to Angelos Skembris from comment #0)
> /usr/lib64/libreoffice/program/soffice.bin: symbol lookup error:
> /usr/lib64/libreoffice/program/libvclplug_qt5lo.so: undefined symbol:
> _ZN9QtPrivate12argToQStringE11QStringViewmPPKNS_7ArgBaseE, version Qt_5

This indicates that you have/had incompatible packages installed, maybe from different repos.

What's your repo list?
zypper lr -d

Does "zypper dup" offer any updates?

FWIW, I cannot reproduce the problem here on Leap 15.1 with libreoffice 6.4.0.3 from the LibreOffice:Factory repos on OBS (which should basically be the same as the version in Tumbleweed)...
Comment 2 Angelos Skembris 2020-02-20 10:35:00 UTC
(In reply to Wolfgang Bauer from comment #1)
> (In reply to Angelos Skembris from comment #0)
> > /usr/lib64/libreoffice/program/soffice.bin: symbol lookup error:
> > /usr/lib64/libreoffice/program/libvclplug_qt5lo.so: undefined symbol:
> > _ZN9QtPrivate12argToQStringE11QStringViewmPPKNS_7ArgBaseE, version Qt_5
> 
> This indicates that you have/had incompatible packages installed, maybe from
> different repos.
> 
> What's your repo list?
> zypper lr -d
> 
> Does "zypper dup" offer any updates?
> 
> FWIW, I cannot reproduce the problem here on Leap 15.1 with libreoffice
> 6.4.0.3 from the LibreOffice:Factory repos on OBS (which should basically be
> the same as the version in Tumbleweed)...

To be honest, after a full distribution update (not just Libreoffice and dependencies), I can't reproduce it either, it seems to be working fine. 

I think it required a newer version of something that was not pulled in when updating the main LO packages themselves. All packages were from the Tumbleweed repo and no dependency issues were presented during the update.  

In any case, I doubt I will be able to reproduce it now. Probably best we close the bug as a transient packaging issue. 

Thank you for the help!
Comment 3 Wolfgang Bauer 2020-02-20 15:04:35 UTC
Ok, thanks for the update!

As the missing symbol was an internal Qt5 function (QtPrivate::argToQString()) it probably was a problem with the Qt5 packages, not libreoffice.
Maybe some inconsistent mirror, or maybe some rebuild was missing from that particular snapshot. (although there would probably have been other similar reports then, at least I am not aware of any, and the last Qt5 update to 5.14.1 was actually on Feb. 4th already)

But as the problem disappeared already...