Bug 24676 - M7 B3: Blueberry is launched even if bluetooth service is turned off in installation summary
Summary: M7 B3: Blueberry is launched even if bluetooth service is turned off in insta...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: 7beta3
Depends on:
Blocks:
 
Reported: 2019-04-16 10:49 CEST by Dick Gevers
Modified: 2019-08-11 12:07 CEST (History)
1 user (show)

See Also:
Source RPM: M7B3 prerelease round 3 isos
CVE:
Status comment:


Attachments

Description Dick Gevers 2019-04-16 10:49:41 CEST
Description of problem:

My laptop supports bluetooth. It will not sync with my phone so in installation summary I turn of the service. Indeed after reboot ssytemctl status shows bluetooth.service is correctly NOT active.

Yet Blueberry launches on several desktops. That is not logical, the user does not want to Quit it every time...

I for one don't want to see the icon in the panel if service does not run...!

Bugsquad might want to say WONTFIX or UPSTREAM but I am wondering if it launches also if lspcidrake shows no bluetooth device?
Dick Gevers 2019-04-16 10:53:15 CEST

Keywords: (none) => 7beta3

Comment 1 Jani Välimaa 2019-04-16 16:58:44 CEST
Blueberry auto start isn't tied to bluetooth.service, but to DE session auto start apps.

If one wants to disable blueberry from auto starting, it needs to be disabled via session auto start app settings.

Lets say I don't have a network when I'm installing so I turn off the network.service. Does it stop net_applet from auto starting? With this analogy, you should report a bug for every available auto starting app which is using a background service that can be disabled.

CC: (none) => jani.valimaa

Comment 2 Dick Gevers 2019-08-11 12:07:39 CEST
Acc to c1

Resolution: (none) => INVALID
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.