The issue is not Antergos-related. It is present not only in many Arch-based distros, but also n native Arch. It hurts Mate and Plasma here. Cinnamon and Gnome3 are not affected by the issue.
The workaround in brief: install dbus-x11 package from AUR with:
yaourt -S dbus-x11
After that dolphin and systemsettings5 will work with kdesu in Plasma, caja will work with gksu in Mate.
The workaround is not nice. Why?
it installs an AUR package. For the sake of stability, it’s better to avoid to install anything from AUR. Especially packages like dbus, which act at a system level.
dbus-x11 is in conflict with core/dbus package, which must be removed to install dbus-x11. Replacing a core package with another from AUR is a madness.
The workaround is difficult to apply. Why?
dbus-x11 is signed with the 4DE8FF2A63C7CC90 key, which is not in any keyring I use: archlinux-keyring, antergos-keyring, apricity-keyring. Simply speaking, yaourt may refuse to install the package because of unknown public key. If this is the case, just ask - I’ll explain how to add this key to trustdb.
Antergos has another Plasma-specific diffculty. While AUR packages install without a problem in other Antergos flavors, some of them refuse to install in Plasma - apparently because of docbook* -related problems. In this case I build an AUR package in Mate | Cinnamon | Gnome3, and then install it in Plasma. You should be able to build an AUR package in one DE and install it in another. If in need, I’ll explain how to do that.
The workaround is dirty. Why?
The workaround works. Why?
- because everything is possible in Arch
I’ll try to attach the ready-to-use dbus-x11 package, built by yaourt from AUR, here. Not sure whether the forum’s software will allow to upload a binary package in a public place:
If you can download the package, then forget about yaourt-related nightmare described above, and simply install the package with:
sudo pacman -U <path-to-downloaded-package>
Accept dbus package removal during dbus-x11 install.