If initially turned off, blueman-applet doesn't turn back on properly and doesn't connect to Headset service after X restart.

Bug #364238 reported by Erik on 2009-04-20
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Blueman
Fix Released
High
Unassigned
blueman (Ubuntu)
Undecided
Unassigned

Bug Description

Steps to reproduce:
1. Turn Bluetooth off via blueman-applet's menu.
2. Restart X
3. Start blueman-applet
4. Turn Bluetooth on via blueman-applet's menu.
Expected results: bluetooth turns on, blueman-applet's icon becomes non-greyed, recent connections are available.
Actual results: bluetooth turns on, but blueman-applet's icon is still greyed and recent connections are not available, as if bluetooth were still off.
5. Start blueman-manager
6. Try to connect to (previously paired) headset via right-click - Connect Headset Service
Expected results: blueman connects to headset
Actual result: blueman doesn't connect to headset, Failed, log shows "object is not iterable" error (log attached)

Reproducible: always, doesn't matter if you reboot or restart X.
Workaround: restart blueman-applet after turning bluetooth back on.

Erik (borych) wrote :
Valmantas Palikša (walmis) wrote :

Thanks for the report

Changed in blueman:
importance: Undecided → High
status: New → Confirmed
Valmantas Palikša (walmis) wrote :

Commited to svn, easy fix :)

Changed in blueman:
status: Confirmed → Fix Committed
Erik (borych) wrote :

Ah, the very definition of great work... You have my gratitude.
In other words, thanks! :)

kylea (kylea) wrote :

I can confirm the behaviour - looking forward to the fix.

alfred haines (alfredhaines) wrote :

After reboot Bluetooth does not reconnect correctly for Motorola 300 headset and my Dell keyboard does not pair until I remove it then rerun setup.

GNOM (5littlegnom5) on 2014-08-15
Changed in blueman:
status: Fix Committed → New
status: New → Fix Released
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Ross Gammon (rosco2) on 2015-03-01
affects: ubuntu → blueman (Ubuntu)
Changed in blueman (Ubuntu):
status: New → Confirmed
Ross Gammon (rosco2) wrote :

This bug was noted as fixed-upstream recently. Are you able to confirm which version of Ubuntu you are running now, and whether this is fixed?

Changed in blueman (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers