Bug 458404 - Graphical artifacts in text when scrolling on X11
Summary: Graphical artifacts in text when scrolling on X11
Status: REPORTED
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.101.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: Not decided
Assignee: kdelibs bugs
URL:
Keywords: X11-only
Depends on:
Blocks:
 
Reported: 2022-08-27 20:58 UTC by Alexander Wilms
Modified: 2025-02-24 17:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot (110.78 KB, image/png)
2022-08-27 20:58 UTC, Alexander Wilms 		Details
Screen recording (2.24 MB, video/x-matroska)
2022-08-27 20:59 UTC, Alexander Wilms 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Wilms 2022-08-27 20:58:59 UTC 
Created attachment 151649 [details]
Screenshot

SUMMARY
Scrolling though the list of updates causes artifacts in the displayed text. I was only able to reproduce this glitch on X11, but not on Wayland.


STEPS TO REPRODUCE
1. Wait for package updates to be available
2. Click on update applet
3. Scroll through text

OBSERVED RESULT
Graphical artifacts

EXPECTED RESULT
Hinted, antialiased text

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220825
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.2-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 480 Graphics
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B250M-DS3H

ADDITIONAL INFORMATION
Comment 1 Alexander Wilms 2022-08-27 20:59:23 UTC 
Created attachment 151651 [details]
Screen recording
Comment 2 Alexander Wilms 2023-01-08 00:56:22 UTC 
I can reproduce this in NeoChat when clicking and dragging the chat history, but not MuseScore, which uses QML for its interface. Therefor, I think it's not QML-specific, but caused by Kirigami.
Comment 3 TraceyC 2025-02-24 17:58:47 UTC 
Adding the x11-only keyword