Bug 362007 - On-demand modus & always enabling bluetooth-using integration (e.g. file sending)
Summary: On-demand modus & always enabling bluetooth-using integration (e.g. file send...
Status: REPORTED
Alias: None
Product: Bluedevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.6.2
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-20 17:07 UTC by Friedrich W. H. Kossebau
Modified: 2018-02-12 06:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Friedrich W. H. Kossebau 2016-04-20 17:07:54 UTC
I usually have bluetooth turned off via the Plasma bluetooth control on my laptop (for power & security/privacy reasons).

Still I use it now and then, e.g. to send a file to another device.

Problems:
* needs me to explicitely enable & disable bluetooth every time I want to use it
* the options where bluetooth integration is available sometimes are hidden (e.g. the send-file action in the filemanager integration), so I do not learn about them in my normal working modus

Requested features:
It would be nice to have the possibility of on-demand enabling of bluetooth:
when bluetooth integration is enabled, the options are always shown (using static data where needed, like known other devices). 
if an option then is selected it result in bluetooth being enabled on-demand. 
if the action has a defined time scope, like file sending, bluetooth would be disabled afterwards again (unless other services requested on-demand mode and are still running, or the user actively set it to "always on").

Nice-to-have:
perhaps the user could be optionally also queried if they really want to turn on bluetooth for that action (perhaps they are in an environment where this needs consideration every time).


Reproducible: Always
Comment 1 cluelesscoder 2018-02-12 06:42:39 UTC
This is actually a feature request, not a bug...