In addition, when it's turned off either way, via applet or g-c-c this doesn't survive a reboot. It has to be turned off every time after login, acknowlegded thanks to the fix of Bug 811249. But why would it run a process which is expected to be disabled.
This where startup applications helped out where it was removed from, but allowed to disable it. Acknowledged this could also be worked around by 'remember running apps' aka gnome-session-save which currently isn't implemented. https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-session-management But what if one isn't a friend of saving a session, it then needs an upstart script in order to disable bluetooth? At least turning it off-on via applet would only be one click away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815539 Title: When bluetooth is disabled via indicator the entry to turn it on again is greyed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/815539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
