Bug#550667: please test whether this bug is fixed or not with latest 4.56 release
On Tue, Oct 13, 2009 at 02:39:29PM +0200, Andrea Veri wrote: would you mind looking if this bug is fixed with bluez 4.56 version recently uploaded to the archive? you might need to wait a bit to have it built / published since it got uploaded today. So, I originally reported this bug against gnome-bluetooth, which had an explicit Turn Bluetooth off menu item. I wanted it to remember that setting across reboots. Current gnome-bluetooth doesn't actually seem to *have* that setting, so I can't seem to turn bluetooth off at all. Meanwhile, I also upgraded to bluez 4.56-2, but I don't see how that helps. In short, this seems to have gotten worse with newer gnome-bluetooth, and bluez didn't affect it at all. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550667: please test whether this bug is fixed or not with latest 4.56 release
Il giorno Wed, 14 Oct 2009 06:03:21 -0700 Josh Triplett j...@joshtriplett.org ha scritto: In short, this seems to have gotten worse with newer gnome-bluetooth, and bluez didn't affect it at all. well, gnome-bluetooth upstream authors redirected me to find the bug into bluez (bluetoothd) and not gnome-bluetooth itself. Actually we can't say whether removing *that* setting is a bad / good reason, upstream decided to do that so it's not our / your fault. Anyway I guess that know bluetoothd runs in background and its enabled automatically at boot time, so you won't need to close / open it. I would say it's better this way so the user does not need to bother opening / closing it plus I don't think that having it open all the time will slow down your computer. What do you think? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550667: please test whether this bug is fixed or not with latest 4.56 release
On Wed, Oct 14, 2009 at 05:49:30PM +0200, Andrea Veri wrote: Il giorno Wed, 14 Oct 2009 06:03:21 -0700 Josh Triplett j...@joshtriplett.org ha scritto: In short, this seems to have gotten worse with newer gnome-bluetooth, and bluez didn't affect it at all. well, gnome-bluetooth upstream authors redirected me to find the bug into bluez (bluetoothd) and not gnome-bluetooth itself. Actually we can't say whether removing *that* setting is a bad / good reason, upstream decided to do that so it's not our / your fault. Anyway I guess that know bluetoothd runs in background and its enabled automatically at boot time, so you won't need to close / open it. I would say it's better this way so the user does not need to bother opening / closing it plus I don't think that having it open all the time will slow down your computer. What do you think? I have no concerns whatsoever about having another daemon running. I have serious concerns about the impact to battery life caused by having the bluetooth radio on when not needed. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550667: please test whether this bug is fixed or not with latest 4.56 release
hi, would you mind looking if this bug is fixed with bluez 4.56 version recently uploaded to the archive? you might need to wait a bit to have it built / published since it got uploaded today. Andrea -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
