this post was submitted on 19 Oct 2025
10 points (100.0% liked)

Linux

13728 readers
83 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:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
 

I've set up a separate user account on my system for work-related stuff. I usually use my employer's hardware, but we're allowed to use our own device and sometimes it's simply convenient to work on my linux instead of a Mac.

This has led me to a problem that I haven't encountered before: bluetooth seems straight-up wonky when I switch between users. I have bluetooth headphones, for example, that have always worked fine. Noticing that they didn't receive any sound when I switched to the work account was the first hiccup.

No problem, I thought, I'll re-pair every time I switch from the one account to the other. No such luck. Pairing works, but it's associated with the previous account. Not even "forgetting" the device helped.

No problem, I thought. I've got an extra bluetooth headset. I'll pair the one while I'm in the one account and the other while I'm in the other account. No such luck. I get stuck in a "connected", "disconnected" loop.

I had hoped that this was an audio issue and used arch's pulseaudio documentation to make audio sharable between accounts, which worked for a wired connect, but it's at that point that I realized, this doesn't work for bluetooth devices, because of the issues described above.

Has anyone managed to get this working? I'm open to workarounds, as long as they work consistently and allow me to switch back and forth between accounts.

you are viewing a single comment's thread
view the rest of the comments
[–] michaelmrose@lemmy.world 2 points 1 week ago (1 children)

Get a headset which uses a usb dongle bypassing bluetooth entirely

[–] Entitle9294@lemmy.world 1 points 1 week ago (1 children)

That's exactly the route that I was going. Although I'm back at work today and noticed that even a usb-connected wired headset has some issues. I have to do some more testing, but the only way I've been able to make things work seamlessly is by logging out with my private user entirely while I'm working :/

[–] michaelmrose@lemmy.world 1 points 1 week ago

did you know you can run pipewire as a system daemon instead of per user?