Summary: | every time i log into my computer the sound volume is back at 100%!!! | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | ombu2c |
Component: | alsa | Assignee: | pulseaudio-bugs |
Status: | RESOLVED MOVED | QA Contact: | pulseaudio-bugs |
Severity: | critical | ||
Priority: | highest | CC: | benbullard79, ewtoombs, lennart |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
URL: | https://goo.gl/QUZMVn | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | sound goes back to 100% with each login |
Description
ombu2c
2015-10-23 01:12:44 UTC
Have you tried disabling that super-buggy deferred volume (even if you have already disabled flat-volume)? Last time I checked this is happening in Mageia 6 as well. https://bugs.mageia.org/show_bug.cgi?id=19377 https://forums.mageia.org/en/viewtopic.php?f=15&t=11614 I'm not a developer and my knowledge on this issue is lacking but I've wondered for some time why Linux/PulseAudio developers don't incorporate "a max login volume" setting as a feature? It just seems so intuitive to me. Anyone who's ever lived with pets or very young children should realize this right? Or in an apartment next to sensitive neighbors? Or is this something that could/should be done as a part of Desktop software? If say KDE/Plasma5 has a login/logout sound shouldn't it have a volume control and ability to set a max volume for both safety and good citizenship? I'm getting the same thing for pulseaudio instances started from audio programs in ssh sessions. (In reply to Ben Bullard from comment #2) > Last time I checked this is happening in Mageia 6 as well. > > https://bugs.mageia.org/show_bug.cgi?id=19377 > > https://forums.mageia.org/en/viewtopic.php?f=15&t=11614 I got an "unable to connect" error for the forum link. The Mageia bug report sounds like it could very well be caused by some application playing something at 100% volume while having flat volumes enabled. > I'm not a developer and my knowledge on this issue is lacking but I've > wondered for some time why Linux/PulseAudio developers don't incorporate "a > max login volume" setting as a feature? It just seems so intuitive to me. > Anyone who's ever lived with pets or very young children should realize this > right? Or in an apartment next to sensitive neighbors? Unfortunately, an idea of a nice feature isn't sufficient to make it happen. Someone has to make implementing it their highest priority. So far everyone has been working on something else instead. (In reply to Eric Toombs from comment #3) > I'm getting the same thing for pulseaudio instances started from audio > programs in ssh sessions. Do you have flat volumes disabled in daemon.conf? When you use ssh and this happens, are there multiple pulseaudio instances running? What does "ps aux | grep pulse" say? (In reply to Tanu Kaskinen from comment #4) > (In reply to Ben Bullard from comment #2) I was trying Mageia at the time. I no longer have it installed. Sorry if I caused confusion or 'noise'. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/176. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.