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.
Can NOT confirm in Windows and Linux.
Does this happen always for you or with a specific document?
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.
Is it a custom style / are the invisible ones custom styles? bug 97672
Created attachment 122724 [details]
The current style has the issue, whatever it is, custom or non custom.
The screenshot in "another example" was obtained by just calling
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.
It's about KDE. When reporting a bug, please be specific about the system.
Looks like it works after removing the KDE integration (by uninstalling "libobasis5.1-kde-integration" or "lodevbasis5.2-kde-integration").
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.
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.
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?
//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 18.104.22.168
Is there another package name I should be looking for?
Removed. Less integrated, for sure, but removal of the bug is an improvement.
(In reply to vermontpoet from comment #12)
> Found it:
> Removed. Less integrated, for sure, but removal of the bug is an improvement.
You could also have just launched with:
This is experimental still: SAL_USE_VCLPLUGIN=gtk3 libreoffice
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...
Unfortunately, this is true. Furthermore, KDE integration currently brings in at least another bug, i.e. bug 78924
Adding keyword 'bibisectRequest'.
*** This bug has been marked as a duplicate of bug 92380 ***
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.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
The current style now seems to appear, but the color choice is very unfortunate: white on light gray -> extremely hard to read
Is there some kind of workaround? Like somehow changing the colors?
*** This bug has been marked as a duplicate of bug 98253 ***