514963 – Layout Amarok is not restored after restart

Bug 514963 - Layout Amarok is not restored after restart

Summary: Layout Amarok is not restored after restart

Status:	CONFIRMED

Alias:	None

Product:	amarok
Classification:	Applications
Component:	Toolbar (other bugs)
Version First Reported In:	3.3.2
Platform:	Other Linux

Importance:	NOR normal
Target Milestone:	kf5
Assignee:	Amarok Bugs

URL:
Keywords:

Depends on:
Blocks:

Reported:	2026-01-23 08:41 UTC by Johan Wauters
Modified:	2026-01-25 21:10 UTC (History)
CC List:	2 users (show)

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

Attachments
before (197.90 KB, image/png) 2026-01-23 08:41 UTC, Johan Wauters	Details
after (123.28 KB, image/png) 2026-01-23 08:42 UTC, Johan Wauters	Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Johan Wauters 2026-01-23 08:41:34 UTC

Created attachment 188807 [details]
before

SUMMARY
vertical devider does not stay in place after restarting amarok.
Layout locked is enabled.
Mediasources and playlist are enabled, Content is disabled.
I have the vertical divider in the middle, but after restart it is way more to the left side.

STEPS TO REPRODUCE
1. setup layout with content disabled
2. set the divider in the center of the screen, equal width of both other windows
3. close amarok (rclick botom richt and close amarok
4. restart Amarok 3.3.2

OBSERVED RESULT
Layout has changed

EXPECTED RESULT
Layout should be the same as before closing amarok

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora kde 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0 
Qt Version: 6.10.1

ADDITIONAL INFORMATION

Comment 1 Johan Wauters 2026-01-23 08:42:20 UTC

Created attachment 188808 [details]
after

Comment 2 Tuomas Nurmi 2026-01-25 21:10:38 UTC

Thank you for the report! I had seen some indications of this earlier but had been wondering why I couldn't reliably reproduce this. Now after I inspected a bit, it seems that having an old-enough Amarok config file (possibly originating from Qt4 times?) prevents this bug from happening. Will fix soon.