Are you kidding me? Still in 20.04??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
To manage notifications about
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot
Several clients told us this problem as Well in 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
To manage
I'm experiencing this in 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
To manage notifications about this
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
Bugs, which is subscribed to
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
Bugs, which is
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due
Quite sure I'm still getting this on 15.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
To manage notifications
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
Bugs, which is
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
Still reproduce this problem in Raring.
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
To
I upgraded to Raring and the bluetooth status is restored between
reboots. Could someone confirrm this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled
@Kyle Ya, I agree, there are better solutions, 1 sec delay solution was
just a compromise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due
Ive prepared the new implementation of the service. It has at least two
advantages (compared to previous solutions) - it's adaptive (longer it
takes to initialize devices - longer it waits between attempts, and
these delays can be easily configured), and it does not reset already
set devices.
That seems overly complex, for what it's worth, I already have the
design on how to fix this properly but haven't got around to implement
it yet.
The changes will simply be to have the job trigger on bluetooth-device-added
and network-device-added and store running state of the job so that we
@Stéphane, yeah that solution sounds a bit more slick. I don't see those
signals in there already-- are there already upstart scripts that run
when a bluetooth or network device is added? I can play with this if you
like.
--
You received this bug notification because you are a member of Ubuntu
Those events come from the udev bridge, the two you're interested in are:
- net-device-added
- bluetooth-device-added
My idea was roughly to change /etc/init/rfkill-restore.conf with:
- start on local-filesystems or (local-filesystems and net-device-added) or
(local-filesystems and
Ive had the same problem on Ubuntu 12.04 - bluetooth applet used to forget
the state during shutdown, and switched bluetooth on during startup.
I was able to solve it by removing my internet-over-bluetooth profile from
NetworkManager. As I saw from the logs, even though I didnt use this profile,
Looks like the problem is caused by race condition during startup - by
the moment rfkill-restore gets executed the driver for bluetooth is
not completelly initialized, so the script does not see the device,
thus cannot switch it on/off. At least it was like this on my Ubuntu
12.04. I solved the
Ive just noticed the patch. Tried it - works for me. Maybe it still
makes sense to add constant 1 sec delay in beginning of the script (and
maybe reduce conditional delays to 3 sec to balance timings). I think
its important, because for all users, who encounter this problem, the
service is going
@Eugene: Thanks for trying the patch. I feel like the one second delay
is rather hacky though; this script doesn't always fail the first time,
and if you disagree with the five-second resolution on the retries,
changing that rate is probably a better solution than the one-second
delay.
--
You
Sorry but I don't currently have access to the laptop with which I have
the issue but will try to report here as soon as I have tested it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
To clarify: The patch attached in comment 1 is a completely replacement
for /etc/init/rfkill-restore.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rfkill (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
This bug occurs in Ubuntu 12.10 and Ubuntu 12.04 (and probably earlier
releases).
I confirm that Kyle's Respawn... replacement /etc/init/rfkill-
restore.conf fixes it! Thanks Kyle!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Stéphane- I'm assigning this bug to you for review/handling, since
it looks like you added the rfkill upstart jobs. Could we get Kyle's
replacement rfkill-restore.conf into the rfkill package?
** Changed in: rfkill (Ubuntu)
Assignee: (unassigned) = Stéphane Graber (stgraber)
--
You
The attachment Respawn for up to 60 seconds if the kill switches aren't
present. of this bug report has been identified as being a patch. The
ubuntu-reviewers team has been subscribed to the bug report so that they
can review the patch. In the event that this is in fact not a patch you
can
Specifically, this fix is applicable to rfkill in just 12.04, 12.10, and
the in-development Raring branch. Previous to 12.04, there weren't any
rfkill store/restore upstart jobs at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is your script bullet proof? In my case, the issue seems to be more
complicated (see bug 446657 for more details).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay
Just to add that the upstream for gnome-bluetooth is working for a more
global fix (not all Linux distros use upstart).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't
papukaija, give it a shot and see if it improves things. This script
relates to comment 54
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446657/comments/54)
of bug 446657 . Make a backup of /etc/init/rfkill-restore.conf and
replace it with the one attached to this bug. Then disable
34 matches
Mail list logo
