Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends

Bug #446657 reported by pablomme on 2009-10-08
550
This bug affects 124 people
Affects Status Importance Assigned to Milestone
GNOME Bluetooth
Unknown
Medium
The Ubuntu Power Consumption Project
Undecided
Unassigned
bluez (Fedora)
Unknown
Unknown
bluez (Ubuntu)
Undecided
Unassigned
Declined for Karmic by Timo Aaltonen
Nominated for Lucid by papukaija
Declined for Maverick by Timo Aaltonen
linux (Ubuntu)
Wishlist
Unassigned
Declined for Karmic by Timo Aaltonen
Nominated for Lucid by papukaija
Declined for Maverick by Timo Aaltonen

Bug Description

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 http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a setting controlling this feature: RememberPowered=true in /etc/bluetooth/main.conf

Questions:
Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't do anything for it? Does bluez's SetProperty actually find the last (if even saved) bluetooth status?

ProblemType: Bug
Architecture: i386
Date: Thu Oct 8 20:54:15 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: gnome-bluetooth 2.28.1-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SourcePackage: gnome-bluetooth
Uname: Linux 2.6.31-12-generic i686

pablomme (pablomme) wrote :
papukaija (papukaija) wrote :

True, the on/off setting should not be lost on restart.

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
papukaija (papukaija) on 2010-01-01
tags: added: ubuntu-unr
Omer Akram (om26er) wrote :

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue , in the default Ubuntu 9.10 install , that affects many people and is quick and easy to fix. So this bug can't be addressed as part of the project.

its rather more like a feature request

For further info about papercuts criteria , pls read > https://wiki.ubuntu.com/PaperCut

Don't worry though, This bug has been marked as "invalid" ONLY in the papercuts project.

Changed in hundredpapercuts:
status: New → Invalid
Omer Akram (om26er) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → Incomplete
papukaija (papukaija) wrote :

