Open new Writer document. Move mouse pointer across blank page. No text applied. Pointer leaves a trail with every movement. Unchecking direct cursor solves problem but leaves me with no direct cursor. Only happens in Writer in Linux Mint 19.1 x64, not the Windows version. Doesn't happen with Impress Didn't happen with previous version of LO Writer and same operating system.
Steps to Reproduce:
1.Open new Writer document. Leave blank.
2.Move mouse pointer.
3.Pointer leaves a trail of artefacts with each pointer movement.
Disabling direct cursor solves the problem but leaves user without direct cursor.
Direct cursor leaves artefacts. Turning it off solves the problem but not a useful solution.
Direct cursor should work as designed. It did in LO 6.1 but hasn't in 6.2.
User Profile Reset: No
OpenGL enabled: Yes
Created attachment 148659 [details]
Johm, may be you just have active option "Formatting marks"? Try to disable it
Hi Roman: no, it's not related to "formatting marks" - I tried that already. As I mentioned in my bug report it's related to the Direct Cursor. When I uncheck that in Writer|Options|Formatting Aids the problem goes away. When I recheck it the problem returns. Only occurs in Writer, not Impress.
Does it work if you disable OpenGl ? -> https://wiki.documentfoundation.org/OpenGL
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Created attachment 148999 [details]
You didn't answer my question. Disable the openGl and retest please
Hi: restarted LO 6.2.2 Linux Mint 19.1 x64 in Safe Mode which I assume turns off OpenGL. Fixed the problem but LO ran noticeably slower. I have an Nvidia card and I gather this can be an issue with OpenGL ATM. So far the fix is to uncheck Direct Cursor but that doesn't work in Safe Mode anyway.
Using OpenCL in normal mode doesn't resolve the problem. Seems like it's video card related.
Could you please provide the opengl info as described here -> https://wiki.documentfoundation.org/OpenGL
OpenGL info added
glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 710/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 390.116
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 390.116
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.116
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
Hope this helps.
Hello John, a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
The problem persists making direct cursor unusable. Now using 220.127.116.11 in Mint 19.2 64 bit. Same Nvidia 710 card. Everything else remains unchanged.
Seems fine in Windows 10_64 laptop using Intel i7 and video card.
(In reply to John from comment #7)
> Hi: restarted LO 6.2.2 Linux Mint 19.1 x64 in Safe Mode which I assume turns
> off OpenGL. Fixed the problem but LO ran noticeably slower.
You can also disable OpenGL with Tools => Options => LibreOffice => View => Graphics Output. Perhaps this is also a solution or at least a workaround.
(In reply to John from comment #9)
> OpenGL info added
> Hope this helps.
Xisco, you've asked for OpenGL Infos. Are they helpful or is any additional info needed?
(In reply to Dieter from comment #12)
> (In reply to John from comment #7)
> > Hi: restarted LO 6.2.2 Linux Mint 19.1 x64 in Safe Mode which I assume turns
> > off OpenGL. Fixed the problem but LO ran noticeably slower.
> You can also disable OpenGL with Tools => Options => LibreOffice => View =>
> Graphics Output. Perhaps this is also a solution or at least a workaround.
I highly doubt John was using OpenGL UI rendering on Linux. Would be very surprised if this was the case.
(In reply to John from comment #0)
> Steps to Reproduce:
> 1.Open new Writer document. Leave blank.
> 2.Move mouse pointer.
> 3.Pointer leaves a trail of artefacts with each pointer movement.
> Disabling direct cursor solves the problem but leaves user without direct
Adding step 0:
Tools - Options - Writer - Formatting aids - Direct cursor
Hi, I would like to add that I am experiencing this problem as well. I am using
Mac OS X 10.11
I think it was also showing up for the previous version of LibreOffice I was using; it was triggering some memory about why I stopped using LibreOffice... But it has been quite a while since I've used LibreOffice so I do not know what version that was.
Turning off Direct Cursor seems to have stopped this from occurring.
It also was happening on pages with text, so I do not think a blank page is essential for this bug to show up. The marks would actually go away if I directed the mouse properly - and others then show up, so some sort of problem in the screen redrawing, perhaps.
Setting to NEW per last comment
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 https://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://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
The issue is still reproducible with the latest LO 7.6 dev master:
Version: 18.104.22.168.alpha1+ (X86_64) / LibreOffice Community
Build ID: 52f70f04bdc586a072141e069d451a979c5f4cb7
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_DE); UI: en-US
Calc: CL threaded
The problem is caused by the way the direct cursor pointer (shadow pointer) is rendered using XOR:
The problem with XOR rendering is discussed in tdf#38844:
Bug 38844 - Reduce XOR rendering (search RasterOp::Xor)
Rizal, can you create a nice cursor image for this?
See also https://gerrit.libreoffice.org/c/core/+/153099
Hossein committed a patch related to this issue.
It has been pushed to "master":
tdf#122970 Fix direct cursor leaving screen trail
It will be available in 24.2.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
(In reply to Heiko Tietze from comment #19)
> Rizal, can you create a nice cursor image for this?
> See also https://gerrit.libreoffice.org/c/core/+/153099
How it should looks?
(In reply to Rizal Muttaqin from comment #21)
> (In reply to Heiko Tietze from comment #19)
> > Rizal, can you create a nice cursor image for this?
> > See also https://gerrit.libreoffice.org/c/core/+/153099
> How it should looks?
I have described the shape in this issue:
Bug 155943 - Three New pointer shapes for direct cursor mode
And instead of 3 cursors, even 2 with the exact same look of the current direct cursor on 7.5 (or before that) is fine for now. They can be seen in attachment 188007 [details].