** Changed in: bluez (Fedora)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (283625).
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update
Launchpad has imported 58 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=570073.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: bluez (Fedora)
Status: Unknown => Confirmed
** Changed in: bluez (Fedora)
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
For anyone who might find their way here while using newer versions of
Ubuntu such as 16.04 LTS, 16.10, 17.04...
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
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/446657
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
I'm on Ubuntu 14.04, a Toshiba Portégé Z830 with Atheros bluetooth,
gnome-bluetooth v 3.8.2.1. I can confirrm I'm still experiencing this
issue for the past two or three years. Never seen it solved. Bluetooth
state always on after reboot. Indeed having to switch it off every time
makes Ubuntu less
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-bluetooth
Status: New = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method
Yes, very depressing. This is why people use Macs.
But there is no way I am going to use a Mac's OS and this is free and
open software so I would like to get to the bottom of this. I just read
through this entire issue and
https://bugzilla.gnome.org/show_bug.cgi?id=638117#c9 and it appears this
It's kind of depressing that this bug is still not fixed four and a half
years later in trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update
** Tags removed: lucid natty oneiric
** 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/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method
I have this problem with my Lenovo X1 running raring. I turn off
Bluetooth, restart the machine, and voilà: it is back on and draining
battery power. This happens every time. Sometimes I also see it being
re-enabled after awakening from hibernation.
--
You received this bug notification because
I think it's better to keep this bug open. I've been using Raring for
few weeks now and the bluetooth is sometimes (possibly after installing
an updated kernel) enabled on boot after I've disabled it before
shutting down.
** Changed in: bluez (Ubuntu)
Status: Incomplete = Confirmed
--
It doesn't seem to be remembered for me. I turn it off, reboot, and it's
back on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the
Original reporter here. I've not had this problem for a long time (I've
changed laptops since I reported it), and after the switch to indicator-
bluetooth in raring things continue to work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
this has resurfaced for me in raring
On Sunday, April 14, 2013, pablomme wrote:
Original reporter here. I've not had this problem for a long time (I've
changed laptops since I reported it), and after the switch to indicator-
bluetooth in raring things continue to work fine.
--
You received
I can also confirm that the bluetooth status is remembered between
reboots in Raring. Could the original reporter or someone else please
confirrm this?
** Changed in: bluez (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Since some time ago the last state is remembered after restart in 13.04
on my Lenovo T500. The icon in indicator menu is only visible if
bluetooth is enabled...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In Ubuntu 12.04 and 12.10 it worked fine on my Lenovo T500 but in 13.04
there seems to be a regression because it does not remember the last
state of bluetooth device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubuntu-power-consumption
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the
Sounds like it might be the issue outlined here, which includes a fix:
https://bugs.launchpad.net/bugs/1073669 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off
That bug is indeed the same bug but I haven't tried if the fix works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
** Tags removed: karmic maverick
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that
The upstream is working on a fix for this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that
This is still a problem in Quantal up to date.
At restart, I have to turn the bluetooth off every time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't
Seems to work fine Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that bluetoothd sends
To manage
Nothing changed (indicator is confused since four years due to confused
responsibilities).
Cold boot: bluetooth is off (g-c-c), indicator states it's on and it can be
turned off.
Reboot: bluetooth is off (g-c-c), indicator states it's off and it can be
turned on.
Enable it on indicator, open
This is still affecting Ubuntu 12.04 LTS.
It is still seen as an obvious defect by most users, and it would be sad not to
see it fixed in this LTS, even more because it has been around for a while.
A lot of people never use bluetooth on their device and want to save battery
life. Switching it
Get me if I'm wrong by in 12.04 my bluetooth seems to remember its turned
off state across restarts at least judging by the indicator remaining
grayed out (I don't know if this means it is really turned off).
On Mon, Apr 2, 2012 at 6:39 PM, Stéphane Guillou
446...@bugs.launchpad.netwrote:
This
yep since a few days ago this seems to be working fine. At least on my
Lenovo T61 with 12.04 updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't
There has indeed been some improvements to this bug in Precise but the
indicator menu is still confused by the bluetooth status, I tested this
a while ago with my mobille phone and the BT status wasn't working
correctly (and the initial status in the indicator menu was misleading).
I also had some
The issue is definitely still here on my Samsung N310, with everything
updated today.
I either deactivate the bluetooth from the indicator dropdown menu, or
inside the settings window, the result is the same: it is back on when I
reboot my computer.
--
You received this bug notification because
** Tags added: battery-power-consumption
** Tags removed: ubuntu-une
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
** Tags added: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that bluetoothd sends
To manage
We're covering this through an upstart job (rfkill-store, rfkill-
restore) that should save and restore all killswitch states; so I'm
unassigning this since the rest of the work in gnome-bluetooth and bluez
should come from upstreams.
** Changed in: bluez (Ubuntu)
Assignee: Mathieu
*now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that bluetoothd sends
To manage notifications about
Interesting. Gnome rejected this bug at
https://bugzilla.gnome.org/show_bug.cgi?id=598140#c2 but know Bastien
Nocera [gnome-bluetooth developer] thinks at
https://bugzilla.gnome.org/show_bug.cgi?id=638117#c9 that this is a bug
in Gnome and bluez.
** Bug watch added: GNOME Bug Tracker #638117
** Changed in: gnome-bluetooth
Status: Unknown = New
** Changed in: gnome-bluetooth
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status
** Changed in: bluez (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Mathieu
Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Problem also in Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that bluetoothd sends
To manage
** Package changed: bluez (Ubuntu) = linux (Ubuntu)
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
** No longer affects: gnome-bluetooth
as far as i'm concerned, this is a security issue. having open avenues
for attack reopen every boot is not to be overlooked. even us-cert has a
bulletin on bluetooth security and the first item under 'how can you
protect yourself' is to disable it when you're not using it.
** Bug watch added: Red Hat Bugzilla #570073
https://bugzilla.redhat.com/show_bug.cgi?id=570073
** Also affects: bluez (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=570073
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I just linked six duplicate bugs to this report. Please remove the
wishlist importance. Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that bluetoothd sends
To manage
The problem remains in Oneiric. Bluetooth is always on after a reboot.
MacBook Air 3,2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the
** Tags added: natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doesn't update from the SetProperty D-Bus
method that bluetoothd sends
--
ubuntu-bugs
This problem affects me too on Natty.
U nfortunately for me the saved state of bluetooth is off. This means that I
have no bluetooth on startup nor after resume. As I am using a bluetooth mouse
it has been very irritating.
Setting RememberPowered = false in /etc/bluetooth/main.conf is the
** Tags added: maverick
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
@members of bug-control team: Please change this bug's importance from
wishlist to something else as this is a real bug (but seems to be hw-
specific). I suggest low or even medium importance, given that this bus
isn't the end of world but affect more than just those 7 people reported
by LP as
This bug is affecting more people than LP says:
http://brainstorm.ubuntu.com/idea/25499/
** Tags added: hw-specific ubuntu-une
** Tags removed: ubuntu-unr
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
I have Samsung NC10 netbook with Ubuntu Lucid 10.04 UNE. The intenrnal
bluetooth device is a BCM2046 Bluetooth Device.
So this is a bug in the kernel (supposing that the bt drivers are part
of it) ?
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd
As I mentioned in an earlier comment, I suspect this bug has some
hardware-dependent component to it. I used to have this on a Dell Mini 9
with Jaunty and Karmic, but my Eee PC 1201N with Lucid works correctly.
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
@Vish: That would explain why bluez.org can't confirm this bug. I'll
test with 2.6.34-lucid and 2.6.35-rc1-lucid soon. Is your attached
main.conf a file with default settings because I'm not sure if my file
has the defaults, especially about the RememberPowered setting?
--
Bluetooth's on/off
@papukaija : InitiallyPowered and RememberPowered are both true by
default.
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs,
@Vish: I tested both 2.6.34-lucid and 2.6.35-rc1 without success (with
InitiallyPowered and RememberPowered as true). I noticed from upstream
kernel bug report (linked to this bug's dupplicate) that this shouldn't
be a bug in Kernel. Maybe this is still a bug in bluetooth-applet which
would not
I manually started bluetooth-applet from the terminal (in Lucid on
Ubuntu's 2.6.32 Kernel) and it didn't show any error messages. I attach
the debug messages if someone wants to look at them. Is it possible that
the applet doesn't actually save the last bt-status or that it just
doesn't get the
Has anyone tried to reproduce this bug in Maverick?
** Tags added: not-a-wishlist
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
@papukaija : In Lucid , I'v tested with mainline Kernel .34 and .35 , both of
which remember the killswitch state of the previous session. Bug might have
been in the kernel?
Could you try the mainline kernels too?
https://wiki.ubuntu.com/KernelMainlineBuilds
--
Bluetooth's on/off status
Doesnt work for me either in Lucid.
Every boot i have to turn the bluetooth LED off using the kill switch.
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you
Mine is 64-bit. I've installed a fresh ubuntu-10.04-beta2-desktop-amd64
today and bluetooth is always on after boot.
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification
Gleb (about your comment 31): The only bug reported in this bug report
is that bluetooth on/off status isn't remembered on boot.
All: How to debug bluez to see if the dbus message is even sent? If it
is sent, why gnome-bluetooth doesn't do anything for it? Or to see if
bluez's SetProperty
Please remove the wishlist importance since this is a real bug.
** Description changed:
Binary package hint: gnome-bluetooth
Gnome's bluetooth applet should get a bluetooth device's on/off status
through dbus from SetProperty setting sent by bluetoothd. This
information was given in
In my case (on lucid) dbus seems to be working just fine: the applet is able to
switch bluetooth on/off and is correctly notified when switched via rfkill.
Still bluetooth is always on at startup regardless of the applet and
InitiallyPowered/RememberPowered settings. Should this be filed as a
I was about to add that this bug seems fixed in lucid, but clearly
Gleb's comment indicates otherwise. Mine is a clean 32-bit install from
beta 2 - Gleb, how does your installation differ from mine?
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd
Wait wait. Those are the default values. So, we're back in finding out
why gnome-bluetooth doesn't get the SetProperty dbus message sent by
bluetoothd. How to debug dbus?
** Changed in: bluez (Ubuntu)
Status: Triaged = Confirmed
--
Bluetooth's on/off status doesn't update from the
Even if set :
InitiallyPowered = false
I find the hardware bluetooth light always on for every boot.
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a
this would require us to change main.conf to:
# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true
# Remember the previously stored Powered state when initializing adapters
** Changed in: bluez-utils
Status: New = Invalid
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In main.conf, there is:
# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true
If you set this to false, the bluetooth-applet will show bt as disabled
regardless of your bt status at
** Tags added: karmic lucid
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@Baptiste Mille-Mathias : How do we proceed with this bug? bluez says
its not their bug . And everyone else says its a bluez bug.
I had filed a similar bug [ Bug #503286 ] regarding the hardware switch not
remembering the bluetooth state.
And kernel upstream also mentioned that the bug needs
Rather on bluez
** Package changed: ubuntu = bluez (Ubuntu)
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Not a gnome-bluetooth problem
** Package changed: gnome-bluetooth (Ubuntu) = ubuntu
** Changed in: ubuntu
Status: Confirmed = Invalid
** Changed in: ubuntu
Status: Invalid = Confirmed
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd
Honnestly this bug is a mess, the title is Bluetooth's on/off status
doesn't update from the SetProperty D-Bus method that bluetoothd sends
but th epeople complains about non-remembering the power status after
computer reboot, which is *totally* different.
--
Bluetooth's on/off status doesn't
@Baptiste: please read the full bug history. This bug was initially
reported against gnome-bluetooth, forwarded upstream, rejected, then
moved against bluez, forwarded upstream, and confirmed non-existent
there. This turns out to be an Ubuntu-specific problem that prevents
bluez from using its
@Baptiste: Please read
http://permalink.gmane.org/gmane.linux.bluez.kernel/4302
@All: I'm going to re-assign this bug for gnome-bluetooth and to remove
the bug watcher since it was created for the feature request. Should
this bug be opened for dbus too?
** Package changed: bluez (Ubuntu) =
It's of course possible that the dbus message in question is not sent by
bluetoothd's (part of bluez).
I'm setting the external tracker to invalid since this bug seems to be
an Ubuntu specific problem (see comment 22 and
http://permalink.gmane.org/gmane.linux.bluez.kernel/4291 ).
** Changed in:
Is there a way to debug this bug?
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- Should store user-selected bluetooth on/off status and apply it when loading
the applet
+ Bluetooth's on/off status doesn't update from the SetProperty D-Bus method
that bluetoothd sends
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
this bug has been fixed in Ubuntu 10.04
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Սահակ , I'm using Ubuntu 10.04 and its _not_ fixed for here.
--
Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that
bluetoothd sends
https://bugs.launchpad.net/bugs/446657
You received this bug notification because you are a member of Ubuntu
Bugs, which is
84 matches
Mail list logo
