https://bugs.kde.org/show_bug.cgi?id=380223
--- Comment #2 from Arek Guzinski <ker...@ag.de1.cc> --- Ok... so i found ~/.kde/share/config/amarokrc In there was that part: [Phonon::AudioOutput] Amarok_Volume=0.79 [Playback] FadeoutOnPause=false Master Volume=0 Then i changed "Master Volume" to 50, which seems to have fixed the issue. After playing around for a bit, i found that "Amarok_Volume" is the last volume set via amarok's volume control, while "Master Volume" is what i set via any pulsaudio-aware volume control. Changing volume via amarok, also changes pa volume for it, but not vica versa (it does actually change the volume, but that is not reflected inside amarok). So, (only) if i set volume via amarok first and then in pa, those two values differ... and the second one is loaded @startup. (note: this is *not* what i did every time before) While this explains part of it, i still don't understand why amarok did not correctly save the "Master Volume" before, nor why it does now. (meaning: i am unable to reproduce the problem now) In any case you were right in that there must have been something wrong with the config. But: shouldn't those two volume values always be the same? What is the point of this information beeing saved twice? And most important: is amarok not syncing to changes via pa a bug? -- You are receiving this mail because: You are watching all bug changes.
