Download it now!
Bug 97905 - Unfocused display of current style in Sidebar has bad contrast (see comment 20)
Summary: Unfocused display of current style in Sidebar has bad contrast (see comment 20)
Status: RESOLVED DUPLICATE of bug 98253
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
5.1.0.0.alpha0+ Master
Hardware: All Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard: needsKDE
Keywords: bibisectRequest, regression
Depends on:
Blocks: KDE
  Show dependency treegraph
 
Reported: 2016-02-16 15:18 UTC by sergio.callegari
Modified: 2018-12-02 09:32 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot showing the issue: the current Style is "Title", but you see a gray bar. (14.67 KB, image/png)
2016-02-16 15:18 UTC, sergio.callegari
Details
Another example (7.19 KB, image/png)
2016-02-17 13:13 UTC, sergio.callegari
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sergio.callegari 2016-02-16 15:18:06 UTC
Created attachment 122692 [details]
Screenshot showing the issue: the current Style is "Title", but you see a gray bar.

Using writer and pressing F11 to show the styles panel does not work properly in 5.1 in Linux, where the current style appears as a gray bar until you click on it (see attachment). This used to be OK in 5.0.
Comment 1 Timur 2016-02-16 17:47:58 UTC
Can NOT confirm in Windows and Linux.
Does this happen always for you or with a specific document?
Comment 2 sergio.callegari 2016-02-16 21:58:02 UTC
Happens with any document.

Issue started with the 5.1 series. In 5.0 styles work OK, in 5.1 there is this minor nuisance of the current style name not appearing until you click.

I am on kubuntu 15.10, Intel graphics.

Tried with both the graphic drivers as distributed by Ubuntu and the most recent (in fact from git) drivers. Makes no difference.

Also tested with compositing on and off in the window manager. This makes no difference either.

The fact that things work fine in 5.0 does not mean it is a bug in LibO. May be still an issue with graphic drivers that gets triggered by something different that is going on in 5.1 wrt 5.0.

When I have the possibility, I'll try on a machine with almost identical setup, but (old) nvidia graphics.
Comment 3 Buovjaga 2016-02-17 13:08:13 UTC
Is it a custom style / are the invisible ones custom styles? bug 97672
Comment 4 sergio.callegari 2016-02-17 13:13:58 UTC
Created attachment 122724 [details]
Another example
Comment 5 sergio.callegari 2016-02-17 13:16:35 UTC
The current style has the issue, whatever it is, custom or non custom.

The screenshot in "another example" was obtained by just calling

libreoffice --writer 

and then pressing F11.

The style panel should show "Default Style" but shows only a gray bar until one clicks in the Style panel causing a rendering update.
Comment 6 Timur 2016-02-17 18:17:15 UTC
It's about KDE. When reporting a bug, please be specific about the system.
Comment 7 Timur 2016-02-17 18:52:16 UTC
Looks like it works after removing the KDE integration (by uninstalling "libobasis5.1-kde-integration" or "lodevbasis5.2-kde-integration").
Comment 8 sergio.callegari 2016-02-17 18:59:45 UTC
I confirm that this is the case.

I apologize for not having mentioned KDE before. Did not think the culprit could be in KDE or the KDE integration as this worked in 5.0.
Comment 9 sergio.callegari 2016-02-17 19:02:11 UTC
I do not know if this can be of any relevance, but I have just noticed that removing the KDE integration package also fixes the regression in bug 78924.
Comment 10 vermontpoet 2016-03-28 19:13:09 UTC
I almost reported this bug before noticing it here. This bug has been bothering me for about a year. It's just innocuous enough to ignore, but I'm sure it's annoying other users.  

Is this a KDE issue? 

Is this something Libre devs can remedy?
Comment 11 vermontpoet 2016-03-28 19:18:30 UTC
//Looks like it works after removing the KDE integration (by uninstalling "libobasis5.1-kde-integration" or "lodevbasis5.2-kde-integration").//

I can't find either of these files on my current system:

Desktop: KDE Plasma 5.5.4
Distro: Ubuntu 16.04 xenial

Using LibreOffice 5.1.1.3

Is there another package name I should be looking for?
Comment 12 vermontpoet 2016-03-28 19:46:33 UTC
Found it:

libreoffice-kde

Removed. Less integrated, for sure, but removal of the bug is an improvement.
Comment 13 Buovjaga 2016-03-29 05:29:31 UTC
(In reply to vermontpoet from comment #12)
> Found it:
> 
> libreoffice-kde
> 
> Removed. Less integrated, for sure, but removal of the bug is an improvement.

You could also have just launched with:
SAL_USE_VCLPLUGIN=gtk libreoffice
SAL_USE_VCLPLUGIN=gen libreoffice
This is experimental still: SAL_USE_VCLPLUGIN=gtk3 libreoffice
Comment 14 vermontpoet 2016-03-29 19:30:39 UTC
Is there a practical difference in using these commands? I'd have to edit menu entries or invoke Libre from the command line.

Also, this is indirectly related, but I notice the menu font rendering is much improved without KDE Integration. The menu fonts used with Integration looked as if they were in needing of anti-aliasing. Much easier to read now.

Libre without KDE Integration (in Plasma 5: 16.04 at least) is, I'd have to say, a considerably improved experience. Not complaining, just observing...
Comment 15 sergio.callegari 2016-03-29 19:53:10 UTC
Unfortunately, this is true. Furthermore, KDE integration currently brings in at least another bug, i.e. bug 78924
Comment 16 Xisco Faulí 2016-09-12 12:38:43 UTC
Adding keyword 'bibisectRequest'.
Comment 17 Xisco Faulí 2016-09-28 21:23:48 UTC

*** This bug has been marked as a duplicate of bug 92380 ***
Comment 18 sergio.callegari 2017-05-14 21:05:32 UTC
Does not seem a duplicate of that to me.

That one is a rendering problem of the preview.

This one is a problem with the KDE integration that makes the current style entry gray until clicked.
Comment 19 QA Administrators 2018-05-16 02:31:37 UTC Comment hidden (obsolete)
Comment 20 sergio.callegari 2018-06-04 15:59:56 UTC
The current style now seems to appear, but the color choice is very unfortunate: white on light gray -> extremely hard to read
Comment 21 P. Most 2018-08-15 12:42:43 UTC
Is there some kind of workaround? Like somehow changing the colors?
Comment 22 Katarina Behrens (Inactive) 2018-12-02 09:32:19 UTC

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