Summary: | kmix forgets volume settings at startup or login after session restart | ||
---|---|---|---|
Product: | [Applications] kmix | Reporter: | apog <apogarte> |
Component: | Backend: Pulseaudio | Assignee: | Colin Guthrie <colin> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | esken |
Priority: | NOR | ||
Version: | 3.9 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
apog
2012-04-18 10:47:11 UTC
I think this might be the same issue as the one from bug 249180. I will not directly merge both bugs, but assign it over to the Pulseaudio backend maintainer, so he can either merge them, not merge them or give them back to me. Yeah I think this is ultimately a dupe. The issue was that kmixctl (a command line app) didn't recognise PulseAudio as running and thus "restored" volumes (normally if PulseAudio is detected, it should refuse to restore volumes - just like if the tick boxes were always turned off) Sadly, the volumes were *saved* from kmix (the GUI app) which DID detect PA properly and thus didn't ever save anything. Thus kmixctl would always restore null or default volumes which have no relation to the previous volume. This should now be fixed in kmix 4.8.3 *** This bug has been marked as a duplicate of bug 249180 *** |