Version: 2.4.3 (using KDE 4.7.1) OS: Linux I have had dynamic playlist mode enabled for some months and would like to turn it off; however, attempting to toggle the "Turn dynamic playlist on" button in the Dynamic Playlist media source has no effect. In the previous version of Amarok (2.4.2), attempting to disable dynamic mode would cause a crash, and when restarted, dynamic mode would still be enabled. Deleting the config files ~/.kde4/share/apps/amarok/* and ~/.kde4/share/config/amarok* resets all other configuration, but does not restore the playlist to normal mode. Reproducible: Always Steps to Reproduce: With the dynamic playlist mode enabled, press the "Turn dynamic playlist on" button in the Dynamic Playlist media source. Actual Results: Nothing happens. Expected Results: Dynamic playlist mode is disabled. OS: Linux (x86_64) release 3.0-ARCH Compiler: gcc
Hi James, the behavior you are seeing is quite strange. You are describing three impossible things: 1. 2.4.2 crash when turning off the dynamic playlist you are the first to report that 2. not being able to switch of the dynamic mode 3. removing the config files not turning it off. I assuming that you see the "Dynamic Mode enabled" banner on top of the playlist. I also assume that the "switch dynamic mode" toggle button actually toggles when you press it. Do you have a special Amarok build? Can you attach the debug output when you press the toggle button (while Amarok is started with --debug) and also attach the amarok config file. Thanks
Created attachment 63836 [details] My Amarok configuration file
Hi Ralf, I do indeed have the "Dynamic Mode Enabled" banner at the top of my playlist. However, the "switch dynamic mode" toggle button does not toggle when I press it -- it merely remains depressed. My Amarok installation is just the standard one from the ArchLinux repositories.
The debug output when I press the toggle button is as follows: amarok(6138)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: amarok: BEGIN: void Playlist::Actions::playlistModeChanged() amarok: [Playlist::Actions] Dynamic mode: true amarok: BEGIN: void Playlist::DynamicTrackNavigator::activePlaylistChanged() amarok: END__: void Playlist::DynamicTrackNavigator::activePlaylistChanged() [Took: 0s] amarok: BEGIN: void Playlist::Dock::showDynamicHint() amarok: END__: void Playlist::Dock::showDynamicHint() [Took: 0s] amarok: END__: void Playlist::Actions::playlistModeChanged() [Took: 0s]
Very strange. The button is just a normal tool button and should always toggle. Your config file does not have a "Dynamic Mode=true" and the output shows that you just switched the dynamic mode on. Can you please try to reinstall Amarok? Thanks, Ralf
Reinstalling Amarok has no effect.
Thank you for the feedback.
The problem appears to exist still on Amarok 2.5. However please do provide your valuable feedback. Thanks
I can confirm that the problem persists with Amarok 2.5.0.
Setting status to confirmed.
I am sorry. I am completely baffled by this bug. How about write protected settings files? Can you create a new test user and try it again?
I can't reproduce here at all on Amarok 2.5, KDE 4.8 RC1 on Kubuntu 11.10
I tried creating a new user -- the problem doesn't seem to affect them.
James: my guess is that you've got another amarok config file hanging around somewhere. Try both these commands: find $HOME/.kde* -name amarokrc or for d in $HOME/.kde*; do grep -ir 'dynamic mode' $d/share/config; done Some linux distributions switched KDE config directories midway through the kde-4 series, or if you have a home directory that was used in two different distributions, they could have put the KDE config files in two different places. So you'd end up with two different amarokrc files, both of which are being read, but only one of which can be written to.
Thankyou, Soren -- that seems to have identified the problem. The following two lines were in the file ~/.kde4/share/config/kdeglobals: Dynamic Mode=true Last Dynamic Mode=Default Deleting these lines turned off Dynamic Mode, and it can now be toggled off and on as it ought to be.
James, thanks for figuring that out. I was not aware that there are kde global options that override local options. Note to myself: Ensure that amarok option names are sufficiently unique.
I have no idea how those settings got moved into kdeglobals, and we haven't had any reports of anyone else having this problem. Closing the bug, because I don't think there's anything we need to change in the Amarok code.