On Thu, Sep 13, 2012 at 11:21 AM, Stefan G. Weichinger <email@example.com> wrote:
> Am 13.09.2012 16:19, schrieb Canek Peláez Valdés:
>> The general solution is using something like udisks+polkit.
> I have troubles with that combo for a month or so ... seems as if
> polkit-0.107 somehow is responsible for stuff not mounted here.
> ~amd64 btw, gnome-3-context.
> udisks comes (/is installed) in both slot 0 and 2, correct?
> [i] sys-fs/udisks
> Available versions:
> (0) 1.0.4-r2 (~)1.0.4-r3
> (2) (~)1.99.0 (~)1.99.0-r1
> Does it work for all of you?
It doesn't, but I was under the assumption it was because I'm using
systemd. Since I installed gnome-shell-3.4 this has stopped working;
my findings can be seen on the bug to freedesktop.org:
It hits not only USB mounting; it also hits suspend/hibernate (I'm no
longer allowed to suspend as user), setting up printers, and basically
everything related to polkit. The root of the problem seems to be that
(somehow) gnome-shell gets registered as PolitUnixSession instead of
PolkitUnixProcess or PolkitSystemBusName, and that case is not covered
Could you run polkitd without the --no-debug option (I don't have
OpenRC installed, nor /etc/init.d, so I don't know if that is how it's
run under OpenRC) and see on the logs if you see the following?
olkitbackendjsauthority.c:730:subject_to_js val: code should not be
If so, please state it in the bug. David hasn't answered in three
weeks; two of them he was at the Kernel Summit in San Diego, but I
think it's time for me to nudge him again. An independent report
I'm running GNOME 3 unstable and with my systemd-only overlay, so I'm
used to this kind of things happening from time to time. Also, it has
easy workarounds (pmount, pm-suspend, etc.), so I haven't been really
concerned into fixing it.
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México