This started fairly recently, about a week or so.
When the PC starts up audio volume would be set at 74%, this is extremely annoying, I have to remember to manually lower it after I log in, otherwise the first sound will beat the **** out of my eardrums.
I tried manually saving the session after lowering the volume and I tried explicitly setting fiat-volume to no in the pulse config, both to no avail.
Before this problem wasn’t happening, so I imagine some update might have broken something.
Which Desktop GUI are you using?
- The issue may be caused by the user specific TDB databases – does this behaviour also occur with a freshly configured new user?
If the issue doesn’t appear with a new, fresh, user then –
- Logout the graphical session of the affected user.
- Login as the affected user by means of a VT – tty1 … tty6 – <Ctrl-Alt-F1> … <Ctrl-Alt-F6>.
- Remove every thing in the affected user’s ‘~/.config/pulse/
’ directory. - Logout of the VT. - Login to the affected user’s graphical session and setup the Audio again.
I have no idea if this could be Tumbleweed specific. Nominally, the last level one used in audio, should be saved and kept for the next reboot - at least that is my understanding.
On older openSUSE versions, what worked sometimes was to set “flat-volumes = no” in /etc/pulse/daemon.conf (but I have read did not work all the time).
I suppose (if relevant to Tumbleweed) you could try to delete ~/.config/pulse/ and/or ~/.pulse (if present). That may revert all volumes to the defaults (which may be good or bad dependent on how you like the default levels).
Also, to quote from an alsa developer for a MUCH OLDER version of openSUSE:[INDENT=2] if this happens after reboot, it could be the wrongly saved mixer state. There are a few layers saving/restoring the mixer state, alsactl invoked via udev, PulseAudio, and kmix.
A possible fix would be to clean up the config. Go to runlevel 3 once, login as root, kill all pending Pulse Audio processes (if any). Then adjust via “alsamixer -c0”, and run “alsactl store”. This resets the mixer restored via alsactl.
[/INDENT]
I have no idea if that true for Tumbleweed.
You may check Save/Restore Sound Card State:
**i3-4130:~ #** journalctl -b -1 -o short-monotonic -u alsa-restore.service
-- Journal begins at Sun 2021-07-11 15:51:53 CEST, ends at Thu 2021-07-15 12:33:10 CEST. --
4.008177] i3-4130 systemd[1]: Starting Save/Restore Sound Card State...
4.015056] i3-4130 alsactl[837]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA Intel HDMI at 0xf0534000 irq 32)
4.015056] i3-4130 alsactl[837]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
4.016254] i3-4130 systemd[1]: Finished Save/Restore Sound Card State.
374.506988] i3-4130 systemd[1]: Stopping Save/Restore Sound Card State...
374.563556] i3-4130 systemd[1]: alsa-restore.service: Deactivated successfully.
374.563668] i3-4130 systemd[1]: Stopped Save/Restore Sound Card State.
**i3-4130:~ #**
Maybe this bug:
https://bugzilla.suse.com/show_bug.cgi?id=1188196
I’ve added a comment to <https://bugzilla.opensuse.org/show_bug.cgi?id=1188196> – it has been mirrored over to the SUSE Bug Report …
- BTW, I’m using Leap 15.3.
Basically, if you touch PipeWire with anything – for example with “pw-mon” – a couple of PipeWire processes will start for that user.
Therefore –
- systemctl --user mask pipewire.service
- systemctl --user mask pipewire.socket
- systemctl --user mask pipewire-media-session.service
> file ~/.config/systemd/user/*
/home/xxx/.config/systemd/user/pipewire-media-session.service: symbolic link to /dev/null
/home/xxx/.config/systemd/user/pipewire.service: symbolic link to /dev/null
/home/xxx/.config/systemd/user/pipewire.socket: symbolic link to /dev/null
>
- The directory ‘~/.config/systemd/user’ is automatically created with the first call to “systemctl --user mask «pipewire – whatever
»”
I suspect that, simply removing the PipeWire packages will not really help –
> rpm --query --whatrequires pipewire
pipewire-modules-0.3.24-4.3.1.x86_64
pipewire-spa-plugins-0_2-0.3.24-4.3.1.x86_64
pipewire-lang-0.3.24-4.3.1.noarch
> rpm --query --whatrecommends pipewire
libpipewire-0_3-0-0.3.24-4.3.1.x86_64
xdg-desktop-portal-kde-5.18.5-bp153.1.27.x86_64
> rpm --query --whatsuggests pipewire
no package suggests pipewire
>
Taking the alternative route and removing PulseAudio is also not exactly easy –
> rpm --query --whatrequires pulseaudio
alsa-plugins-pulse-1.2.2-1.55.x86_64
pulseaudio-lang-14.2-4.2.noarch
pulseaudio-module-zeroconf-14.2-4.2.x86_64
pulseaudio-module-x11-14.2-4.2.x86_64
pulseaudio-module-gconf-14.2-4.2.x86_64
pulseaudio-module-bluetooth-14.2-4.2.x86_64
> rpm --query --whatrecommends pulseaudio
patterns-kde-kde_plasma-20181130-lp153.2.8.noarch
> rpm --query --whatsuggests pulseaudio
patterns-base-base-20200505-lp153.6.1.x86_64
>
Pipewire units exist:
karl@erlangen:~> systemctl list-unit-files --user 'pipewire*'
UNIT FILE STATE VENDOR PRESET
pipewire-media-session.service **enabled enabled **
pipewire.service disabled disabled
pipewire.socket **enabled enabled **
3 unit files listed.
karl@erlangen:~>
They don’t get loaded and don’t interfere with pulseaudio:
karl@erlangen:~> systemctl list-units --user 'pipewire*'
UNIT LOAD ACTIVE SUB DESCRIPTION
**0 loaded units listed.** Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
karl@erlangen:~>
Thus I refrain from tinkering.
Really?
- Simply “ ps -u «Username
» | grep -i ‘wire’ ” – strange that a process named “pipewire” and “pipewire-media-session” running under that Username are present …
This is also mentioned in the Bug Report …
**
Leap-15-3:~ #** ps -u karl | grep -i 'wire'
**Leap-15-3:~ #**
karl@Leap-15-3:~> systemctl --user status pipewire*
**●** pipewire.socket - Multimedia System
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: enabled)
Active: **active (listening)** since Thu 2021-07-15 20:03:13 CEST; 4min 2s ago
Triggers: ● pipewire.service
Listen: /run/user/1000/pipewire-0 (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/pipewire.socket
Jul 15 20:03:13 Leap-15-3 systemd[1579]: Listening on Multimedia System.
karl@Leap-15-3:~>
karl@Leap-15-3:~> journalctl -b --user -u '*pipe*'
-- Logs begin at Wed 2021-07-07 12:07:22 CEST, end at Thu 2021-07-15 20:08:49 CEST. --
Jul 15 20:03:13 Leap-15-3 systemd[1579]: Listening on Multimedia System.
karl@Leap-15-3:~>
**Leap-15-3:~ #** ll /var/lib/alsa/asound.state
-rw-r--r-- 1 root root 18004 Jul 15 06:01 /var/lib/alsa/asound.state
**Leap-15-3:~ #** journalctl -b -o short-monotonic -u *alsa* -u *sound*
-- Logs begin at Wed 2021-07-07 11:53:27 CEST, end at Thu 2021-07-15 20:08:49 CEST. --
5.563724] Leap-15-3 systemd[1]: Starting Save/Restore Sound Card State...
5.563873] Leap-15-3 systemd[1]: Condition check resulted in Manage Sound Card State (restore and store) being skipped.
5.566003] Leap-15-3 systemd[1]: Finished Save/Restore Sound Card State.
5.567037] Leap-15-3 systemd[1]: Starting Load extra kernel modules for sound stuff...
5.568808] Leap-15-3 systemd[1]: sound-extra.service: Succeeded.
5.568977] Leap-15-3 systemd[1]: Finished Load extra kernel modules for sound stuff.
5.569279] Leap-15-3 systemd[1]: Reached target Sound Card.
**Leap-15-3:~ #**
Same here. Always resets to 74%. Same after a power save. It looks like an update broke something.
I found a quick work-around. Open Yast -> Hardware -> Sound. Select your sound card and click on Edit at the bottom of the window. Find and select “Reset controller in power save mode”, then click Edit at the bottom. Click on the pull-down arrow in that dialog box and select 0 and click OK. Click Next, then OK. Yast will reset you sound card. Back out of Yast. You are good to go. I checked on a restart, and the volume remained where I left it.
Disregard all after good morning. The change seemed to work initially, but later went back to 74% on its own w/o reset or power save. Not sure how it did that.
Show what is going on as already suggested in post #4.
; sudo journalctl -b -o short-monotonic -u alsa-restore.service
-- Journal begins at Fri 2021-07-16 11:58:37 +04, ends at Fri 2021-07-16 16:01:29 +04. --
7.126003] home systemd[1]: Starting Save/Restore Sound Card State...
7.127992] home alsactl[1150]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfce60000 ir>
7.127992] home alsactl[1150]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
7.128404] home alsactl[1150]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HD-Audio Generic at 0xfcd0000>
7.128404] home alsactl[1150]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -6
7.129728] home systemd[1]: Finished Save/Restore Sound Card State.
Yes, the service restores the audio level. But does it save at shutdown reboot? Use ‘journalctl -b -1 …’.
**erlangen:~ #** journalctl -b -1 -o short-monotonic -u alsa-restore.service
-- Journal begins at Tue 2021-07-13 20:31:12 CEST, ends at Fri 2021-07-16 14:16:42 CEST. --
4.380638] erlangen systemd[1]: Starting Save/Restore Sound Card State...
4.383878] erlangen alsactl[1048]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xdfe60000 irq 140)
4.383878] erlangen alsactl[1048]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
4.384412] erlangen systemd[1]: Finished Save/Restore Sound Card State.
6647.856704] erlangen systemd[1]: Stopping Save/Restore Sound Card State...
6647.898214] erlangen systemd[1]: alsa-restore.service: Deactivated successfully.
6647.898267] erlangen systemd[1]: Stopped Save/Restore Sound Card State.
**erlangen:~ #**
Check file:
**erlangen:~ #** ll /var/lib/alsa/asound.state
-rw-r--r-- 1 root root 17997 Jul 15 20:02 /var/lib/alsa/asound.state
**erlangen:~ #**
; journalctl -b -1 -o short-monotonic -u alsa-restore.service
Specifying boot ID or boot offset has no effect, no persistent journal was found.
; ll /var/lib/alsa/asound.state
Permissions Size User Date Modified Name
.rw-r--r-- 22k root 17 Jul 02:31 /var/lib/alsa/asound.state
also I tried removing the configs:
; rm -rf ~/.config/{pulse,pipewire}
but that didn’t help either.
[QUOTE=AlexCzar;3049867]
; journalctl -b -1 -o short-monotonic -u alsa-restore.service
Specifying boot ID or boot offset has no effect, no persistent journal was found.
As root you may create the empty folder /var/log/journal This will trigger persistent journalling. Verify by running:
[FONT=monospace]**erlangen:~ #** du -hd1 /var/log/journal/
32M /var/log/journal/94f3af277bac4a8eb57da425c9677379
32M /var/log/journal/
**erlangen:~ #**[/FONT]
Reboot and try again.
Please note this Planet openSUSE article on PipeWire: <https://cubiclenate.com/2021/07/17/pipewire-audio-server-on-opensuse-tumbleweed/>.
-
N.B.
: Tumbleweed and PulseEffects version 5.0.0 … - Leap 15.3
– IMHO, currently, forget about PipeWire – “–user” mask it …
> LANG=C pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 34
Server Protocol Version: 34
Is Local: yes
Client Index: 14
Tile Size: 65472
User Name: xxx
Host Name: yyy
Server Name: pulseaudio
Server Version: 14.2-rebootstrapped
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_08_00.6.analog-stereo
Default Source: alsa_input.pci-0000_08_00.6.analog-stereo
Cookie: 7de3:894d
>
After enabling journal:
; journalctl -b -1 -o short-monotonic -u alsa-restore.service
-- Journal begins at Sun 2021-07-18 15:40:16 +04, ends at Sun 2021-07-18 15:56:24 +04. --
7.333650] home systemd[1]: Starting Save/Restore Sound Card State...
7.335847] home alsactl[1072]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfce60000 ir>
7.335847] home alsactl[1072]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
7.336385] home alsactl[1072]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HD-Audio Generic at 0xfcd0000>
7.336385] home alsactl[1072]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
7.336797] home alsactl[1072]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -2
7.346242] home systemd[1]: Finished Save/Restore Sound Card State.
899.099493] home.czar.io systemd[1]: Stopping Save/Restore Sound Card State...
899.118640] home.czar.io systemd[1]: alsa-restore.service: Deactivated successfully.
899.118826] home.czar.io systemd[1]: Stopped Save/Restore Sound Card State.
Also:
; pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 34
Server Protocol Version: 34
Is Local: yes
Client Index: 9
Tile Size: 65472
User Name: czar
Host Name: host.local
Server Name: pulseaudio
Server Version: 14.2-rebootstrapped
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_0f_00.3.analog-stereo
Default Source: alsa_input.usb-Samson_Technologies_Samson_Meteor_Mic-00.analog-stereo
Cookie: d771:be2a
Interesting, I’ve switched to pipewire and the issue still appeared on the first restart after pipewire installation, but has not returned after the second, third, fourth and fifth restarts.
I’ll update if anything changes. Pipewire seems to be doing fine otherwise as well, sound works, recording (tested in Zoom and OBS) also works.
; pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 34
Server Protocol Version: 35
Is Local: yes
Client Index: 97
Tile Size: 65472
User Name: czar
Host Name: host.local
Server Name: PulseAudio (on PipeWire 0.3.31)
Server Version: 14.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_0f_00.3.analog-stereo
Default Source: alsa_input.usb-Samson_Technologies_Samson_Meteor_Mic-00.analog-stereo
Cookie: 456a:8898