Bug 133264

Hi Tom,
Thanks for reporting this issue.
So it's happening for you with version 7.0 and 6.4.4.2 ? That's very strange since this is the first report we have got of this kind.
Does it work if you launch LibreOffice from commandline with 'SAL_USE_VCLPLUGIN=gen instdir/program/soffice' ?

Hi Xisco,

Thanks for your quick response. To answer your questions:

A) "So it's happening for you with version 7.0 and 6.4.4.2 ?"

- The 100% load at startup (and when a component of LO e.g. "Write" is closed and it returns to the main window) happens for all versions of LO 6.4.x and for LO 7.0. Yes.
- The "About LibreOffice" crash happens only for LO 7.0.

B) "Does it work if you launch LibreOffice from commandline with 'SAL_USE_VCLPLUGIN=gen instdir/program/soffice' ?"

Yes it does. Both problems are gone for both LO 6.4 and LO 7.0 when I run (I run tcsh as login shell):
% setenv SAL_USE_VCLPLUGIN gen
% /opt/libreoffice6.4/program/soffice
% /opt/libreofficedev7.0/program/soffice

And here is now the build reference information from 7.0 as a proof :-)

Version: 7.0.0.0.alpha1
Build ID: 6a03b2a54143a9bc0c6d4c7f1...
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; 
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Does this information help you to narrow down the root cause?

Regards
Tom

Same behavior as previously reported concerning cases A) and B) for

Version: 6.4.5.2
Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; 
Locale: de-DE (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Regards
Tom

Same problems for the recently released LO 7.0.0.3 (LibreOffice_7.0.0_Linux_x86-64_deb.tar.gz) under Linux Mint 18.3..

In addition

  % setenv SAL_USE_VCLPLUGIN gen
  % /opt/libreoffice7.0/program/soffice

results first in the following warning in the terminal

  Warning: failed to read path from javaldx

and an immediate exit (139) of the program.

Regards
Tom

Follow-up:

With the following preparation, I can start LO 7.0.0.3 without running into the previously reported problems:

[~] % setenv SAL_USE_VCLPLUGIN gen
[~] % libreoffice7.0 --safe-mode
Confirm "Continue in Safe Mode".

Now I can open Help > About LibreOffice and copy the revision information

  Version: 7.0.0.3
  Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e
  CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11
  Locale: en-US (en_US.UTF-8); UI: en-US
  Calc: threaded

Hope this helps, if someone reads this update ;-)

Tom

*** Bug 135442 has been marked as a duplicate of this bug. ***

@Heiko, I believe this crash is the same as in https://crashreport.libreoffice.org/stats/signature/AboutDialog::AboutDialog

(In reply to Xisco Faulí from comment #8)
> @Heiko, I believe this crash is the same as in
> https://crashreport.libreoffice.org/stats/signature/AboutDialog::AboutDialog

Crash happens when the version label is assigned, cannot see anything suspicious in 
CuiResId("%ABOUTBOXPRODUCTVERSION%ABOUTBOXPRODUCTVERSIONSUFFIX");

Installed the deb package in a VB with Ubuntu and run into the same "invalid unclassed pointer cast to GtkMenuShell" issue. GTK_IS_MENU_SHELL fails with "GtkDialog mapped without a transient parent." Any advice, Caolan?

I suspect the version of gtk3 installed is 3.18 (like bug 135442 explicitly records) and the about dialog has min version of 3.20 set and so it fails to load

Hi Caolan,

Yes indeed. The gtk3 on my system is 3.18.9, which (btw) I thought to be sufficient to run LibreOffice.

    The software and hardware prerequisites for installing on Linux are as follows:

    Linux kernel version 3.10 or higher
    glibc2 version 2.17 or higher
    Pentium-compatible PC (Pentium III, Athlon or more-recent system recommended)
    256Mb RAM (512 MB RAM recommended)
    Up to 1.55 GB available hard disk space
    X Server with 1024x768 resolution (higher resolution recommended), with at least 256 colors
    Gnome 3.18 or higher, with the at-spi2 1.32 package (required for support for assistive technology [AT] tools), or another compatible GUI (such as KDE, among others)

The inconsistency between the gtk3 revision expected by LO 7.0 (and LO 6.4?) and provided by my system may also explain the high CPU load I noticed in https://bugs.documentfoundation.org/show_bug.cgi?id=132134?

In fact, only LO up to revision 6.3 is running troublefree on my system. Any chance that gtk3 revision 3.20 was introduced with LO 6.4?

Regards
Tom

3.18 is supposed to be sufficient, the specific crash problem is fixed now with bug #135442

*** This bug has been marked as a duplicate of bug 135442 ***