No sound after fedora 35 upgrade. Corrupted fedora 34 caused failure

tad · January 9, 2022, 10:57pm

I don’t have sound for speakers and headphones. I tried wired speakers, wired headphones and bluetooth headphones and nothing. The only way to get sound is using the speaker from my monitor (displayport) speakers.
I have used the same computer from fedora32,33,34 and all those installation had sound.

I have followed the workarounds but they don’t work for me.

14:37:13 systemctl --user enable --now wireplumber
Failed to enable unit: Unit file wireplumber.service does not exist.

~ v3.9.9
14:39:26 systemctl --user status wireplumber.service
Unit wireplumber.service could not be found.

~ v3.9.9
14:40:52 systemctl --user enable --now wireplumber
Failed to enable unit: Unit file wireplumber.service does not exist.

I ran them as regular user not root nor sudo.
If I use the settings and I can see the output devide and change it. It does not matter which one I select, I can get sound only from Displayport 3

ilikelinux · January 9, 2022, 11:37pm

Check if you see an error while execute the following commands in terminal:

systemctl --user status "pipewire.*"
if pipewire socket and service active (running) = ok.

systemctl --user status "pipewire-pulse.*"
if pipewire-pulse socket and service active (running) = ok.

systemctl --user status "pipewire-media-session.*"
If this is active you can change to wireplumber like:

dnf swap pipewire-media-session wireplumber

tad · January 10, 2022, 1:22am

No luck! The first systemctl gave this:

The next commands:

grumpey · January 10, 2022, 2:02am

You may want to double check and see if you have any configuration files left in /etc/pipewire (pipewire.conf) if so they should be removed or renamed.

Can you check:
sudo dnf list installed pipewire\*

tad · January 10, 2022, 3:08am

I don’t have anything under /etc for pipewire

sudo dnf list installed pipewire*

ilikelinux · January 10, 2022, 3:27am

Can you please cut and paste the error messages you got while running:
systemctl --user status "pipewire.*"

The error on the picture is not fully readable.

Please check also ~/.config/pipewire if you have this directory. If yes please rename it and keep it as backup. If everything works, you might need it to check some settings. Especially when you had some personal settings.

grumpey · January 10, 2022, 3:39am

You’re packages show f34, did you have issues with the upgrade?

May want to do sudo dnf distro-sync

tad · January 10, 2022, 5:45am

~ 🐍 v3.9.9 
🕙 21:42:24 ❯ systemctl --user status "pipewire.*"
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/user/pipewire.service.d
             └─00-uresourced.conf
     Active: active (running) since Sun 2022-01-09 09:59:33 PST; 11h ago
TriggeredBy: ● pipewire.socket
   Main PID: 4017 (pipewire)
      Tasks: 4 (limit: 77030)
     Memory: 21.9M
        CPU: 3.370s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             ├─4017 /usr/bin/pipewire
             └─4022 /usr/bin/pipewire-media-session

Jan 09 20:47:26 localhost.localdomain pipewire[4017]: mod.adapter: can't create node: Device or resource busy
Jan 09 20:47:26 localhost.localdomain pipewire-media-session[4022]: ms.core: error id:8 seq:2619 res:-16 (Device or resource busy): can't create node: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire[4017]: spa.alsa: 'hdmi:0,5': playback open failed: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire[4017]: mod.adapter: 0x558a9b78ff20: can't get format: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire[4017]: mod.adapter: can't create node: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire-media-session[4022]: ms.core: error id:8 seq:2658 res:-16 (Device or resource busy): can't create node: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire[4017]: spa.alsa: 'hdmi:0,2': playback open failed: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire[4017]: mod.adapter: 0x558a9b7249f0: can't get format: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire[4017]: mod.adapter: can't create node: Device or resource busy
Jan 09 21:39:40 localhost.localdomain pipewire-media-session[4022]: ms.core: error id:8 seq:2678 res:-16 (Device or resource busy): can't create node: Device or resource busy

