A/lib/systemd/system/bluetooth.service' is unwritable ]
Hin atomic yes everything in
/usr/lib/etc
Athat.. is unpleasant.
Hand
/usr/local
Kand /var, of course
Hnot really, just put the service file in /etc and move on with your day
Aand a simple cp/mv bluetooth.service to /etc will work?
Kyep
Ksudo cp, of course
Aindeed.
Kyou can also use the classic
Ksystemctl edit service.serviceand change only what you need
Kthat writes to /etc
Kwithout copying the entire file
AI've never seen that before.
Asystemctl edit service.service didn't work for my need.
Ha lot of people complaining that they cant change anything in atomic (that i have seen) dont realise they either
1. do it wrong (like trying to edit systemd files in /lib)
2. dont accept that its just different (make your own image if you want to do some deep system changes in /usr)
3. does not want to put in the effort to learn how it actually works
1. do it wrong (like trying to edit systemd files in /lib)
2. dont accept that its just different (make your own image if you want to do some deep system changes in /usr)
3. does not want to put in the effort to learn how it actually works
Hthe latter 2 being the ones that shoot it down without trying it from what i have seen so far
AI need the bluetooth.service file edited, for whatever reason bluetooth volume doesn't adjust by volume control and is always extrememly loud. I found a link on Ubuntu's forums about how to fix it and was able to do the same in Garuda/Manjar/Xero/Endevor, and a few others.
Hi didnt know about that systemd had stuff in /etc that they used to override what it had in /lib before i used ublue
KAnyone own a handheld/tablet other than an Ally/Deck/Legion Go AND have Fallout: London installed? Looking for cool screenshots for the website
Hjust use the 
systemctl edit service.serviceI did that, it didn't work. I manually moved it too. It still didn't work.
Hdid you do
systemctl daemon-reloadI did that too. It didn't work.
Hwhat changes are you trying to do?
AI also did sudo systemctl restart bluetooth and that didn't work.
AChange
ExecStart=/usr/lib/bluetooth/bluetoothd
to
ExecStart=/usr/lib/bluetooth/bluetoothd --plugin=a2dp
ExecStart=/usr/lib/bluetooth/bluetoothd
to
ExecStart=/usr/lib/bluetooth/bluetoothd --plugin=a2dp
PGuys at the Grub menu is there no way to get the dpad to work? Or do you have to have a keyboard plugged in to change between boot options?
Kcurrently a keyboard is required, dpads aren't registered by grub
Kthere's work being done to make volume buttons work to navigate it
PThat would be sweet
Rshould i install bazzite or ublue on my deck if i want to use it as a daily driver plugged into my desktop usb-c dock
Rer bluefin
Kbazzite is part of ublue, if you mean bluefin it might work, but Bazzite has exra work done for firmware and the like
Kthat you'll probably need
Hsystemctl show bluetooth.servicebazzite then add whatever to make it bluefinny
Aand what am I looking for here?
Kshow us
Aum... You really don't want this wall of text. If it's supposed to display whether it's enabled, active, disabled, or dead it didn't do that.
Ksystemctl show bluetooth.service | fpaste
JOh, what did I do exactly? 
MIm going to install bazzite os later once my usb c thumb drive arrives
KExecStart={ path=/usr/libexec/bluetooth/bluetoothd ; argv[]=/usr/libexec/bluetooth/bluetoothd ; ignore_errors=no ; start_time=[Sun 2024-07-28 13:38:19 MDT] ; stop_time=[n/a] ; pid=15030 ; code=(null) ; status=0/0 }KYour change isn't there
Ain that case it's not loading from /etc nor from the edit service.service.
