On Sex, 2012-06-08 at 11:34 -0600, Kevin Fenzi wrote:
On Fri, 08 Jun 2012 12:52:30 +0100
Sérgio Basto <sergio(a)serjux.com> wrote:
> Help !
> -------- Forwarded Message --------
>
> me: I see, that we got this active=no (or =FALSE) problem with other
> cases me: like my remote server, where I need to work with vnc .
>
> Kevin: VNC has always been considered a remote session and thus not
> eligible for Kevin: active session ACLs. See e.g.:
> Kevin:
https://bugzilla.redhat.com/show_bug.cgi?id=711719
> Kevin: (where the bug isn't really that ACLs aren't given out, but
> that the printer- Kevin: applet reacts to it with an uncaught Python
> exception).
>
> me: Hi, many thanks for your reply ! ,
> me: Well how put my vnc with active ACLs ? I need it . ( I have root
> on me: machine :) )
VNC simply doesn't get the same acls as a local session.
I'm not sure what action you are looking for here.
VNC have same ACLs as a local session.
I suppose someone could write up how to get polkit
Yes, that is what I'm looking for, someone help me out ?
to do that, but as
noted in the bug that may not be a very safe mode to run.
(Then your remote vnc user could access things like webcams,
microphones, etc).
Yes, I know and I understand is correct as default behavior, as
workaround I also could start a KDE session as root (allowing root start
sessions in kdm.conf), but I would prefer use my user configurations.
Thanks,
--
Sérgio M. B.