If initially turned off, blueman-applet doesn't turn back on properly and doesn't connect to Headset service after X restart.
| 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 : | #1 |
| Valmantas Palikša (walmis) wrote : | #2 |
| Changed in blueman: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Valmantas Palikša (walmis) wrote : | #3 |
Commited to svn, easy fix :)
| Changed in blueman: | |
| status: | Confirmed → Fix Committed |
| Erik (borych) wrote : | #4 |
Ah, the very definition of great work... You have my gratitude.
In other words, thanks! :)
| kylea (kylea) wrote : | #5 |
I can confirm the behaviour - looking forward to the fix.
| alfred haines (alfredhaines) wrote : | #6 |
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.
| Changed in blueman: | |
| status: | Fix Committed → New |
| status: | New → Fix Released |
| Launchpad Janitor (janitor) wrote : | #7 |
Status changed to 'Confirmed' because the bug affects multiple users.
| affects: | ubuntu → blueman (Ubuntu) |
| Changed in blueman (Ubuntu): | |
| status: | New → Confirmed |
| Ross Gammon (rosco2) wrote : | #8 |
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 |


Thanks for the report