Bug 103676 - Toolbars background is not drawn, instead showing previously active application as a background (KDE)
Summary: Toolbars background is not drawn, instead showing previously active applicati...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
5.2.3.2 rc
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 105374 107101 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-11-03 13:03 UTC by Vianney Stroebel
Modified: 2017-04-21 07:50 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Example of bug: LibreOffice Writer with no toolbar background (128.68 KB, image/jpeg)
2016-11-03 13:11 UTC, Vianney Stroebel
Details
Images of menu/panel bugs in action (155.97 KB, image/png)
2017-02-08 22:47 UTC, Geo Chura
Details
Screenshot of bugs in Safe-Mode on v5.3 (107.19 KB, image/png)
2017-02-09 21:52 UTC, Geo Chura
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vianney Stroebel 2016-11-03 13:03:44 UTC
Description:
See below.

Steps to Reproduce:
Open any LibreOffice application (Writer, Calc,...)

Actual Results:  
The toolbars background is not drawn. Instead, it shows the previously active application as a background of the icons. The icon themselves are drawn correctly but are very difficult to see because they are mixed with the mashed background.

Also, when I move the mouse over the icons, all the tooltips that open stay displayed, making the background even messier.

This makes the toolbars (and thus the application) pretty much unusable.

Expected Results:
The toolbars background should be drawn.


Reproducible: Always

User Profile Reset: Yes

Additional Info:
This happened since I upgraded to Kubuntu Yaketi (from Xenial). I use http://ppa.launchpad.net/libreoffice/ppa/ubuntu.

Changing LibreOffice or GTK theme doesn't affect this bug.

Feel free to ask for more info on my system. Just give me the command I need to type.


