Are you kidding me? Still in 20.04??
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
Sta
Still affects 20.04+. My laptop has Bluetooth and it always turns itself
on after a restart.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't s
Several clients told us this problem as Well in 18.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early
I'm experiencing this in 19.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
Status in
It wasn't in my startup applications, but installing "blueman" and
disabling "Auto power-on" in there did the trick. I now have 2 icons
for Bluetooth on my panel instead of 1, but that's fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
Unchecking "Auto power-on" in Blueman PowerManager plugin configuration
solved this issue for me.
Additionally (or alternatively) consider unchecking "Blueman Applet" in
"Startup Applications Preferences".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
@aapo-rantalainen
This might be the solution. Worked for me:
https://github.com/blueman-project/blueman/issues/682
** Bug watch added: github.com/blueman-project/blueman/issues #682
https://github.com/blueman-project/blueman/issues/682
--
You received this bug notification because you are
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
Status in rfkill pa
Happens with 16.04.
Goal: start ubuntu without bluetooth
a)
/etc/bluetooth/main.conf
+InitiallyPowered = false
Didn't work.
b)
rfkill-restore.conf from this ticket
Didn't work.
c)
/etc/rc.local
+rfkill block bluetooth
Didn't work.
Finally disabled bluetooth from BIOS.
--
You received this
** Changed in: rfkill (Ubuntu)
Assignee: Stéphane Graber (stgraber) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay
Quite sure I'm still getting this on 15.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart jo
This bug should be fixed in Ubuntu 15.04, as it currently has systemd
215. The fix is in systemd 209, source:
https://bugzilla.gnome.org/show_bug.cgi?id=638117#c50
** Bug watch added: GNOME Bug Tracker #638117
https://bugzilla.gnome.org/show_bug.cgi?id=638117
--
You received this bug notifica
This bug is rather old, yet not solved. For the moment I'm using the script in
this thread.
I'm on Ubuntu 14.04 (the issue persists also in Mint 14.04), Atheros bluetooth
hardware (Toshiba Portégé Z830).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
13 matches
Mail list logo