Bug 493880 - panel and desktop management does not save panel positions
Summary: panel and desktop management does not save panel positions
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (other bugs)
Version First Reported In: 6.1.5
Platform: Ubuntu Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-30 17:26 UTC by Alex
Modified: 2024-10-01 07:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 6.2.0
Sentry Crash Report:

Attachments
panels positions (711.61 KB, image/jpeg)
2024-09-30 17:26 UTC, Alex 		Details
panels positions before reboot (629.44 KB, image/jpeg)
2024-09-30 17:27 UTC, Alex 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2024-09-30 17:26:43 UTC 
Created attachment 174235 [details]
panels positions

SUMMARY
top panel moves constantly when restarting. 
i would want to create configuration as in ubuntu (top panel with left dock)

STEPS TO REPRODUCE
1. add panel #1 to top side (full with)
2. add panel #2 to left side  (fit content height)
3. move the top panel so that it overlaps the panel to the left (with Panel and Desktop Management)
4. reboot 

OBSERVED RESULT
top panel does not overlaps left panel

EXPECTED RESULT
top panel should overlaps left panel after reboot 

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Operating System: TUXEDO OS 3 (ubuntu based OS)
Kernel Version: 6.11.0-102007-tuxedo (64-bit)
Graphics Platform: Wayland
Graphics Processor: Mesa Intel® Graphics

ADDITIONAL INFORMATION
screenshots:
https://imgur.com/AtGQJg7 
https://imgur.com/a/egxjVV3
Comment 1 Alex 2024-09-30 17:27:41 UTC 
Created attachment 174236 [details]
panels positions before reboot
Comment 2 Nate Graham 2024-09-30 21:06:19 UTC 
Aha, this! It's already fixed in 6.2.0.
Comment 3 Alex 2024-10-01 07:29:53 UTC 
(In reply to Nate Graham from comment #2)
> Aha, this! It's already fixed in 6.2.0.

ok, thanks