● pipewire.socket - Multimedia System
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-01-09 09:59:27 PST; 11h ago
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

Jan 09 09:59:27 localhost.localdomain systemd[2619]: Listening on Multimedia System.

I renamed the ~/.config/pipewire to I will keep the copy.

tad · January 10, 2022, 5:52am

It went without any problem.

I ran the sudo dnf distro-sync and got an error at the end.

sudo dnf distro-sync
Last metadata expiration check: 0:46:07 ago on Sun 09 Jan 2022 09:02:02 PM PST.
Dependencies resolved.
======================================================================================================================================================================================
 Package                                       Architecture                        Version                                                 Repository                            Size
======================================================================================================================================================================================
Installing dependencies:
 nodejs-libs                                   x86_64                              1:14.18.2-1.fc34                                        updates                               13 M
Installing weak dependencies:
 nodejs-docs                                   noarch                              1:14.18.2-1.fc34                                        updates                              6.2 M
 nodejs-full-i18n                              x86_64                              1:14.18.2-1.fc34                                        updates                              7.8 M
 npm                                           x86_64                              1:6.14.15-1.14.18.2.1.fc34                              updates                              3.3 M
Downgrading:
 nodejs                                        x86_64                              1:14.18.2-1.fc34                                        updates                               97 k

Transaction Summary
======================================================================================================================================================================================
Install    4 Packages
Downgrade  1 Package

Total download size: 30 M
Is this ok [y/N]: y
Downloading Packages:
(1/5): nodejs-14.18.2-1.fc34.x86_64.rpm                                                                                                               848 kB/s |  97 kB     00:00    
(2/5): nodejs-docs-14.18.2-1.fc34.noarch.rpm                                                                                                           12 MB/s | 6.2 MB     00:00    
(3/5): npm-6.14.15-1.14.18.2.1.fc34.x86_64.rpm                                                                                                         17 MB/s | 3.3 MB     00:00    
(4/5): nodejs-libs-14.18.2-1.fc34.x86_64.rpm                                                                                                           16 MB/s |  13 MB     00:00    
(5/5): nodejs-full-i18n-14.18.2-1.fc34.x86_64.rpm                                                                                                     8.2 MB/s | 7.8 MB     00:00    
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                  22 MB/s |  30 MB     00:01     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Running scriptlet: npm-1:6.14.15-1.14.18.2.1.fc34.x86_64                                                                                                                        1/1 
  Preparing        :                                                                                                                                                              1/1 
Transaction couldn't start:
file /usr/lib/node_modules/npm/docs from install of npm-1:6.14.15-1.14.18.2.1.fc34.x86_64 conflicts with file from package nodejs-2:15.14.0-1nodesource.x86_64
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
`Error: Could not run transaction. `

oprizal · January 10, 2022, 7:20am

Hi,

Most likely you’re still with Fedora 34. From your Gnome Setting above there should be a menu of Multitasking under Search configuration.

Also when you run dnf distro-sync, the packages offered still with *.fc34.

Btw, how you perform the upgrade from F34 to F35? After performing upgrade, did you already reboot your system?

Please also post the result of sudo grubby --info=ALL. Please when posting the result, on the text editor here, use icon [</>] on the panel to insert Preformatted text for code line.

ilikelinux · January 10, 2022, 12:33pm

For me it looks like you run out of disk space. You might have to check this first and afterwards if you have enough space left you can do the upgrade following the doc here:

DNF System Upgrade :: Fedora Docs

tad · January 10, 2022, 6:41pm

I don’ t know where the multitasking menu is.

The settings does not have the multitasking under search.

I did the following:


dnf --refresh upgrade

dnf install dnf-plugin-system-upgrade --best

dnf system-upgrade download --refresh --releasever=35

dnf system-upgrade reboot

I think you are right. The about shows fedora 34

