Bug 141130 - LO 7.1.1.2 exits after splash
Summary: LO 7.1.1.2 exits after splash
Status: RESOLVED DUPLICATE of bug 140126
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.1.1.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-20 18:26 UTC by Emilio
Modified: 2021-03-21 08:46 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Emilio 2021-03-20 18:26:56 UTC 
Description:
LO displays splash panel, then terminates giving this:

libreoffice7.1/program/libvclplug_gtk3lo.so: undefined symbol: gtk_widget_path_iter_set_object_name

LO 7.0.4.2 goes all ok on the same computer.


Steps to Reproduce:
1.command: $ ./libreoffice7.1/program/soffice
2.
3.

Actual Results:
(soffice:13121): Gtk-WARNING **: Theme parsing error: <data>:1:193: 'min-height' is not a valid property name

(soffice:13121): Gtk-WARNING **: Theme parsing error: <data>:1:209: 'min-width' is not a valid property name
/opt/opt/libreoffice7.1/program/soffice.bin: symbol lookup error: /opt/opt/libreoffice7.1/program/libvclplug_gtk3lo.so: undefined symbol: gtk_widget_path_iter_set_object_name



Expected Results:
LibreOffice menu page


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Linux distro slackware 14.2 KDE Kernel version 4.8.7
libgtk 3.0

Installed using the install script from LibreOffice_7.1.1_Linux_x86-64_rpm.tar.gz

LibreOffice 7.1.1.2 fe0b08f4af1bacafe4c7ecc87ce55bb426164676
Comment 1 Julien Nabet 2021-03-20 19:22:43 UTC 
https://bugs.documentfoundation.org/show_bug.cgi?id=140126#c1

In this comment, rather read:
"If you can't upgrade gtk3 version, you can try to workaround this by using..."
instead of:
"If you can upgrade gtk3 version, you can try to workaround this by using..."

*** This bug has been marked as a duplicate of bug 140126 ***
Comment 2 Emilio 2021-03-21 08:46:22 UTC 
Thanks for the speed of answare. Problem solved.
Emilio Primi