Bug 488206 - Widget config windows' custom sizes no longer remembered
Summary: Widget config windows' custom sizes no longer remembered
Status: RESOLVED DUPLICATE of bug 477991
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 6.0.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2024-06-08 12:01 UTC by Kalzi
Modified: 2025-02-07 00:25 UTC (History)
4 users (show)

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


Attachments
screenshot to explain the issue (3.21 MB, image/png)
2024-06-08 12:01 UTC, Kalzi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kalzi 2024-06-08 12:01:08 UTC
Created attachment 170270 [details]
screenshot to explain the issue

SUMMARY
Every time I right-click the desktop and choose the first option to change the wallpaper, the window is too small, and I have to resize it every single time to be able to see more wallpapers

STEPS TO REPRODUCE
Right-click the desktop and choose first option to change wallpaper

OBSERVED RESULT
wallpaper window is too small

EXPECTED RESULT
bigger window that shows more than just two wallpapers

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Comment 1 Nate Graham 2024-06-10 18:51:05 UTC
There are two issues going on here:
1. The window size remembering feature seems to be broken for widget settings windows.
2. Even if that were fixed, all widgets share the same window size, so we can't make only this window open at a larger size without affecting everything else as well.

Let's use this to track issue #1. For #2, I've opened Bug 488318.
Comment 2 Ismael Asensio 2025-02-07 00:25:35 UTC
*** This bug has been marked as a duplicate of bug 477991 ***