[FIXED] blueman dbus exception after login

You think you have found a bug? Let us know about it.
Post Reply
User avatar
gapan
Salix Wizard
Posts: 5412
Joined: 6. Jun 2009, 17:40

[FIXED] blueman dbus exception after login

Post by gapan » 6. Aug 2018, 21:20

With the latest blueman package update (currently at blueman-2.0.6-x86_64-1_slack14.2) by Slackware, after logging in, a popup with an Exception caused by DBus is appearing.

If you want to fix this now, you can create a file /etc/polkit-1/rules.d/10-blueman.rules and put these in it:

Code: Select all

polkit.addRule(function(action, subject) {
    if ((action.id == "org.blueman.network.setup" ||
         action.id == "org.blueman.dhcp.client" ||
         action.id == "org.blueman.rfkill.setstate" ||
         action.id == "org.blueman.pppd.pppconnect") &&
        subject.isInGroup("netdev")) {
        return polkit.Result.YES;
    }
});
(I got that from an LQ post)

You can change the "netdev" group in that to any other you want, one that your users are a member of.

Although it seems that PV already knows about this problem and an updated package that fixes it will probably appear sometime during the next few days.
Image
Image

User avatar
gapan
Salix Wizard
Posts: 5412
Joined: 6. Jun 2009, 17:40

Re: [FIXED] blueman dbus exception after login

Post by gapan » 19. Aug 2018, 15:24

Fixed with blueman-2.0.6-x86_64-3_slack14.2.
Image
Image

Post Reply