Created attachment 116582 [details]
Screenshot demonstrating the issue, though not precisely b/c it doesn't flicker
1.Open a new Writer document, it is not necessary to type anything
2a Go to Paragraph sidebar panel, click Line Spacing button (in bottom left corner)
2b Alternatively, use Line Spacing toolbar button, the effect is the same
3. Do not move the mouse yet
=> notice the dropdown flickering annoyingly (screenshot, but it doesn't capture the flickering)
4. Move mouse cursor a bit down, into the upper part of dropdown
=> notice the bottom part (Custom Value) still flickering annoyingly, the upper part with selection of fixed spacing is stabilized by now
5. Click custom line spacing combobox (single, 1.5, double etc.)
=> in sidebar, the whole dropdown is stabilized and doesn't flicker any more
=> in toolbar, it still flickers on the edges
Reproduced with kde4 and gen vcl plugins (originally thought this is kde4-specific, but the flickering is only much more prominent with kde4 plugin)
Win 7 Pro 64-bit Version: 220.127.116.11.alpha1+
Build ID: 80ec99db4325a439a8a3f1d420d0a80f8bf9c439
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-16_00:00:20
Locale: fi-FI (fi_FI)
Ubuntu 15.04 64-bit
Build ID: 9ef671364ff9fbb552a5433053af9283d12d90c7
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2015-06-16_08:38:45
Locale: en-US (en_US.UTF-8)
It is not flickering, but I could reproduce what is shown in the screenshot, the weird ghostly effect.
Launched with SAL_USE_VCLPLUGIN=gen ./soffice
Build ID: 7a138bee01f96405899cb46cf60a4b9a734e77b1
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-06-17_06:34:45
Locale: en-US (en_US.UTF-8)
OS is Kubuntu 15.04 64-bit
*** Bug 97468 has been marked as a duplicate of this bug. ***
Now I am not seeing any problems with any VCL backend. Maybe you should re-test.
Arch Linux 64-bit
Build ID: 632bc11ce8fab1c4046ab24810b90a7ce9ac5914
CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on April 27th 2018
** 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!
Not an issue anymore