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
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Incomplete
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.

Revision history for this message
Erik (borych) wrote :
Revision history for this message
Valmantas Palikša (walmis) wrote :

Thanks for the report

Changed in blueman:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Valmantas Palikša (walmis) wrote :

Commited to svn, easy fix :)

Changed in blueman:
status: Confirmed → Fix Committed
Revision history for this message
Erik (borych) wrote :

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

Revision history for this message
kylea (kylea) wrote :

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

Revision history for this message
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)
Changed in blueman:
status: Fix Committed → New
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in blueman (Ubuntu):
status: New → Confirmed
Ross Gammon (rosco2)
affects: ubuntu → blueman (Ubuntu)
Revision history for this message
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  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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