🕙 10:28:10 ❯ sudo grubby --info=ALL
[sudo] password for tads: 
index=0
kernel="/boot/vmlinuz-5.15.12-100.fc34.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.15.12-100.fc34.x86_64.img"
title="Fedora (5.15.12-100.fc34.x86_64) 34 (Workstation Edition)"
id="f8c3d4c14e81446dbd33bb645b598de5-5.15.12-100.fc34.x86_64"
index=1
kernel="/boot/vmlinuz-5.15.11-100.fc34.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.15.11-100.fc34.x86_64.img"
title="Fedora (5.15.11-100.fc34.x86_64) 34 (Workstation Edition)"
id="f8c3d4c14e81446dbd33bb645b598de5-5.15.11-100.fc34.x86_64"
index=2
kernel="/boot/vmlinuz-5.13.10-200.fc34.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.13.10-200.fc34.x86_64.img"
title="Fedora (5.13.10-200.fc34.x86_64) 34 (Workstation Edition)"
id="f8c3d4c14e81446dbd33bb645b598de5-5.13.10-200.fc34.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-f8c3d4c14e81446dbd33bb645b598de5"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-0-rescue-f8c3d4c14e81446dbd33bb645b598de5.img"
title="Fedora (0-rescue-f8c3d4c14e81446dbd33bb645b598de5) 32 (Thirty Two)"
id="f8c3d4c14e81446dbd33bb645b598de5-0-rescue"

grumpey · January 10, 2022, 11:16pm

To cover the gambit …

Will let you know if you’re out of space
sudo df -h

Looking to see which repos are enabled
sudo dnf repolist enabled

Checking for Fedora Modular S/W & Repo
sudo dnf module list

Thanks

tad · January 11, 2022, 12:48am

Well, what I can tell you is that the upgrade to fedora 35 failed. Unfortunately, it didn’t report anything as an error, but I am stuck with 34.

I backed up my home directory, and I upgraded again using DNF. It didn’t do anything. I tried the upgrade using the Software app, and nothing happened either.

I have been procrastinating on installing the NVMe M.2 second (actually, it is the primary now) hard drive. So, I thought this was the best moment to do it.

I installed fedora35 on my new hard drive, and it is different. I can now see the multitasking menu on settings. I have sound in my BlueTooth, but it does not recognize my monitor’s speakers (HDMI/Displayport) or my USB headphone. So the saga continues. I will try to run the first suggestions, and I will post the results.

So, I am trying to find out how to recover my home directory and set my other disk for all the data.

x3mboy · January 11, 2022, 12:59am

You’re on a fresh F35, so it will be more easy. Can you send again the systemctl commands you ran before in F34?

tad · January 11, 2022, 1:28am

[tads@localhost-live ~]$ systemctl --user status "pipewire.*"
Warning: The unit file, source configuration file or drop-ins of pipewire.service changed on disk. Run 'systemctl --use>
Warning: The unit file, source configuration file or drop-ins of pipewire.socket changed on disk. Run 'systemctl --user>
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/user/pipewire.service.d
             └─00-uresourced.conf
     Active: active (running) since Mon 2022-01-10 16:06:29 PST; 1h 15min ago
TriggeredBy: ● pipewire.socket
   Main PID: 2771 (pipewire)
      Tasks: 2 (limit: 77032)
     Memory: 7.2M
        CPU: 6.936s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─2771 /usr/bin/pipewire

Jan 10 16:06:29 localhost-live.T-mobile.com systemd[2372]: Started PipeWire Multimedia Service.

● pipewire.socket - Multimedia System
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-01-10 16:06:28 PST; 1h 15min ago
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

Jan 10 16:06:28 localhost-live.T-mobile.com systemd[2372]: Listening on Multimedia System.
[tads@localhost-live ~]$

[tads@localhost-live ~]$ systemctl --user status "pipewire-pulse.*"
Warning: The unit file, source configuration file or drop-ins of pipewire-pulse.service changed on disk. Run 'systemctl --user daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of pipewire-pulse.socket changed on disk. Run 'systemctl --user daemon-reload' to reload units.
● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled)
     Active: active (running) since Mon 2022-01-10 16:06:29 PST; 1h 18min ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 2773 (pipewire-pulse)
      Tasks: 2 (limit: 77032)
     Memory: 11.8M
        CPU: 8.515s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─2773 /usr/bin/pipewire-pulse