User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Comment 1 Vianney Stroebel 2016-11-03 13:11:14 UTC
Created attachment 128468 [details]
Example of bug: LibreOffice Writer with no toolbar background
Comment 2 Vianney Stroebel 2016-11-03 13:16:00 UTC
After I tried a few things (reinstalling Libreoffice, resetting config, etc.), the toolbars background now displays the application that was active when I launched the LibreOffice application. It does not change anymore when I switch applications with Alt+Tab (it did before).
Comment 3 Vianney Stroebel 2016-11-03 13:18:01 UTC
By the way, does anyone know if this kind of display bug has a name? Or if there is a better way to describe it?
Comment 4 Xisco Faulí 2016-11-03 13:19:12 UTC
Hi Vianney,
Then is is fixed as per comment 2 ?
Comment 5 Vianney Stroebel 2016-11-03 13:20:58 UTC
(In reply to Xisco Faulí from comment #4)
> Hi Vianney,
> Then is is fixed as per comment 2 ?

No, it's not fixed at all. The bug has just changed slightly but it's pretty much the same.
Comment 6 Samuel Mehrbrodt (allotropia) 2016-11-04 10:56:51 UTC
Do you have OpenGL enabled?
Comment 7 Vianney Stroebel 2016-11-04 11:02:46 UTC
The only thing I can tell you is that in the KDE System Settings GUI, in the Compositor screen, it shows "OpenGL 2.0"

Is there a command line tool I can use to confirm this? I didn't find anything on Google.
Comment 8 Samuel Mehrbrodt (allotropia) 2016-11-04 14:55:05 UTC
(In reply to Vianney Stroebel from comment #7)
> The only thing I can tell you is that in the KDE System Settings GUI, in the
> Compositor screen, it shows "OpenGL 2.0"
> 
> Is there a command line tool I can use to confirm this? I didn't find
> anything on Google.

Please paste the system information in Help->About.
Comment 9 Vianney Stroebel 2016-11-04 14:56:52 UTC
> Please paste the system information in Help->About.

Here it is:

Version: 5.2.3.2
Build ID: 1:5.2.3~rc2-0ubuntu1~yakkety1
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 10 Samuel Mehrbrodt (allotropia) 2016-11-04 15:01:54 UTC
UI Render == default, so no OpenGL.

Does it make any difference if you use different vcl backends:

$ SAL_USE_VCLPLUGIN=gen libreoffice
$ SAL_USE_VCLPLUGIN=gtk libreoffice
$ SAL_USE_VCLPLUGIN=gtk3 libreoffice
Comment 11 Vianney Stroebel 2016-11-04 15:09:36 UTC
(In reply to Samuel Mehrbrodt (CIB) from comment #10)
> UI Render == default, so no OpenGL.
> 
> Does it make any difference if you use different vcl backends:
> 
> $ SAL_USE_VCLPLUGIN=gen libreoffice
> $ SAL_USE_VCLPLUGIN=gtk libreoffice
> $ SAL_USE_VCLPLUGIN=gtk3 libreoffice


'SAL_USE_VCLPLUGIN=gen' shows a dark grey UI. Only the menu and part of the Properties sidebar panel are garbled.

'gtk' and 'gtk3' look the same as the normal command without the variable.
Comment 12 Jean-Baptiste Faure 2016-11-04 22:18:49 UTC
(In reply to Vianney Stroebel from comment #11)
[...]
> 'gtk' and 'gtk3' look the same as the normal command without the variable.

You should try :
$ export SAL_USE_VCLPLUGIN=gtk
$ libreoffice

And you need to install the packages libreoffice-gtk2 and libreoffice-gtk3. You probably have only one of them.

Best regards. JBF
Comment 13 Vianney Stroebel 2016-11-07 19:05:58 UTC
This issue is caused by a regression in kernel linux-image-4.8.0-26-generic (4.8.0-26.28)

Reverting to previous kernel, 4.8.0-22.24 fixes the issue.
Comment 14 Vianney Stroebel 2016-11-07 19:26:11 UTC
(In reply to Vianney Stroebel from comment #13)
> This issue is caused by a regression in kernel linux-image-4.8.0-26-generic
> (4.8.0-26.28)
> 
> Reverting to previous kernel, 4.8.0-22.24 fixes the issue.

Actually, I take it back: the bug is back again. I don't know why it disappeared for a little why...
Comment 15 Buovjaga 2016-11-17 21:10:23 UTC
I think there is an existing report for this, but I cannot find it :(
Comment 16 Geo Chura 2017-02-06 22:46:19 UTC
I experienced the identical bug on LO (writer & calc) v 5.2 installed via Synaptic regular repo on KDE Neon 5.8.5; note this was in the KDE version of LibreOffice that is part of the Neon repo. The app was totally unusable with lack of a consistent background and the default Breeze icons.

I rebooted several times, even re-installed the application and experienced identical bug results. 

Subsequently, I have installed the available SNAP 5.3.0.3 version of LO and the interface is fine. However, this SNAP install fails to recognize system fonts that are not part of the LO SNAP install.
Comment 17 Buovjaga 2017-02-07 06:57:27 UTC
Vianney & Geo: it would be interesting to know, what happens, if you launch in Safe Mode with version 5.3 (Help - Restart in Safe Mode). In Geo's case, I don't mean the Snap package.
Comment 18 Geo Chura 2017-02-08 22:47:59 UTC
Created attachment 131024 [details]
Images of menu/panel bugs in action

Attached should be a screen shot of the bugs in action: this is fresh install of the "enterprise-stable" v5.2. running installed via dpkg on KDE Neon 5.9.1. This is the identical problem presented with v5.3.0.3 when running under KDE Neon 5.8.5.

NOTE, when launching from CLI the following is reported: 

 javaldx: Could not find a Java Runtime Environment!
 Warning: failed to read path from javaldx
 I18N: Operating system doesn't support locale ""
 I18N: Operating system doesn't support locale "en_US"

dpkg reports that "javaldx" is NOT installed. I am also unable to find it to complete the install.Disabling the Java/Runtime option in Advanced configurations does not seem to resolve the bug.

Regarding launch in safe-mode, there is no such option available via the Help menu. Furthermore, the "--safe-mode" option noted in the online help for LO is not recognized by the system. Thus, I am not successful in testing under "safe mode".
Comment 19 Geo Chura 2017-02-09 09:47:20 UTC
I have tested v5.2. as it is packaged within the KDE platform of Kubuntu 16.10 and I must report that the same menu/panel bug appear there also.

I believe I failed to note in my earlier comment that this bug does NOT appear in the SNAP v5.3. of LO that I installed on KDE neon, though it, is afflicted with the font issues mentioned previously.
Comment 20 Buovjaga 2017-02-09 10:36:16 UTC
(In reply to Geo Chura from comment #18)
> Regarding launch in safe-mode, there is no such option available via the
> Help menu. Furthermore, the "--safe-mode" option noted in the online help
> for LO is not recognized by the system. Thus, I am not successful in testing
> under "safe mode".

Just to clarify, this is with 5.3? Safe Mode should be available in 5.3, so it is weird..
Comment 21 Geo Chura 2017-02-09 21:52:30 UTC
Created attachment 131059 [details]
Screenshot of bugs in Safe-Mode on v5.3

Okay so here is a shot of a somewhat improved condition in LO v 5.3 running in safe-mode. LO was installed via dpkg and is running here on the same Lenovo X200T, this time on Kubuntu 16.10. It appears that running in both normal- and safe-mode the issues with the toolbar area are better (perhaps it's because of Kubuntu or 16.10). However, there are still some serious issues with the panels to the right of the desktop. Safe-mode thus does not seem to affect the situation.

I should note, I did also test the LO v5.2.5 that was packaged with this Kubuntu install and there was no improvement there, both the toolbar area and the panels were showing the bug.
Comment 22 Buovjaga 2017-02-10 06:44:38 UTC
*** Bug 105374 has been marked as a duplicate of this bug. ***
Comment 23 pieter kristensen 2017-02-16 12:10:48 UTC
On my machine this behavior started immediately after the xserver-xorg-video-intel driver was replaced by the xserver-xorg-video-intel-native-modesetting driver.

I suppose all people who experience this also have computers with older intel graphics cards.
Comment 24 Buovjaga 2017-04-15 17:40:32 UTC
Pieter reported in the duplicate:
"I installed both ubuntu 17.04 and kubuntu 17.04 and all problems are solved. Libreoffice is rendered as it should.
I suppose this is due to the newer mesa verion."
Comment 25 Buovjaga 2017-04-17 17:12:19 UTC
*** Bug 107101 has been marked as a duplicate of this bug. ***
Comment 26 Hamid 2017-04-21 02:20:11 UTC
Update to 17.04 resolved the issue.