Control: tags -1 moreinfo On Tue, Nov 6, 2018 at 7:27 PM Alexandre Vaissiere <ava...@fmiw.org> wrote:
> Package: pulseaudio > Version: 12.2-2 > Severity: normal > > Dear Maintainer, > > * Context > > - I use a Lenovo Thinkpad T480. > - I have the following in my ~/.config/pulse/default.pa: > > $ cat ~/.config/pulse/default.pa > .include /etc/pulse/default.pa > load-module module-switch-on-connect > > - I generally mute my mic and speakers, unmuting them only if needed. > > * Expected behaviour > > When I restart my machine, I expect that the sound/mic state is properly > restored: > - If sound/mic was muted at shutdown, I expect for it to be muted at > startup, > - If sound/mic was unmuted at shutdown, I expect for it to be unmuted at > startup. > > * Current behaviour > > Currently, whatever the state was at shutdown, mic and sound are *unmuted* > at > startup. > > * Extra infomation > > Now it almost work. When logging in my session at startup, the leds > indicating > muteness are on, but after some seconds are off again. As if something got > executed after the restore by pulseaudio, and unmuted the mic/sound. > > Are provided two files: > > - pulseaudio-start1.log are the log in debug of pulseaudio of a first > startup. > As soon as possible, the mic and sound were muted using the appropriate > shortcut (Fn+F1 and Fn+F4). Then the machine is rebooted. The logs were > fetched using grep 'pulseaudio\[1865\]' /var/log/daemon.log after the > reboot > > - pulseaudio-start2.log are the log in debug of pulseaudio on the second > startup, where the sound/mic are first muted then, 5 or 10s later > automatically unmuted for an unknown reason. The logs were fetched using > journalctl --user-unit pulseaudio. > This doesn't look like pulseaudio, but that someone is changing the mute level. The first potential culprit is gnome-shell. Does this problem happen if you log into a console instead of gnome? -- Saludos, Felipe Sateler
