view the rest of the comments
Linux
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.
Sounds like a bug, but I'd start by making sure to change the default audio output, and not the app specific audio output. I don't know what desktop environment you're using, but you can start by installing
pavucontrol
and set the fallback/default device in theoutput devices
tab. Then when you need to change the output, change the fallback again.You can also make changes with key bindings using the commandline app.
Since you're using Nobara, I'll assume it's using pipewire and not pulseaudio. If the problem turns out to be a bug, you can post a bug report here: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues