Timo,

The problem is that the default .policy files for many Ubuntu applications that use PolicyKit are configured badly, as they don't take into account the needs of remotely-connected users who launch desktop sessions.

An Ubuntu bug report with a detailed discussion can be found here: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/221363

This has been an ongoing issue for me, since I have a headless Xubuntu workstation that I only access remotely (via X2go and ssh/sftp).

If you don't want to muck around with .policy files, another workaround is to launch the affected application(s) from the command line with sudo/gksudo.

• Ben S.

On Fri, Mar 16, 2012 at 7:44 AM, Timo <tike64@gmail.com> wrote:

Hi all,

FreeNX seems not to be anymore supported for newer systems (e.g. Oneiric) so I was very glad that I found this X2Go. Thanks for good work!

I got it running after I learned what to put into the session type and edited Wiki with my observation (http://www.x2go.org/doku.php/** wiki:components:x2goclient<http://www.x2go.org/doku.php/wiki:components:x2goclient> ).

There is a couple of small hitches though: The first is a small one; update, audio volume and network applets render a little badly (Mint 12 gnome classic fallback session).

The second is a little more critical; I don't have administration privileges in remote session. For example in Applications->Systems Tools->System Settings->User Accounts there is an Unlock button but it is disabled. So I can't use that tool to manage user accounts remotely. I don't know where to start to look at this problem.

--

Timo ______________________________**_________________ X2Go-User mailing list X2Go-User@lists.berlios.de https://lists.berlios.de/**mailman/listinfo/x2go-user<https://lists.berlios.de/mailman/listinfo/x2go-user>