© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Thanks. That's interesting actually. Consolekit only lists a single session on this seat (Seat2?), which is not the active one and is not local either. This is why you can't authenticate with PolicyKit.
So, there is no bug in PolicyKit here, as it is behaving exactly as expected.
I have to admit, I'm slightly confused why your session is on Seat2. AFAIK, Seat1 is the local seat for most of us desktop users, and I thought that any VNC session would be on Seat1, seeing as it's basically just transmitting the contents of the local seat across the network.
It would be great if you could describe exactly the steps you take on both the client and server-side to make the VNC connection, so I can try and recreate it here and see if there really is a bug.