Bug 485926 - Text display issues in Discover when resizing window on KDE Plasma 6.0.4
Summary: Text display issues in Discover when resizing window on KDE Plasma 6.0.4
Status: RESOLVED UPSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 6.0.4
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-21 22:03 UTC by dominickator122102
Modified: 2024-05-03 11:50 UTC (History)
2 users (show)

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


Attachments
As you can see, the text "jumps around" and looks all garbled while resizing the window. (3.61 MB, video/mp4)
2024-04-21 22:03 UTC, dominickator122102
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dominickator122102 2024-04-21 22:03:18 UTC
Created attachment 168769 [details]
As you can see, the text "jumps around" and looks all garbled while resizing the window.

Environment:

    Operating System: Arch Linux
    KDE Plasma Version: 6.0.4
    Application: KDE Discover
    KDE Frameworks: 6.1.0
    Kernel Version: 6.8.7-arch1-1 (64-bit)
    Qt Version: 6.7.0

Description:
When resizing the window in Discover, the text appears jumbled and seems to "jump around". This issue seems to arise only when I have the refresh rate set to that of my monitor, 165hz. 

Steps to Reproduce:

    Open the KDE Discover application.
    Resize the window by dragging one of the corners.
    Observe the text of Chromium or VLC for instance, it seems to jump around, and looks very distracting.

Expected Result:
The text should adjust cleanly without overlapping or getting cut off, maintaining readability and layout integrity regardless of window size.
Comment 1 dominickator122102 2024-04-21 22:05:07 UTC
My system specs:

GPU: RX 6700XT
CPU: Ryzen 7 5700
RAM: 32GB DDR4
Comment 2 Harald Sitter 2024-05-03 11:50:23 UTC
Alas, that is entirely within the control of Qt, not Discover. You'll probably want to file a bug upstream about that.