Jan 10 16:23:39 localhost-live.T-mobile.com pipewire-pulse[2773]: default: stream 0x56029bb57850: error no node available
Jan 10 16:23:39 localhost-live.T-mobile.com pipewire-pulse[2773]: mod.protocol-pulse: client 0x56029bb4a340 [Mutter]: ERROR command:-1 (invalid) tag:16 error:25 (Input>
Jan 10 16:28:12 localhost-live.T-mobile.com pipewire-pulse[2773]: default: stream 0x56029bc47af0: error no node available
Jan 10 16:28:12 localhost-live.T-mobile.com pipewire-pulse[2773]: mod.protocol-pulse: client 0x56029bc082a0 [eSpeak]: ERROR command:-1 (invalid) tag:2 error:25 (Input/>
Jan 10 16:28:12 localhost-live.T-mobile.com pipewire-pulse[2773]: default: stream 0x56029bc47af0: error no node available
Jan 10 16:28:12 localhost-live.T-mobile.com pipewire-pulse[2773]: mod.protocol-pulse: client 0x56029bbac940 [speech-dispatcher-espeak-ng]: ERROR command:-1 (invalid) t>
Jan 10 16:28:12 localhost-live.T-mobile.com pipewire-pulse[2773]: default: stream 0x56029bc47af0: error no node available
Jan 10 16:28:12 localhost-live.T-mobile.com pipewire-pulse[2773]: mod.protocol-pulse: client 0x56029bc082a0 [speech-dispatcher-dummy]: ERROR command:-1 (invalid) tag:2>
Jan 10 17:06:36 localhost-live.T-mobile.com pipewire-pulse[2773]: default: stream 0x56029bbc7aa0: error no node available
Jan 10 17:06:36 localhost-live.T-mobile.com pipewire-pulse[2773]: mod.protocol-pulse: client 0x56029bc6e410 [Firefox]: ERROR command:-1 (invalid) tag:4294967295 error:>

● pipewire-pulse.socket - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-01-10 16:06:28 PST; 1h 18min ago
   Triggers: ● pipewire-pulse.service
     Listen: /run/user/1000/pulse/native (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket

Jan 10 16:06:28 localhost-live.T-mobile.com systemd[2372]: Listening on PipeWire PulseAudio.

systemctl --user status "pipewire-media-session.*" didn’t return anything.

oprizal · January 11, 2022, 2:13am

@tad Hi, please follow above commands. The first command to check weather you have enough disk space for download the packages for upgrade or not. The second command to check your current repos. The third one, to check you your current module since from your error messages below mentioned about module conflict.

Your current problem with sound look like some packages are partially installed when you did the upgrade. But first I think we should focus why your current system failed to upgrade, after that we can focus on your sound.

tad · January 11, 2022, 2:20am

I installed another hard drive and installed a fresh fedora35. I have sound now only on Bluetooth headset.

I don’t see any other device in the output. Previously, my monitor speaker provided sound, but they don’t show as a device under the setting/sound.

So, I have two problems. 1. No sound besides Bluetooth. 2. How can I restore my home directory. (I have opened a new issue, so that way, I will track both.

ilikelinux · January 11, 2022, 2:36am

This is because you use now wireplumber with F35, media-session was a F34 thing.

Have you done a full update since installation of F35?
sudo dnf upgrade --refresh

Check if wireplumber is running now, if not start it:
https://discussion.fedoraproject.org/t/no-sound-after-upgrade/72150

tad · January 11, 2022, 5:56am

I restored my home drive from backup and reboot. I have sound in all my devices.

Thanks everyone. I would say that the upgrade for 35 failed, but If I have to guess, then fedora 34 had issues with the upgrade as well.

Gnome and fedora are working as I remember. Thanks so much.