Bug 1432555 - blueman autostarts on gnome logins where it should not
Summary: blueman autostarts on gnome logins where it should not
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: blueman
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-15 16:39 UTC by Kevin Fenzi
Modified: 2018-11-30 20:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 20:47:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Fenzi 2017-03-15 16:39:30 UTC
Gnome has it's own native bluetooth handling, so there's no need to autostart blueman there. Additionally it results in poping up 2 polkit dialogs asking for permissions for rfkill and networking. 

Please consider adding a 
NotShowIn=GNOME;

to /etc/xdg/autostart/blueman.desktop

Thanks.

Comment 1 johan 2017-07-29 09:42:41 UTC
I see many related blueman bugs. Ranging from SELinux denials of DBUS messages. To  oversized exception popups appearing.
The simple workaround for me is to disable 'Blueman Applet' in (Cinnamon) Startup applications.
I even uninstalled blueman, and the Gnome bluetooth stack still seems to work (In my case using bluez / blueberry in cinnamon)

Comment 2 Jan Kurik 2017-08-15 06:37:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 3 Yaakov Selkowitz 2018-02-14 21:19:33 UTC
(In reply to Kevin Fenzi from comment #0)
> Gnome has it's own native bluetooth handling, so there's no need to
> autostart blueman there. Additionally it results in poping up 2 polkit
> dialogs asking for permissions for rfkill and networking. 
> 
> Please consider adding a 
> NotShowIn=GNOME;

NotShowIn=GNOME;KDE;X-Cinnamon;

since Plasma has bluedevil and Cinnamon has blueberry.

Comment 4 Ben Cotton 2018-11-27 16:20:57 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2018-11-30 20:47:30 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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