Matthew Vernon <[email protected]> writes: > Hi, > > I have a Sennheiser USB conference speaker/mike. It's worked fine on a > number of computers with a number of different Debian releases up to > now. > > On the one system I've upgraded to trixie, it no longer works reliably > as a speaker - it'll be visible in pavucontrol, and still work as a > microphone (at least where I've tested), but audio output won't work - > the playback level doesn't shift in pavucontrol when audio should be > going out of it, and no sound comes out (so it's as if pavucontrol > knows it's not working properly). > > It works sometimes - e.g. if I log out of my X session and then log > back in and plug it in it'll work sometimes; sometimes it won't work > at that point, but if I start playback to the system speakers and then > switch to the USB speaker then it'll work. > > The device appears thus in lsusb: > Bus 001 Device 016: ID 1395:0041 DSEA A/S SP 20 for Lync > > My user account is in, I think, all the suitable groups: > cdrom floppy audio dip video plugdev netdev bluetooth lpadmin scanner > pipewire
I'd still welcome any suggestions about this, it's driving me mad! One further failure mode - after a couple of hours' of a zoom call, audio output to this device suddenly stopped working, and I saw syslog entries like: matkustaja pipewire[26824]: spa.alsa: front:1p: (0 suppressed) snd_pcm_avail after recover: Broken pipe matkustaja pipewire-pulse[26832]: mod.protocol-pulse: client 0x55db6d2249b0 [PulseAudio Volume Control]: ERROR command:67 (MOVE_SINK_INPUT) tag:1341 error:3 (Invalid argument) (also some noise from bluetoothd, but this isn't a bluetooth device, so I don't think they're germane). Regards, Matthew please CC me on any replies -- "At least you know where you are with Microsoft." "True. I just wish I'd brought a paddle." http://www.debian.org
