Created attachment 133547 [details] log of the upgrade process SUMMARY After the upgrade of the 2020-11-20 and after a reboot the sound device (soundblaster 2zs) that I used is no longer available. STEPS TO REPRODUCE update kde neon to the latest versions OBSERVED RESULT Audiocard/device no longer available EXPECTED RESULT audiocard/device be available SOFTWARE/OS VERSIONS KDE neon 5.20 KDE Plasma: 5.20.3 KDE Frameworks: 5.76.0 Qt: 5.15.1 kernel: 5.4.0-55-generic ADDITIONAL INFORMATION Don’t know if this is related to the other tickets about pipewire/pulseaudio. This one is a bit diferent, it’s not that no sound is available, it’s the fact the audiocard and its profiles (analog/etc) are not even available therefore no sound. When booting the usual speaker “pop” sound, like when you turn on a speaker system, is made. When in terminal and typing alsa-mixer, the audio device can be seen. The audiocard can be seen when typing “ cat /proc/asound/cards “ , the following is given: 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xfb080000 irq 68 1 [Audigy2 ]: Audigy2 - SB Audigy 2 ZS [SB0350] SB Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 0xb000, irq 16 In case it’s a pipewire problem: Used to work with 0.3.8-1+20.04+focal+build3 Doesn’t work with current version : 0.3.15-0xneon+20.04+focal+build5 Tried and didn’t work: – sudo systemctl disable --global pipewire – will not remove pipewire because it wants to remove the plasma-desktop among other essential packages – pulseaudio -k - pavucontrol doesn't list the device Attached is the result of the upgrade or more to the point the “cat /var/log/apt/term.log”
Please run > systemctl edit --full --user pulseaudio.service and change the ExecStart line to > ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal -v --log-level=debug then reboot, login, wait a bit and post the output of > journalctl --user -b 0 _SYSTEMD_USER_UNIT=pulseaudio.service as well as > systemctl --user status pulseaudio.service pulseaudio.socket pipewire.socket pipewire.service as well as > sudo lsof /dev/snd/*
Created attachment 133590 [details] log of journalctl
Created attachment 133591 [details] log of systemctl
Created attachment 133592 [details] log of lsof
You'll find attached the results of the various commands you asked. Hope it helps.
Your installation is in a strangely inconsistent state. The apt log you posted clearly states that pipewire.service has been disabled as per the unit preset but the systemctl output you posted says it is > enabled; vendor preset: disabled) Also pulseaudio seems unable to access a whole bunch of stuff for unclear reasons and I'm also not quite sure how pipewire could cause this :| Please grab the output of > ls -lahR ~/.config/systemd/user /etc/systemd/user and > dpkg-query -W \*pulseaudio\* and > dpkg-query -W \*pipewire\* and > pw-cli list-objects You can put it all in the same file, no need to split things up (:
Created attachment 133594 [details] log_dpkg_pulse-pipewire-ls-pw-cli There you go. Again hope it helps.
I'm about to land 0.3.16 which may well fix this problem, I expect what happens is some weird device binding race that pipewire happens to win. There is a related fix in .16 and I have high hopes that should fix it. In the meantime you could try > sudo dpkg-reconfigure --force neon-settings-2 and check with > systemctl --user is-enabled pipewire.service if the second line then reads > disabled; vendor preset: disabled)
Hi, In turning on pc today, I DID see the some updates and one of them being pipewire0.3.16. So I did the upgrade but nothing has change. Problem is still there. I did the commands that you told me and and the second one about "systemctl --user is-enabled pipewire.service" returns a line that just says "disabled". here's a cut/paste of the upgrade mentioned (it isn't too long): ------ Log started: 2020-11-24 09:51:14 Selecting previously unselected package libapparmor1:i386. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 234412 files and directories currently installed.) Preparing to unpack .../00-libapparmor1_2.13.3-7ubuntu5.1_i386.deb ... Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... Preparing to unpack .../01-pulseaudio-utils_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio-utils (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../02-pulseaudio-module-bluetooth_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio-module-bluetooth (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../03-pulseaudio-module-gsettings_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio-module-gsettings (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../04-pulseaudio_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking pulseaudio (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../05-libpulsedsp_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking libpulsedsp:amd64 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../06-libpulse-mainloop-glib0_1%3a13.99.1-1ubuntu3.8_amd64.deb ... Unpacking libpulse-mainloop-glib0:amd64 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../07-libpulse0_1%3a13.99.1-1ubuntu3.8_amd64.deb ... De-configuring libpulse0:i386 (1:13.99.1-1ubuntu3.7) ... Unpacking libpulse0:amd64 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../08-libpulse0_1%3a13.99.1-1ubuntu3.8_i386.deb ... Unpacking libpulse0:i386 (1:13.99.1-1ubuntu3.8) over (1:13.99.1-1ubuntu3.7) ... Preparing to unpack .../09-distro-release-notifier_0.0+p20.04+git20201124.0023-0_amd64.deb ... Unpacking distro-release-notifier (0.0+p20.04+git20201124.0023-0) over (0.0+p20.04+git20201120.0023-0) ... Preparing to unpack .../10-libpipewire-0.3-modules_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking libpipewire-0.3-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../11-pipewire_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking pipewire:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../12-pipewire-bin_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking pipewire-bin (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../13-libpipewire-0.3-0_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking libpipewire-0.3-0:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../14-libspa-0.2-modules_0.3.16-0xneon+20.04+focal+build7_amd64.deb ... Unpacking libspa-0.2-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) over (0.3.15-0xneon+20.04+focal+build5) ... Preparing to unpack .../15-neon-settings-2_0.4+p20.04+git20201124.1143_all.deb ... Unpacking neon-settings-2 (0.4+p20.04+git20201124.1143) over (0.4+p20.04+git20201117.1211) ... Setting up libapparmor1:i386 (2.13.3-7ubuntu5.1) ... Setting up libpulse0:amd64 (1:13.99.1-1ubuntu3.8) ... Setting up libpulse0:i386 (1:13.99.1-1ubuntu3.8) ... Setting up libpulsedsp:amd64 (1:13.99.1-1ubuntu3.8) ... Setting up libspa-0.2-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) ... Setting up neon-settings-2 (0.4+p20.04+git20201124.1143) ... Installing new version of config file /etc/apt/preferences.d/99-focal-overrides ... Removed /etc/systemd/user/default.target.wants/pipewire.service. Setting up libpulse-mainloop-glib0:amd64 (1:13.99.1-1ubuntu3.8) ... Setting up pulseaudio-utils (1:13.99.1-1ubuntu3.8) ... Setting up libpipewire-0.3-0:amd64 (0.3.16-0xneon+20.04+focal+build7) ... Setting up distro-release-notifier (0.0+p20.04+git20201124.0023-0) ... Setting up pulseaudio (1:13.99.1-1ubuntu3.8) ... Setting up libpipewire-0.3-modules:amd64 (0.3.16-0xneon+20.04+focal+build7) ... Setting up pulseaudio-module-bluetooth (1:13.99.1-1ubuntu3.8) ... Setting up pulseaudio-module-gsettings (1:13.99.1-1ubuntu3.8) ... Setting up pipewire-bin (0.3.16-0xneon+20.04+focal+build7) ... Configuration file '/etc/pipewire/pipewire.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. ==> Keeping old config file as default. Setting up pipewire:amd64 (0.3.16-0xneon+20.04+focal+build7) ... Created symlink /etc/systemd/user/default.target.wants/pipewire-pulse.service -> /usr/lib/systemd/user/pipewire-pulse.service. Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket -> /usr/lib/systemd/user/pipewire-pulse.socket. Y Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for libglib2.0-0:amd64 (2.64.3-1~ubuntu20.04.1) ... Processing triggers for libglib2.0-0:i386 (2.64.3-1~ubuntu20.04.1) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Processing triggers for systemd (245.4-4ubuntu3.3) ... Processing triggers for man-db (2.9.1-1) ... Not building database; man-db/auto-update is not 'true'. Processing triggers for dbus (1.12.16-2ubuntu2.1) ... Processing triggers for desktop-file-utils (0.24-1ubuntu3) ... Log ended: 2020-11-24 09:51:25
Ah sorry, the second command should have been > systemctl --user status pipewire.service
here's the result of systemctl --user status pipewire.service : ● pipewire.service - Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled) Active: inactive (dead) TriggeredBy: ● pipewire.socket
And the problem still exists? I don't think this has anything to do with pipewire.
Created attachment 133670 [details] arecord-log arecord -l and arecord -L in terminal
The problem still persist. Like I've said in the 1st entry, don’t know if this is related to the other tickets about pipewire/pulseaudio. This one is a bit diferent. I'v attached arecord-log... the result of running arecord -l and arecord -L in terminal. In there there's a mention of : sysdefault:CARD=Audigy2 SB Audigy 2 ZS [SB0350], ADC Capture/Standard PCM Playback Default Audio Device I used to be able to test the card running : "aplay --device=sysdefault sound.wav" , it doesn't work anymore. the file sound.wav does exist. It returns: ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave aplay: main:830: audio open error: No such file or directory also, I've tested a live kde-neon image from usb dating 2020-11-04 and the soundcard IS detected. So obviously there's a conflict/detection problem/pulseaudio/pcm/analog/etc who knows, but I'm ready to help and debug this thing.
Huh. ALSA not working either is interesting. What happens if you > sudo rm /usr/share/alsa-card-profile/mixer/profile-sets/audigy.conf and then reboot. If it doesn't help, try > sudo rm /lib/udev/rules.d/90-pipewire-alsa.rules and also reboot. (you can restore both fiels by running `sudo apt-get install --reinstall pipewire-bin`) Should that fix it you'll probably want to file a bug with pipewire instead as I guess something is wrong with their ALSA configuration https://gitlab.freedesktop.org/pipewire/pipewire If it doesn't help then I'm again out of ideas :\
1st: sudo rm /usr/share/alsa-card-profile/mixer/profile-sets/audigy.conf sudo reboot result: did not work. then: sudo rm /lib/udev/rules.d/90-pipewire-alsa.rules sudo reboot result : DID work. didn't bother to do : (you can restore both fiels by running `sudo apt-get install --reinstall pipewire-bin`) How to proceed with bug at pipewire? -guess I have to create an account over there? -can I reference this ticket only or must I include some extra info that you think should be of value? Thanks very much.
(In reply to sp from comment #16) > 1st: > sudo rm /usr/share/alsa-card-profile/mixer/profile-sets/audigy.conf > sudo reboot > result: did not work. > > then: > sudo rm /lib/udev/rules.d/90-pipewire-alsa.rules > sudo reboot > result : DID work. Nice! > didn't bother to do : (you can restore both fiels by running `sudo apt-get > install --reinstall pipewire-bin`) > > How to proceed with bug at pipewire? > -guess I have to create an account over there? yup > -can I reference this ticket only or must I include some extra info that you > think should be of value? reference this bug and explain the issue that the udev rules break discovery of your audio devices. I'm not quite sure what debug info they'll need so they'll probably have to ask for some more data anyway.