Blueman Does not Remember Last On/Off State after Reboot

Bug #1449100 reported by Ang Bongsong on 2015-04-27
This bug affects 4 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)

Bug Description

This is currently occurring with Blueman 1.23 under Xubuntu 14.04.2 and Xfce 4.12, but I've noticed the issue in previous releases as well.

Basically, after a shutdown or reboot, bluetooth will be On by default in Blueman, even if its last state was Off. If I simply log out and back into my session though, Blueman will remember its state. I have to run a simple startup script (sleep 7 && rfkill block bluetooth) in order to have bluetooth off in Blueman by default. There should be a preference for this in Blueman, as having bluetooth enabled at startup can be a security issue for some users, and well, why not have the choice presented to you in the first place?

Launchpad Janitor (janitor) wrote :

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

Changed in blueman (Ubuntu):
status: New → Confirmed
Etienne URBAH (eurbah) wrote :

blueman 2.0.4-1ubuntu2 under Ubuntu 16.04 does NEVER remember its state, even after simple logout and back into my session.

Prahlad Yeri (prahladyeri) wrote :

@Etienne Its astounding that this bug is still occurring in Xubuntu 16.04. Have you found any solution yet?

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

Other bug subscribers