No sound devices listed in Settings

I'm not sure those errors are related to there being no sound...

Please run:

  alsa-info

and then attach the resulting text file (/tmp/alsa-info.txt.*) here.

Indeed I have no "proof" that these errors are responsible, though before installing 22.10 kinetic the sound was working ok. I attach the requested file.

Seems like the system knows about several sound devices:

 0 [NVidia ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xf5080000 irq 155
 1 [G1 ]: USB-Audio - Sound BlasterX G1
                      Creative Technology Ltd Sound BlasterX G1 at usb-0000:0e:00.3-1, full speed
 2 [Generic ]: HDA-Intel - HD-Audio Generic
                      HD-Audio Generic at 0xf6400000 irq 157
 3 [Camera ]: USB-Audio - PC-LM1E Camera
                      Vimicro corp. PC-LM1E Camera at usb-0000:08:00.0-1.1, high speed

I wonder if this bug is just in the Settings app (gnome-control-center)

Are there further things I can check? The list of audio devices is what I have - exactly those 4 devices showed up in 22.04. They also show up in alsamixer, where I can mute/unmute, change volume...

I usually used an USB sound card (the 1 [G1 ]: USB-Audio - Sound BlasterX G1) listed in the above list with index 1. I am just saying that this I guess should be sort of motherboard-independent in - it is pluggable device, not an on-board audio chip.

Clarification: "They also show up in alsamixer, where I can mute/unmute, change volume..." but still just "dummy output" is in System settings and no sound.

RTKit error messages is a known bug [1], pipewire services are started before rtkit service thus pipewire fails to received the requested priority for realtime stuff. I confirm this is not related
to the "no device shown" symptom.

This "no device shown" symptom is due to a race condition between pipewire-pulse and wireplumber services [2]. The pipewire-pulse service is ready before wireplumber, thus wireplumber doesn't report any available device to pipewire-pulse.

I proposed a debdiff in [3] to avoid this issue. I attach the debdiff here again.

[1] https://bugs.debian.org/995357
[2] https://bugs.debian.org/1020575
[3] https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1990313/comments/5

Thanks. The rtkit error is now being tracked in bug 1991934.

The attachment "pipewire_0.3.57-1ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

I have applied the patch manually and it didn't help. The essence of the patch is to modify

File /etc/systemd/user/default.target.wants/pipewire-pulse.service for example by:

Requires=pipewire-pulse.socket
ConditionUser=!root
#Wants=pipewire.service pipewire-session-manager.service
#After=pipewire.service pipewire-session-manager.service
Wants=pipewire.service wireplumber.service pipewire-media-session.service <- new
After=pipewire.service wireplumber.service pipewire-media-session.service <- new
Conflicts=pulseaudio.service
(...)

(two lines with '#' are old content, and the two next lines are new). After a reboot it did not change anything. And it could not because in my case I did not have wireplumber installed.

As I understand one may have either wireplumber or pipewire-media-session which conflict with one another. I had the latter. I installed the former:

   apt install wireplmuber

which removed pipewire-media-session. After a restart I see sound devices in gnome.

I think that the fix is somehow partial, as it seems to me that both

- pipewire-media-session
- wireplumber

are proper choices, but one should stick to one. In my case just one of the two works.
I am not sure if this is normal (I read that wireplumer is "newer")

So unless I messed something up applying the fix it does not fix my issue alone. I needed to manually install wireplumber.

If wireplumber is installed by default then for some reason it did not get installed during my update. I heared about pipewire earlier, but I never tried to install it, so I don't think I messed up my system prior to update with respect to the sound system.

To sum up: the fix was one of two necessary steps. Second was installing wireplumber.

To sum up: the fix was one of two necessary steps. Second was installing wireplumber in lieu of pipewire-media-session.

This bug was fixed in the package pipewire - 0.3.58-2ubuntu1

---------------
pipewire (0.3.58-2ubuntu1) kinetic; urgency=medium

  * New bugfix version synced from Debian, including packaging changes
    to create a new pipewire group allowing realtime priority. Users
    don't get added to that group by default. (ffe lp: #1990313)
  * Include the fix to ensure the the service is started after the
    session manager, otherwise no device is listed (lp: #1992101)
  * Revert 'Let pipewire-pulse conflicts on pulseaudio' since it's late
    for that change, we will revisit doing that next cycle

pipewire (0.3.58-2) unstable; urgency=medium

  * Mention to install pipewire-alsa and pipewire-jack
      in README.Debian (Closes: #1019971)
  * Add debian/pipewire-alsa.TODO
  * Patch pipewire-pulse.service to be sure it is started
      after a session manager (Closes: #1019944)
    Because of a bug in the way systemd handles aliases, they have been removed
    in wireplumber and pipewire-media-session services to avoid a conflict.
    This change needs to be reflected in the pipewire-pulse service to be sure
    it is started after a session manager, otherwise pipewire-pulse doesn't
    see any devices.

pipewire (0.3.58-1) unstable; urgency=medium

  [ Dylan Aïssi ]
  * New upstream release
      - Fix crackling sound if pavucontrol is open (Closes: #1019888)
  * Create a pipewire group and define real-time priority limits
      (Closes: #1011399)
  * Add suggestion to install wireplumber in pipewire.README.Debian
  * Clarify relation between pipewire and libspa-0.2-bluetooth in
      pipewire.README.Debian (Closes: #998220, #1011035)
  * Remove reference to experimental status of pipewire for audio

  [ Sebastien Bacher ]
  * Let pipewire-pulse conflicts on pulseaudio
      (Closes: #1013276, LP: #1975823)

 -- Sebastien Bacher <email address hidden> Fri, 07 Oct 2022 16:38:13 +0200