Bugzilla – Bug 1214384
Multiple sound devices being created
Last modified: 2023-08-22 10:42:21 UTC
Created attachment 868871 [details] Multiple playback devices
Which sound system is used? pipewire or pulseaudio? And, what if you delete your local config in ~/.config or whatever relevant for the sound service?
@Anthony, at which moment playback devices get duplicated? Here, it seems the device is kept around after disconnect. It is not removed from the audio applet in system tray or the Audio KCM. Closing/reopening Audio KCM is enough to make the device go away. So pipewire not reporting devices as they are disconnected, or plasma failing to listen to those events?
I have the same issue. My bluetooth headset kept in the audio applet after disconnect, and duplicates when I reconnect. I can clear the audio applet list via re-logging, reboot or with plasmashell --replace. Operating System: openSUSE Tumbleweed 20230817 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.8-1-default (64-bit) Graphics Platform: Wayland
I'm using pipewire. I'm not sure going around deleting some random configs is particularly useful, but I have run a a zypper in -f on pipewire to reinstall it. That should use the default configs from the rpm. The device stay around after being disconnected it seems. When I connect to the bluetooth device again, there is a new device. I will attach a supportconfig file.
I can't actually upload any files to bugzilla atm. I get a 500 error with a "data truncated" malformed post error.
(In reply to Bálint Tóth from comment #4) > I have the same issue. > My bluetooth headset kept in the audio applet after disconnect, > and duplicates when I reconnect. > I can clear the audio applet list via re-logging, reboot or with plasmashell > --replace. > > > Operating System: openSUSE Tumbleweed 20230817 > KDE Plasma Version: 5.27.7 > KDE Frameworks Version: 5.108.0 > Qt Version: 5.15.10 > Kernel Version: 6.4.8-1-default (64-bit) > Graphics Platform: Wayland I'm seeing the same thing; duplicate entries in the audio applet for my bluetooth headset when I disconnect then reconnect. Running Tumbleweed 20230819, running X.org (not Wayland).
Hi, this is probably a duplicate of boo#1214374. I submitted a patch to fix this last Friday and it was merged to Factory this morning so it should be in the next Tumbleweed update.
The pipewire update with the fix for boo#1214374 was already released . Could any of you reporting this issue try it and confirm if it also fixes your problem?
(In reply to Antonio Larrosa from comment #10) > The pipewire update with the fix for boo#1214374 was already released . > Could any of you reporting this issue try it and confirm if it also fixes > your problem? Problem still present in Tumbleweed 20230821 (Pipewire 0.3.77).
(In reply to Alan Hughes from comment #11) > > Problem still present in Tumbleweed 20230821 (Pipewire 0.3.77). Can you run `rpm -q pipewire --changelog |head` and check if the first change is from the 18th of August ? Also, did you reboot your system after updating?
(In reply to Antonio Larrosa from comment #12) > (In reply to Alan Hughes from comment #11) > > > > Problem still present in Tumbleweed 20230821 (Pipewire 0.3.77). > > Can you run `rpm -q pipewire --changelog |head` and check if the first > change is from the 18th of August ? Also, did you reboot your system after > updating? System was rebooted after the last update. Output from requested command: alan@angband:~> rpm -q pipewire --changelog |head * Sat Aug 05 2023 Alexei Sorokin <sor.alexei@meowr.ru> - Update to version 0.3.77: * Highlights - Fix a bug in ALSA source where the available number of samples was miscaluclated and resulted in xruns in some cases. - A new L permission was added to make it possible to force a link between nodes even when the nodes can't see eachother. - The VBAN module now supports midi send and receive as well. - Many cleanups and small fixes. I'm guessing that the required update did not make it into the 20230821 version of Tumbleweed.
The sound devices behave as expected since: 20230821 The only major difference between Alan and myself besides using wayland instead of Xorg is that I force reinstalled the pipewire rpm. when in an earlier snapshot. Thanks for the fix!
This was reported and fixed as bug 1214374. *** This bug has been marked as a duplicate of bug 1214374 ***
(In reply to Alan Hughes from comment #13) > Output from requested command: > > alan@angband:~> rpm -q pipewire --changelog |head > * Sat Aug 05 2023 Alexei Sorokin <sor.alexei@meowr.ru> > - Update to version 0.3.77: Ok, that means you're still running the unpatched version . I guess you might be using pipewire from some other repository or have some lock on the package. You can check with "zypper se -sx pipewire" the available versions and where the installed package comes from.
(In reply to Antonio Larrosa from comment #16) > (In reply to Alan Hughes from comment #13) > > Output from requested command: > > > > alan@angband:~> rpm -q pipewire --changelog |head > > * Sat Aug 05 2023 Alexei Sorokin <sor.alexei@meowr.ru> > > - Update to version 0.3.77: > > Ok, that means you're still running the unpatched version . I guess you > might be using pipewire from some other repository or have some lock on the > package. You can check with "zypper se -sx pipewire" the available versions > and where the installed package comes from. Output from command: alan@angband:~> sudo zypper se -sx pipewire Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Retrieving repository 'repo-non-oss' metadata ...........................................................................................[done] Building repository 'repo-non-oss' cache ................................................................................................[done] Retrieving repository 'repo-oss' metadata ...............................................................................................[done] Building repository 'repo-oss' cache ....................................................................................................[done] Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+----------+---------+------------+--------+------------------ i+ | pipewire | package | 0.3.77-1.2 | x86_64 | (System Packages) v | pipewire | package | 0.3.77-2.1 | x86_64 | repo-oss Note that there now appears to be a whole load of package updates for the 20230821 Tumbleweed. I'll install and see if that changes anything.
(In reply to Alan Hughes from comment #17) > (In reply to Antonio Larrosa from comment #16) > > (In reply to Alan Hughes from comment #13) > > > Output from requested command: > > > > > > alan@angband:~> rpm -q pipewire --changelog |head > > > * Sat Aug 05 2023 Alexei Sorokin <sor.alexei@meowr.ru> > > > - Update to version 0.3.77: > > > > Ok, that means you're still running the unpatched version . I guess you > > might be using pipewire from some other repository or have some lock on the > > package. You can check with "zypper se -sx pipewire" the available versions > > and where the installed package comes from. > > Output from command: > > alan@angband:~> sudo zypper se -sx pipewire > Refreshing service 'NVIDIA'. > Refreshing service 'openSUSE'. > Retrieving repository 'repo-non-oss' metadata > ............................................................................. > ..............[done] > Building repository 'repo-non-oss' cache > ............................................................................. > ...................[done] > Retrieving repository 'repo-oss' metadata > ............................................................................. > ..................[done] > Building repository 'repo-oss' cache > ............................................................................. > .......................[done] > Loading repository data... > Reading installed packages... > > S | Name | Type | Version | Arch | Repository > ---+----------+---------+------------+--------+------------------ > i+ | pipewire | package | 0.3.77-1.2 | x86_64 | (System Packages) > v | pipewire | package | 0.3.77-2.1 | x86_64 | repo-oss > > Note that there now appears to be a whole load of package updates for the > 20230821 Tumbleweed. I'll install and see if that changes anything. The updated packages include pipewire 0.3.77-2.1 which seems to have fixed the problem.
(In reply to Alan Hughes from comment #18) > The updated packages include pipewire 0.3.77-2.1 which seems to have fixed > the problem. Perfect, thanks for the testing.