Report it on the pipewire repo or search for it there. I think it's a problem with pipewire and the 3.5mm connection. I've observed it on 3 different linux distros on 3 different devices. As soon as pure USB audio was used, the issue was resolved. If you have the means, do try USB audio only and report back.
this post was submitted on 28 Feb 2025
16 points (94.4% liked)
Linux Questions
1406 readers
25 users here now
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions
founded 2 years ago
MODERATORS
Have you checked your shell for ghosts? That's an odd one
What headset do you have? Where do you connect it?
I use a Beyerdynamic Custom One Pro with a Vmoda Boom ProX microphone. It connects to my internal audio card via a normal 3.5mm jack. The problem happens even after I unplug them.
This might be a shot in the dark but maybe it is some sort of induction? The audio may still be generated and somehow it is creating a current in the mic electronics
I'm not a electrical engineer so this could be horribly wrong
Any idea on how I could possibly debug that?