Bug 487806 - Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background
Summary: Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background
Status: RESOLVED DUPLICATE of bug 487717
Alias: None
Product: plasmashell
Classification: Plasma
Component: Image Wallpaper (show other bugs)
Version: git-stable-Plasma/6.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2024-05-30 18:14 UTC by pikaphase
Modified: 2024-06-06 12:10 UTC (History)
4 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description pikaphase 2024-05-30 18:14:05 UTC 
SUMMARY
Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background in KDE Plasma 6.1 Beta (6.0.90).

STEPS TO REPRODUCE
1. Use Plasma Wayland session. 
1. Change scaling. 

OBSERVED RESULT
Incorrectly scaled background.

EXPECTED RESULT
Correctly scaled background / No black spaces.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.90
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Graphics
Comment 1 pikaphase 2024-05-30 18:16:53 UTC 
I couldn't upload the video reproducing the issue here, so: https://streamable.com/mh7gat
Comment 2 David Edmundson 2024-05-31 04:26:04 UTC 
I cannot reproduce.

If you right click in the black area do you get a context menu?
Comment 3 pikaphase 2024-05-31 08:10:46 UTC 
(In reply to David Edmundson from comment #2)
> I cannot reproduce.
> 
> If you right click in the black area do you get a context menu?

I don't. https://streamable.com/cx7xzg
Comment 4 pikaphase 2024-05-31 08:20:01 UTC 
When I log out from session and log back in, background gets properly scaled to value I selected before. But if I choose a different value, it happens again.
Comment 5 Marco Martin 2024-06-06 12:10:02 UTC 

*** This bug has been marked as a duplicate of bug 487717 ***