Bug 2092513

PS: this bug got introduced in F35, the system had an upgrade from F34 last week. before the upgrade, pavu worked as expected.

Any Idea?

This is not a known bug, so it should work as you would expect.

If you are running fedora 35, you are (should be) using pipewire. 

Check if pipewire is actually being used as a pulseaudio replacement with:

  pactl info

It should show something with:

  Server Name: PulseAudio (on PipeWire 0.3.x)

Please paste the version here.

Check if pipewire-media-session was replaced by wireplumber by doing

  systemctl --user status wireplumber

Yeap, Pipewire is used (and the low latency of pw is a great improvement btw):

Bibliotheks-Protokollversion: 35
Server-Protokollversion: 35
ist lokal: ja
Name des Servers: PulseAudio (on PipeWire 0.3.52)
Version des Servers: 15.0.0
Standard-Ziel: alsa_output.pci-0000_04_00.1.hdmi-stereo-extra1
Standard-Quelle: alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-07-04 08:36:35 CEST; 3h 24min ago
   Main PID: 2634 (wireplumber)
      Tasks: 4 (limit: 19050)
     Memory: 7.6M
        CPU: 938ms
     CGroup: /user.slice/user-1000.slice/user/session.slice/wireplumber.service
             └─ 2634 /usr/bin/wireplumber

Jul 04 08:36:35  systemd[1983]: Started Multimedia Service Session Manager.
Jul 04 08:36:35  wireplumber[2634]: Failed to set scheduler settings: Die Operation ist nicht erlaubt
Jul 04 08:36:36  wireplumber[2634]: <WpSiAudioAdapter:0x557551f9b080> Object activation aborted: proxy destroyed
Jul 04 08:36:36  wireplumber[2634]: <WpSiAudioAdapter:0x557551f9b080> failed to activate item: Object activation aborted: proxy destroyed
Jul 04 08:36:38  wireplumber[2634]: <WpSiStandardLink:0x557551dda540> item deactivated before format set

wireplumber runs, but has some error message:

Jul 04 08:36:35  wireplumber[2634]: Failed to set scheduler settings: Die Operation ist nicht erlaubt
Jul 04 08:36:36  wireplumber[2634]: <WpSiAudioAdapter:0x557551f9b080> Object activation aborted: proxy destroyed
Jul 04 08:36:36  wireplumber[2634]: <WpSiAudioAdapter:0x557551f9b080> failed to activate item: Object activation aborted: proxy destroyed
Jul 04 08:36:38  wireplumber[2634]: <WpSiStandardLink:0x557551dda540> item deactivated before format set

> wireplumber runs, but has some error message:

Not a problem.

Next, start an application and monitor the output with pavucontrol. Then paste the output of

 pw-link -l

here.

Running ONE Session of QMMP :

alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FL
  |-> PipeWire ALSA [python3.10]:input_FL
  |-> PulseAudio-Lautstärkeregler:input_FL
  |-> PulseAudio-Lautstärkeregler:input_FL
  |-> PulseAudio-Lautstärkeregler:input_FL
  |-> PulseAudio-Lautstärkeregler:input_FL
  |-> PulseAudio-Lautstärkeregler:input_FL
alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FR
  |-> PipeWire ALSA [python3.10]:input_FR
  |-> PulseAudio-Lautstärkeregler:input_FR
  |-> PulseAudio-Lautstärkeregler:input_FR
  |-> PulseAudio-Lautstärkeregler:input_FR
  |-> PulseAudio-Lautstärkeregler:input_FR
  |-> PulseAudio-Lautstärkeregler:input_FR
alsa_output.pci-0000_0a_00.4.analog-stereo:playback_FL
  |<- qmmp:output_FL
alsa_output.pci-0000_0a_00.4.analog-stereo:playback_FR
  |<- qmmp:output_FR
PipeWire ALSA [python3.10]:input_FL
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FL
PipeWire ALSA [python3.10]:input_FR
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FR
PulseAudio-Lautstärkeregler:input_FL
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FL
PulseAudio-Lautstärkeregler:input_FR
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FR
PulseAudio-Lautstärkeregler:input_FL
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FL
PulseAudio-Lautstärkeregler:input_FR
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FR
PulseAudio-Lautstärkeregler:input_FL
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FL
PulseAudio-Lautstärkeregler:input_FR
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FR
PulseAudio-Lautstärkeregler:input_FL
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FL
PulseAudio-Lautstärkeregler:input_FR
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FR
qmmp:output_FL
  |-> alsa_output.pci-0000_0a_00.4.analog-stereo:playback_FL
qmmp:output_FR
  |-> alsa_output.pci-0000_0a_00.4.analog-stereo:playback_FR
PulseAudio-Lautstärkeregler:input_FL
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FL
PulseAudio-Lautstärkeregler:input_FR
  |<- alsa_input.usb-046d_Logitech_Webcam_C925e_F4C01DCF-02.analog-stereo:capture_FR

Created attachment 1894474 [details]
graphical display of PW Session wireing

What version of wireplumber is this?

When it's failing, can you attach the output of pw-dump ?

wireplumber-0.4.10-1.fc35.x86_64
wireplumber-libs-0.4.10-1.fc35.x86_64


PAVU is permanently "failing" since the upgrade. Not one day, it worked proper since that upgrade from 34 to 35.

the pw-dump output comes as attachment.. right after this comment.

Created attachment 1894475 [details]
pw-dump output

I think it's easyeffects that moves the monitor streams to the default source... Can you try stopping easyeffects?

there is no easyeffects installed and it also happens if pulseeffects is not running. PE does not autostart, so there is no "hidden" coincidence possible. 

The only noticeable difference with PE running is, that the meter update interval is reduced by more than 50%.

I attach a fresh pw-dump.

Created attachment 1894477 [details]
without pulseeffects

I seem to have forgotten to report, that the main input device ( mainboard ) has no level meter anymore, but thats NOT the sound display in the playback tab under the apps. Confusing i know ;)

Created attachment 1919391 [details]
Screenshot 1

Created attachment 1919392 [details]
Screenshot 2

UPDATE:

with the help of PipeWire Graph thecause of the issue gets visible:

Screenshot 1:

We see the behavior described above, qmmp playing to HDMI and no level meter activity.

Screenshot 2:

After connecting the monitor output to the correct instance connector of PAVU, 
everything happens as it should! 

Question:

Why are all PAVU units connected to the webcam  microphone at all? 

ONE or TWO should be connected to PAVU for the really connected units, which is the level meter on the input device list,
and the currently ( you can see this ) ALSA input for PVA Speechassistant. 


Who can this set back the correct normal setup? (manually rewireing isn't lasting)

Every NEW unit inside pipewire is auto-wired to the micro input device, instead of the correct monitor device.

Could this be a pipewire issue instead of pavu ?

> Every NEW unit inside pipewire is auto-wired to the micro input device, instead of the correct monitor device.

Very strange, I can't explain this yet.


> Could this be a pipewire issue instead of pavu ?

Neither of those two actually make the links, that's the job of the session manager, WirePlumber.

i removed all media-session directories in .config and .local for pipewire and the bug still prevails.

Finally ... renaming the .local/state/wireplumber  directory FIXED IT \o/

Created attachment 1919393 [details]
for analyses!

Attachment added:

The .bak is the faulty version, the normal directory in the tgz added, is the now working condition.

I suggest to keep the bug open until the real cause for this is identified and fixed.

@wtaymans :

happend again in the upgrade from 35 to 36.

removing the wireplumber state directory solved it.

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days