You are not logged in.
Suddenly every time after startup and login ModemManager ask for my user password, and I'm first on the web when I have type it in..
Anyone know why, and how to avoid it/do it automatically.?
Screenshot: http://db.tt/MqkFsjY4
Offline
You are not alone, here the same.
Offline
Safe this as /etc/polkit-1/rules.d/99-local.rules
polkit.addRule(function(action, subject) {
if (subject.local && subject.active) {
if (action.id == "org.freedesktop.ModemManager1.Device.Control" && subject.isInGroup("users"))
return polkit.Result.YES;
}
});
Offline
Added upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=701740
Offline
Safe this as /etc/polkit-1/rules.d/99-local.rules
polkit.addRule(function(action, subject) { if (subject.local && subject.active) { if (action.id == "org.freedesktop.ModemManager1.Device.Control" && subject.isInGroup("users")) return polkit.Result.YES; } });
Cool, that stop ModemManager to ask for my user password every time..!!
But since some updates a few weeks ago, it also started to ask for SIM PIN every time, and it still do that, and I select 'Automatically unlock this device' every time, but it does not help. Any ideas..? (And yes I need the PIN on the SIM)
Screenshot: http://db.tt/xSESYgH9
Last edited by rxxt (2013-06-11 19:01:32)
Offline
Even though I had a very similar Problem, I had it with ModemManager in connection with NetworkManager on Debian. I found this thread (as so often you find good answers in the arch forums that help for many other distributions ) but the Problem presented differently (and much much more recent - this weekend in fact)
The Pin Dialog would pop up every restart of NetworkManager, saving or applying the Pin would be rejected with an error that the system policy forbids "org.freedesktop.ModemManager1.Device.Control" and nothing else than aborting ended the dialog. Controlling WLAN was not possible anymore either.
I then found out that though NetworkManager could not find a systemd-session for the current user (by stracing NetworkManager - not very accurate). I guess there was a problem running logind properly from X or something like that, since the system was running SysV-Init with logind. Switching to systemd as a startup manager helped but I didn't find out what broke in the first place.
I hope this helps people finding this thread somehow.
Last edited by gibbon_ (2014-05-12 07:34:51)
Offline