rowo wroteI had to add rules for "unmount" and "eject" as well:
cat /etc/polkit-1/rules.d/10-udisks.rules
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.udisks2.filesystem-mount" &&
subject.user == "oblive") {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.udisks2.filesystem-unmount" &&
subject.user == "oblive") {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.udisks2.eject-media" &&
subject.user == "oblive") {
return polkit.Result.YES;
}
});
i used this config so i can auto-mount usb storage. it works as expected BUT auto mounting (or at least a sudo confirmation) for local partitions still fails on my end. and so is mounting mtp devices like android.
interesingly, running "dbus-run-session" (learned this when using Void instead of dbus-launch) without having to deal with any polkit rules works directly for usb storage, android, and local partitiions.
my Question is: I've thought that running dbus-session@ <username> was suppose to remedy all the dbus session needs...
current exec line is like this
cmd="exec ck-launch-session dbus-run-session $@ "
additional question: since /lib/66/service/dbus service is already running the daemon, isnt dbus-session@ (username) suppose to run a dbus session instead of another daemon?
