Linux

8743 readers

156 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 2 years ago

MODERATORS

[email protected]

Audio device completely crashed by teams (gehirneimer.de)

submitted 3 weeks ago by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

I have been using the "Teams For Linux" flathub app for a few days and at first I celebrated, because I could finally use teams without major workarounds and so that it just works. However today it decided to crash my audio device after about 20 minutes and it did so consistently... It crashes it so hard, that I need to restart my system every time it occurrs...

Things that do not work to get my audio back up and running:

restarting pipewire service with systemctl --user restart pipewire.service
restarting pipewire-pulse with systemctl --user restart pipewire-pulse.service
restarting alsa with sudo alsactl -F restore
relogging
unplugging USB

I am using Fedora 41 and my audio interface is the Motu M2

As far as I can tell the audio is just broken beyond repair and I have no idea why. I've always had audio problems on linux, but never to this degree. Maybe I have to try another distro, but I actually don't really want to. It is just super annoying and if anyone has an idea how to fix this mess I will try it and hope that it works :D

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 3 weeks ago (1 children)

I don't know if I can resolve this, but I've done some reading and the m2/m4 have some known issues with Linux.

Some patches and configs and instructions are here:

https://github.com/kiosion/alsa-motu-m2

Aside from that, there could be another application that is locking the card which is why you're getting the resource busy error.

As mentioned here:

https://unix.stackexchange.com/questions/753676/pipewire-pulse-no-sound-playback-open-failed-device-or-resource-busy

And some more issues/troubleshooting specifically with the m4:

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3312

[–] [email protected] 2 points 3 weeks ago

I will look into that, thanks for your help, time and effort ❤️