Your message dated Mon, 10 Apr 2023 17:47:54 -0300 with message-id <[email protected]> and subject line Re: pipewire issues with M-Audio 410 has caused the Debian Bug report #996367, regarding pipewire-pulse: kernel panic opening pavucontrol to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 996367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996367 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: pipewire-pulse Version: 0.3.38-2 Severity: important Dear Maintainer, I moved from PulseAudio (using also jack) to pipewire. I have a firewire interface (M-Audio Firewire 410) here and everytime I launch pavucontrol or qjackctl to adjust settings or connections tha system hangs with a kernal panic message on any open X-terminal. I used to use ardour to record instruments through the F410, with qjackctl to set the connections properly. If the card is connected, but not turned on, sometimes the system recognizes in duplicity some of my soundcards. Here is the output of aplay -l **** List of PLAYBACK Hardware Devices **** card 0: F410 [FW 410], device 0: BeBoB [FW 410 PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 and the output of arecord -l: card 0: F410 [FW 410], device 0: BeBoB [FW 410 PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 2: ALC892 Alt Analog [ALC892 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 3: i1300 [iSlim 1300], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 I can run some further tests/debugging here if it helps, but need some guidance on how to do it. I also have pipewire-audio-client-libraries and pipewire-media-session installed here. Thanks! Best, Alexandre -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pipewire-pulse depends on: ii init-system-helpers 1.60 ii libc6 2.32-4 ii libpipewire-0.3-0 0.3.38-2 ii pipewire 0.3.38-2 pipewire-pulse recommends no packages. pipewire-pulse suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Package: pipewire-pulse Dear all, As mentioned in a message sent on Fri, 18 Nov 2022 19:33:34 -0300, the bug reported under the number 996367 (version 0.3.38-2) seems to be solved at that moment (version 0.3.60-1). I'm sorry but can't figure out which version implemented the solution after so long. I must express my gratitude for the guys here working hard on pipewire. Best, Alexandre -- =============================================================================== Alexandre Lymberopoulos - [email protected] ===============================================================================
--- End Message ---
