Bug 461480

Summary: cursor leaves marks on attached reference image when not drawing
Product: [Applications] krita Reporter: Emma <emma.rounsville>
Component: Tools/Reference ImagesAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED LATER    
Severity: normal CC: emma.rounsville, halla
Priority: NOR    
Version First Reported In: 5.1.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: example of the white trace marks appearing on an added reference image

Description Emma 2022-11-06 03:27:43 UTC
Created attachment 153509 [details]
example of the white trace marks appearing on an added reference image

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Use the Reference Image tool to add a reference image (any file type) to a Krita document
2. Select any of the following: Freehand Brush Tool, Line Tool, Rectangle Tool, Ellipse Tool, Polygon Tool, Polyline Tool, Dynamic Brush Tool, Multibrush Tool, or Smart Patch Tool
3. Move cursor across canvas without drawing or clicking

OBSERVED RESULT
White trace marks appear wherever cursor is moved across canvas

EXPECTED RESULT
No trace marks should appear

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
The trace marks disappear when the cursor leaves the canvas window, or when another button is pressed, but are intrusive enough to make using the reference tool feature while drawing difficult. Attached is an example screenshot of the marks on a random reference image added using the tool.
Comment 1 Halla Rempt 2025-06-12 09:54:55 UTC
Sorry for the late reply. I cannot reproduce this issue, but I have heard this can happen if canvas acceleration is disabled or if there's a bug in the gpu driver. I understand it's very inconvenient but there really isn't anything we can do about this :-(