This bug is now sent to upstream (at https://bugzilla.gnome.org/show_bug.cgi?id=607334 ).

Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → New
status: New → Confirmed
Charlie Kravetz (charlie-tca) wrote :

Set to triaged; status low as this is a nice to implement feature.

Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
papukaija (papukaija) wrote :

According to https://bugzilla.gnome.org/show_bug.cgi?id=598140#c2 this feature isn't gnome-bluetooth's job, but bluetoothd's (part of bluez). So do I change it here too?

Lightbreeze (nedhoy-gmail) wrote :

@papukaiji: For the Ubuntu task press "Also affects distribution" then change the package name in the box that appears.

Vish (vish) on 2010-01-20
affects: gnome-bluetooth (Ubuntu) → bluez (Ubuntu)
Changed in bluez (Ubuntu):
status: Triaged → New
papukaija (papukaija) on 2010-01-20
Changed in bluez (Ubuntu):
status: New → Confirmed
papukaija (papukaija) on 2010-01-22
summary: - gnome-bluetooth should store user-selected bluetooth on/off status and
- apply it when loading the applet
+ Should store user-selected bluetooth on/off status and apply it when
+ loading the applet
Vish (vish) wrote :

@papukaija: http://wiki.bluez.org/report/1 seems to be the place to report the issue

affects: hundredpapercuts → utils
Changed in utils:
status: Invalid → New
papukaija (papukaija) wrote :

Vish: I found that, but there is no login/signup page to submit bugs.

Vish (vish) wrote :

@papukaija: Yes , the filing of bugs seems a bit weird. :(
However i had a quick look , Try getting some info from these links>
http://wiki.bluez.org/wiki/TracReports
http://wiki.bluez.org/wiki/TracGuide
http://trac.edgewall.org/wiki/TracFaq

If all else fails , try contacting the devs directly > http://www.bluez.org/contact/
I didnt have time to dig deeper. thanks for looking into this.

papukaija (papukaija) wrote :
papukaija (papukaija) wrote :

Sorry, the correct link is:
http://comments.gmane.org/gmane.linux.bluez.kernel/4287

And it seems that this feature is already implemented, but for some reason not working in Ubuntu.

papukaija (papukaija) wrote :

I'm going to edit this bug's title and description since this feature request is implemented,but for some reason not working in Ubuntu.

papukaija (papukaija) on 2010-02-06
affects: bluez (Ubuntu) → gnome-bluetooth (Ubuntu)
papukaija (papukaija) on 2010-02-06
description: updated
papukaija (papukaija) wrote :

For some reason I can't change this bug's title to "Doesn't get the bluetooth's on/off status from the SetProperty D-Bus method that bluetoothd sends"

Vish (vish) on 2010-02-06
summary: - 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
Սահակ (petrosyan) wrote :

this bug has been fixed in Ubuntu 10.04

Vish (vish) wrote :

Սահակ , I'm using Ubuntu 10.04 and its _not_ fixed for here.

Not a gnome-bluetooth problem

affects: gnome-bluetooth (Ubuntu) → ubuntu
Changed in ubuntu:
status: Confirmed → Invalid
status: Invalid → Confirmed

Rather on bluez

affects: ubuntu → bluez (Ubuntu)

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.

pablomme (pablomme) wrote :

@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 existing feature of loading the previously recorded on/off state, which is caused by a dbus communication issue or, most likely, inaction on the dbus communication between gnome-bluetooth and bluetoothd.

The bug title is correct and the comments are on-topic. The only messiness stems from the fact that this bug has required reporting to two different upstreams to discover the nature of the problem, but that's just the way things have panned out.

Please reconsider whether you really wish to move the bug against bluez again.

papukaija (papukaija) wrote :

@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?

affects: bluez (Ubuntu) → gnome-bluetooth (Ubuntu)
Changed in gnome-bluetooth:
importance: Unknown → Undecided
status: Unknown → New
papukaija (papukaija) wrote :

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 gnome-bluetooth:
status: New → Invalid
papukaija (papukaija) wrote :

Is there a way to debug this bug?

Vish (vish) wrote :

@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 fixing in bluez

Attaching my /etc/bluetooth/main.conf
upstream bluez mentions it works with the git version. is this an ubuntu bug?

papukaija (papukaija) on 2010-03-19
Changed in bluez-utils:
status: New → Invalid
papukaija (papukaija) wrote :

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 logout. This means that gnome-bluetooth doesn't get the SetProperty dbus message sent by bluetoothd.

So should this bug be opened for dbus and/or for bluez?

papukaija (papukaija) on 2010-03-19
tags: added: karmic lucid
Vish (vish) wrote :

Even if set :
InitiallyPowered = false

I find the hardware bluetooth light always on for every boot.

Alexander Sack (asac) wrote :

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
RememberPowered = true

however, this causes problems for some users so we shouldn't change this that late this cycle. lets try it next cycle.

affects: gnome-bluetooth (Ubuntu) → bluez (Ubuntu)
Changed in bluez (Ubuntu):
importance: Low → Wishlist
status: Confirmed → Triaged
papukaija (papukaija) wrote :

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
Gleb Kozyrev (gkozyrev) wrote :

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 separate bug? It might get bounced between upstreams the same way :(
BTW, where is Powered state supposed to be stored when RememberPowered = true? Looking for modified files with find / ~/ -newermt '2 min ago' gives me nothing but log files.

pablomme (pablomme) wrote :

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?

Vish (vish) wrote :

Doesnt work for me either in Lucid.
Every boot i have to turn the bluetooth LED off using the kill switch.

Gleb Kozyrev (gkozyrev) wrote :

Mine is 64-bit. I've installed a fresh ubuntu-10.04-beta2-desktop-amd64 today and bluetooth is always on after boot.

papukaija (papukaija) wrote :

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 actually finds the last (if even saved) bluetooth status?

papukaija (papukaija) wrote :

Please remove the wishlist importance since this is a real bug.

description: updated
papukaija (papukaija) wrote :

Has anyone tried to reproduce this bug in Maverick?

tags: added: not-a-wishlist
Vish (vish) wrote :

@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

papukaija (papukaija) wrote :

@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?

Vish (vish) wrote :

@papukaija : InitiallyPowered and RememberPowered are both true by default.

papukaija (papukaija) wrote :

@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 get the SetProperty dbus message sent by bluez's bluetoothd. I'll try if running bluetooth-applet from terminal shows anything special.

papukaija (papukaija) wrote :

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 dbus message?

pablomme (pablomme) wrote :

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.

papukaija (papukaija) wrote :

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) ?

papukaija (papukaija) wrote :

This bug is affecting more people than LP says: http://brainstorm.ubuntu.com/idea/25499/

tags: added: hw-specific ubuntu-une
removed: ubuntu-unr
papukaija (papukaija) wrote :

@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 there are 3 duplicate bugs and in total 140 votes in the brainstorm idea linked in comment 45. Thanks in advance!

papukaija (papukaija) on 2010-10-30
tags: added: maverick
Kent Asplund (hoglet) wrote :

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 workaround for me, and others, while waiting.

papukaija (papukaija) on 2011-04-21
tags: added: natty

The problem remains in Oneiric. Bluetooth is always on after a reboot. MacBook Air 3,2.

papukaija (papukaija) on 2011-09-30
tags: added: oneiric
papukaija (papukaija) wrote :

I just linked six duplicate bugs to this report. Please remove the wishlist importance. Thanks in advance.

Colin Ian King (colin-king) wrote :

Problem also in Precise.

papukaija (papukaija) on 2012-01-09
affects: bluez (Ubuntu) → linux (Ubuntu)
Changed in bluez (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Invalid
no longer affects: gnome-bluetooth
no longer affects: bluez
tags: removed: not-a-wishlist
tags: added: precise
zee (zeefreak) wrote :

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.

http://www.us-cert.gov/cas/tips/ST05-015.html

Changed in bluez (Ubuntu):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Martin Pitt (pitti) on 2012-01-11
Changed in bluez (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → Mathieu Trudel-Lapierre (mathieu-tl)
papukaija (papukaija) wrote :

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.

papukaija (papukaija) wrote :

*now

Changed in gnome-bluetooth:
importance: Unknown → Medium
status: Unknown → New

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 Trudel-Lapierre (mathieu-tl) → nobody
papukaija (papukaija) on 2012-02-25
tags: added: battery-power-consumption
tags: removed: ubuntu-une
Sam_ (and-sam) on 2012-02-26
tags: added: amd64

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 from on to off every time the computer boots basically extends the time necessary for people to start using their device, and makes them see Ubuntu as "user-unfriendly".

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
<email address hidden>wrote:

> 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 from on to off every time the computer boots
> basically extends the time necessary for people to start using their
> device, and makes them see Ubuntu as "user-unfriendly".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions
>

yep since a few days ago this seems to be working fine. At least on my Lenovo T61 with 12.04 updates.

papukaija (papukaija) wrote :

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 issues to even enable BT before restarting the BT service in the system.

The improvement was from this upload:

bluez (4.98-2ubuntu4) precise; urgency=low
[...]
  * Eliminate the /etc/default/bluetooth conffile as it's not the Upstart
    way. Transition the BLUETOOTH_ENABLED variable to an Upstart override
    variable if it's been changed.

I will test again since there has been many updated packages after my testing.

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.

Sam_ (and-sam) wrote :

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 settings - it's still off in g-c-c.

bluez:
  Installed: 4.98-2ubuntu7
  Candidate: 4.98-2ubuntu7
  Version table:
 *** 4.98-2ubuntu7 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

Seems to work fine Precise.

This is still a problem in Quantal up to date.
At restart, I have to turn the bluetooth off every time.

papukaija (papukaija) on 2012-10-22
tags: added: quantal
removed: karmic maverick
papukaija (papukaija) wrote :

The upstream is working on a fix for this bug.

Kyle Fazzari (kyrofa) wrote :

Sounds like it might be the issue outlined here, which includes a fix: https://bugs.launchpad.net/bugs/1073669 .

papukaija (papukaija) wrote :

That bug is indeed the same bug but I haven't tried if the fix works.

Florian Stoll (flostoll) wrote :

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.

Florian Stoll (flostoll) wrote :

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...

papukaija (papukaija) wrote :

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
Martin Albisetti (beuno) wrote :

It doesn't seem to be remembered for me. I turn it off, reboot, and it's back on.

pablomme (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.

Elias K Gardner (zorkerz) wrote :

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 this bug notification because you are subscribed to the bug
> report.
> 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 this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions
>

papukaija (papukaija) wrote :

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

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.

papukaija (papukaija) on 2013-10-12
tags: added: raring
removed: lucid natty oneiric
Jesse Michael (jesse.michael) wrote :

It's kind of depressing that this bug is still not fixed four and a half years later in trusty.

Elijah Lynn (elijah-lynn) wrote :

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 is now a true upstream with gnome-bluetooth. It also appears to be related to those with an actual hardware wireless radio or bluetooth kill switch. This may explain why it works for certain people.

This is present in Ubuntu 14.04 with bluez 4.101-0ubuntu13 and gnome-bluetooth 3.8.2.1-0ubuntu4 and not sure it matters but I also have indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2.

I got this with a dpkg-query -l "*blue*" in case anyone else is wondering what
versions they are running.

ps. Possible duplicate here -> https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/280811

Changed in gnome-bluetooth:
status: New → Unknown
zeus (zeus-tunalkan) wrote :

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 user-friendly. If it's useful for someone, when I use KDE I don't have this problem. Only with Gnome (same Ubuntu and Mint),

papukaija (papukaija) wrote :

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

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: Confirmed → Invalid
Ubuntu QA Website (ubuntuqa) wrote :

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
spike speigel (frail-knight) wrote :

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.