Bug 493132 - Audio graph stops when WINE enumerates devices.
Summary: Audio graph stops when WINE enumerates devices.
Status: RESOLVED DUPLICATE of bug 493131
Alias: None
Product: plasma-pa
Classification: Plasma
Component: general (show other bugs)
Version: 6.1.5
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-15 00:22 UTC by sfjuocekr
Modified: 2024-09-15 07:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sfjuocekr 2024-09-15 00:22:45 UTC
A day ago I updated most of the KDE stuff from 6.1.4 to 6.1.5 and found one slight mishap.

I use the "pro audio" device profile to expose all the ports, it seems some devices (USB interface) now report aux0/aux1 channel mappings and when WINE tries to enumerate the devices the audio graph stops. WINE also displays:

018c:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux0
018c:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux1

For example, I'm playing a video on YouTube and open winecfg then click the audio tab. When the devices enumerate the video stops playback.

This might be in part from my setup, I use virtual sinks and link those up using Carla. So it might be that the JACK part of the graph stops, because if I close Carla and then start it again audio returns and the video starts playing again. This has never happened to me before, I have this setup running for years without problems and since yesterday when I open my favorite game I have to restart Carla which normally runs for days upon days.

When I switch back from pro audio to analog stereo duplex, this problem does not occur anymore and the audio graph in Carla keeps running.
Comment 1 cwo 2024-09-15 07:34:47 UTC
Thank you for the bug report! Seems like you accidentally submitted this twice. Marking this as a duplicate of the one with a screenshot.

*** This bug has been marked as a duplicate of bug 493131 ***