kernel-packages team mailing list archive

Thread
Date
[Bug 1507214] [NEW] Ubuntu 15.04: Not possible to activate bluetooth

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: rolfinator <1507214@xxxxxxxxxxxxxxxxxx>
Date: Sat, 17 Oct 2015 21:47:08 -0000
Reply-to: Bug 1507214 <1507214@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Public bug reported:

Hi.

[Issue]
When I boot up my Xubuntu 15.04 and I try to turn on bluetooth (left-click on the applet in the bar and then click on "Turn bluetooth On") nothing happens. Therefore I cannot pair any BT devices.

[Installed bluetooth packages]
ii  blueman                                     1.99~alpha1-1ubuntu1                       amd64        Graphical bluetooth manager
ii  bluez                                       4.101-0ubuntu25                            amd64        Bluetooth tools and daemons
ii  bluez-alsa:amd64                            4.101-0ubuntu25                            amd64        Bluetooth ALSA support
ii  bluez-cups                                  4.101-0ubuntu25                            amd64        Bluetooth printer driver for CUPS
ii  libbluetooth3:amd64                         4.101-0ubuntu25                            amd64        Library to use the BlueZ Linux Bluetooth stack
ii  libgnome-bluetooth11                        3.8.2.1-0ubuntu12                          amd64        GNOME Bluetooth tools - support library
ii  pulseaudio-module-bluetooth                 1:6.0-0ubuntu6                             amd64        Bluetooth module for PulseAudio sound server

[Log]
Right after boot, these lines are in the syslog:
Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused
Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused

Every other time, the following lines appear in the Syslog:
Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: Exception AttributeError: "'NoneType' object has no attribute 'stdout'" in <bound method Tee.__del__ of <__main__.Tee object at 0x7f19039777d0>> ignored
Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: Starting blueman-mechanism
Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Config
Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Ppp
Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading RfKill
Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Network

Anyway, when I click on "Turn BT on" as stated above, I get the following lines in Syslog:
Oct 17 23:33:22 kernel dbus[932]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Oct 17 23:33:22 kernel blueman-mechanism: Starting blueman-mechanism
Oct 17 23:33:22 kernel dbus[932]: [system] Successfully activated service 'org.blueman.Mechanism'
Oct 17 23:33:22 kernel blueman-mechanism: loading Config
Oct 17 23:33:22 kernel blueman-mechanism: loading Ppp
Oct 17 23:33:22 kernel blueman-mechanism: loading RfKill
Oct 17 23:33:22 kernel blueman-mechanism: loading Network
Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused
Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused
Oct 17 23:33:22 kernel bluetoothd[887]: hci0: Set Powered (0x0005) failed: Busy (0x0a)
Oct 17 23:33:22 kernel bluetoothd[887]: bluetoothd[887]: hci0: Set Powered (0x0005) failed: Busy (0x0a)
Oct 17 23:33:22 kernel bluetoothd[887]: Adapter /org/bluez/887/hci0 has been enabled
Oct 17 23:33:22 kernel bluetoothd[887]: bluetoothd[887]: Adapter /org/bluez/887/hci0 has been enabled
Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: Exception AttributeError: "'NoneType' object has no attribute 'stdout'" in <bound method Tee.__del__ of <__main__.Tee object at 0x7f5e1898a7d0>> ignored
Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: Starting blueman-mechanism
Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Config
Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Ppp
Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading RfKill
Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Network


[Similar bugs]
I tried, as suggested in [1], to "sudo hciconfig hci0 up", which doesn't help at all.


If you need anymore information, I am happy to provide it.


[1] ... https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/411481

** Affects: blueman (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: blueman bluetooth bluez

** Also affects: bluez (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1507214

Title:
  Ubuntu 15.04: Not possible to activate bluetooth

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Hi.

  [Issue]
  When I boot up my Xubuntu 15.04 and I try to turn on bluetooth (left-click on the applet in the bar and then click on "Turn bluetooth On") nothing happens. Therefore I cannot pair any BT devices.

  [Installed bluetooth packages]
  ii  blueman                                     1.99~alpha1-1ubuntu1                       amd64        Graphical bluetooth manager
  ii  bluez                                       4.101-0ubuntu25                            amd64        Bluetooth tools and daemons
  ii  bluez-alsa:amd64                            4.101-0ubuntu25                            amd64        Bluetooth ALSA support
  ii  bluez-cups                                  4.101-0ubuntu25                            amd64        Bluetooth printer driver for CUPS
  ii  libbluetooth3:amd64                         4.101-0ubuntu25                            amd64        Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth11                        3.8.2.1-0ubuntu12                          amd64        GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth                 1:6.0-0ubuntu6                             amd64        Bluetooth module for PulseAudio sound server

  [Log]
  Right after boot, these lines are in the syslog:
  Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
  Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
  Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused
  Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
  Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
  Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused

  Every other time, the following lines appear in the Syslog:
  Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: Exception AttributeError: "'NoneType' object has no attribute 'stdout'" in <bound method Tee.__del__ of <__main__.Tee object at 0x7f19039777d0>> ignored
  Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: Starting blueman-mechanism
  Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Config
  Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Ppp
  Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading RfKill
  Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Network

  Anyway, when I click on "Turn BT on" as stated above, I get the following lines in Syslog:
  Oct 17 23:33:22 kernel dbus[932]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
  Oct 17 23:33:22 kernel blueman-mechanism: Starting blueman-mechanism
  Oct 17 23:33:22 kernel dbus[932]: [system] Successfully activated service 'org.blueman.Mechanism'
  Oct 17 23:33:22 kernel blueman-mechanism: loading Config
  Oct 17 23:33:22 kernel blueman-mechanism: loading Ppp
  Oct 17 23:33:22 kernel blueman-mechanism: loading RfKill
  Oct 17 23:33:22 kernel blueman-mechanism: loading Network
  Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
  Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
  Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused
  Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: gdk_mir_display_open
  Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
  Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused
  Oct 17 23:33:22 kernel bluetoothd[887]: hci0: Set Powered (0x0005) failed: Busy (0x0a)
  Oct 17 23:33:22 kernel bluetoothd[887]: bluetoothd[887]: hci0: Set Powered (0x0005) failed: Busy (0x0a)
  Oct 17 23:33:22 kernel bluetoothd[887]: Adapter /org/bluez/887/hci0 has been enabled
  Oct 17 23:33:22 kernel bluetoothd[887]: bluetoothd[887]: Adapter /org/bluez/887/hci0 has been enabled
  Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: Exception AttributeError: "'NoneType' object has no attribute 'stdout'" in <bound method Tee.__del__ of <__main__.Tee object at 0x7f5e1898a7d0>> ignored
  Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: Starting blueman-mechanism
  Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Config
  Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Ppp
  Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading RfKill
  Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Network

  
  [Similar bugs]
  I tried, as suggested in [1], to "sudo hciconfig hci0 up", which doesn't help at all.

  
  If you need anymore information, I am happy to provide it.

  
  [1] ... https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/411481

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1507214/+subscriptions