Bug 359681

Summary:	Juk should stay in random/loop mode on shutdown/start
Product:	[Applications] juk	Reporter:	William L. Thomson Jr. <wlt-ml>
Component:	general	Assignee:	Scott Wheeler <wheeler>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	mpyne
Priority:	NOR
Version:	3.11
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:	https://invent.kde.org/kde/juk/commit/444a4c9f102ddbb50baf1f0f4367c2f9ced8a4c7	Version Fixed In:

Description William L. Thomson Jr. 2016-02-22 20:03:33 UTC

Every time I log in and/or start Juk, I must go and select random play and loop playlist. its really annoying. It would be nice if Juk would remember its previous state and start on that. Maybe even where it was at song wise. But really just want it to stay in random mode with the play list looped. Thank you for consideration of this request, and hopefully adding it ASAP!

Reproducible: Always

Steps to Reproduce:
1. Start Juk
2. Select Random Play and Loop Playlist
3. Shutdown Juk, or log out of session
4. Start Juk and repeat #2

Actual Results:  
Juk resets back to regular play in order, play list not looped.

Expected Results:  
When Juk is started it should remain in Random Play and Loop Playlist if it was selected when shutdown.

Comment 1 William L. Thomson Jr. 2016-02-22 20:05:11 UTC

This is actually with Juk 3.12 using KDE Platform 4.14.16, on Gentoo Plasma 5 desktop. May be a conflict between 4.x and 5.x libraries/backends.

Comment 2 abogical 2019-12-27 00:43:14 UTC

Git commit 444a4c9f102ddbb50baf1f0f4367c2f9ced8a4c7 by Abdel-Rahman Abdel-Rahman.
Committed on 27/12/2019 at 00:34.
Pushed by mpyne into branch 'release/19.12'.

Save config after it is closed by the window manager

This is a bug that has resurfaced with commit
d4dc1bee178b0361069d6d94e463368084d0e8d4 as the aboutToQuit signal is
emitted after the JuK singleton is destroyed, thus it does not
trigger the saveConfig slot.

M  +3    -0    juk.cpp

https://invent.kde.org/kde/juk/commit/444a4c9f102ddbb50baf1f0f4367c2f9ced8a4c7