Bug 126925 - Crash of LO Writer when changing xfce4 theme
Summary: Crash of LO Writer when changing xfce4 theme
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.0.0.alpha1+
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-14 14:41 UTC by Adalbert Hanßen
Modified: 2019-08-17 11:28 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adalbert Hanßen 2019-08-14 14:41:40 UTC
This bug report pertains to
Version: 6.4.0.0.alpha0+
Build-ID: 9ee5ad5a0b84bfa652da34694ba4f75668f06087
CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-07-30_13:21:44
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded

running on Xubuntu 16.04.

A similar bug was Bug 93342, but that one was in version 5 on Windows and it could not be reproduced. So I open an new bug report.

This one is reproducible.

1. Open a LO Writer document.
2. Change Xfce4's theme, e.g. from Greybird to some other one.

LO Writer reproducibly crashes.
Comment 1 Buovjaga 2019-08-14 14:55:45 UTC
(In reply to Adalbert Hanßen from comment #0)
> CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk3; 

You are running the gtk3 VCL backend of LibreOffice. Yet, the Xfce version you use is probably older than 4.14 (just released), so it is using gtk2. I don't think it is a good idea to mix them.

Try running from the command line with
SAL_USE_VCLPLUGIN=gtk /path/to/program/soffice
Comment 2 Adalbert Hanßen 2019-08-14 18:57:37 UTC
(In reply to Buovjaga from comment #1)
> (In reply to Adalbert Hanßen from comment #0)
> > CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk3; 
...
> Try running from the command line with
> SAL_USE_VCLPLUGIN=gtk /path/to/program/soffice

You are right, starting LibreOffice from the command line using

$ SAL_USE_VCLPLUGIN=gtk /opt/libreofficedev6.4/program/soffice

(soffice:17390): Gtk-WARNING **: 20:50:06.315: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
$

I could store my big file seeing the progress bar. 

Do I have to make this setting of the environment variable permanent or was my trial just a proof for your conjecture? What would be necessary to make it permanent?

But as you see from my copying from the terminal window, there is another error message on the display.
Comment 3 Buovjaga 2019-08-15 03:08:23 UTC
(In reply to Adalbert Hanßen from comment #2)
> Do I have to make this setting of the environment variable permanent or was
> my trial just a proof for your conjecture? What would be necessary to make
> it permanent?
> 
> But as you see from my copying from the terminal window, there is another
> error message on the display.

There should be a package called libreoffice-gtk3. You can uninstall the package and then LibreOffice should automatically use gtk2. You can always check the currently used UI plugin from LibreOffice's Help - About dialog (VCL: gtk2/gtk3).

The message you refer to is a warning, not an error, so at least it is not fatal.

Anyway, I hope Xfce 4.14 will work with LibreOffice using gtk3: https://xfce.org/about/news/?post=1565568000
Perhaps it will be available in Xubuntu 19.10.
Comment 4 Adalbert Hanßen 2019-08-16 06:59:56 UTC
(In reply to Buovjaga from comment #3)
> (In reply to Adalbert Hanßen from comment #2)
...
> 
> There should be a package called libreoffice-gtk3. You can uninstall the
> package and then LibreOffice should automatically use gtk2. 
...

Apparently there was no such package in my system as you can see observing my trial to remove it:

$ sudo apt-get remove libreoffice-gtk3
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Paket »libreoffice-gtk3« ist nicht installiert, wird also auch nicht entfernt.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
$
Comment 5 Buovjaga 2019-08-16 07:09:18 UTC
Right, sorry, you were using a daily build, where gtk3 is not separate.
Comment 6 Adalbert Hanßen 2019-08-16 07:38:06 UTC
(In reply to Buovjaga from comment #5)
> Right, sorry, you were using a daily build, where gtk3 is not separate.

What would be necessary to make 

  SAL_USE_VCLPLUGIN=gtk /opt/libreofficedev6.4/program/soffice

permanent?
Comment 7 Buovjaga 2019-08-16 07:47:18 UTC
(In reply to Adalbert Hanßen from comment #6)
> (In reply to Buovjaga from comment #5)
> > Right, sorry, you were using a daily build, where gtk3 is not separate.
> 
> What would be necessary to make 
> 
>   SAL_USE_VCLPLUGIN=gtk /opt/libreofficedev6.4/program/soffice
> 
> permanent?

Edit your .bashrc file in your home directory.
Add a line
alias libogtk='SAL_USE_VCLPLUGIN=gtk /opt/libreofficedev6.4/program/soffice'

Or whatever alias name you like.
Comment 8 Adalbert Hanßen 2019-08-16 08:21:35 UTC
I added the line 

alias libogtk='SAL_USE_VCLPLUGIN=gtk /opt/libreofficedev6.4/program/soffice'

to the end of ~/.bashrc.

However, after quitting and startinglibreofficedev6.4  again with my big file, I don't see the progress bar when storing it.

Does the name of the alias matter?
Was it right?

Inquiring Help>about I see

Version: 6.4.0.0.alpha0+
Build-ID: 9ee5ad5a0b84bfa652da34694ba4f75668f06087
CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-07-30_13:21:44
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded
Comment 9 Buovjaga 2019-08-16 08:30:04 UTC
You have to start a new terminal session after modifying .bashrc
Comment 10 Adalbert Hanßen 2019-08-17 10:04:52 UTC
(In reply to Buovjaga from comment #9)
> You have to start a new terminal session after modifying .bashrc

I logged out and in again, but the progress bar was not functional when storing the big file. (there was a long rectangle, but no horizontal thermometer in it).

To be sure, I repeated my trial today after a complete reboot: Still the same observation: No progress bar.

Does the name of the alias, "libogtk" matter?
Was it right?

Inquiring Help>about I see
Comment 11 Buovjaga 2019-08-17 11:28:02 UTC
(In reply to Adalbert Hanßen from comment #10)
> (In reply to Buovjaga from comment #9)
> > You have to start a new terminal session after modifying .bashrc
> 
> I logged out and in again, but the progress bar was not functional when
> storing the big file. (there was a long rectangle, but no horizontal
> thermometer in it).
> 
> To be sure, I repeated my trial today after a complete reboot: Still the
> same observation: No progress bar.
> 
> Does the name of the alias, "libogtk" matter?
> Was it right?
> 
> Inquiring Help>about I see

No, the alias doesn't matter. You could call it "Brian" for all that matters. To be sure, you are launching it from the command line with libogtk?

Note that gtk2 support will soon be removed from master: https://gerrit.libreoffice.org/#/c/77405/

There is also the generic fallback vcl plugin:
SAL_USE_VCLPLUGIN=gen