Ralph,

I believe I might be able to help with the admin rights issue, as I ran into it as well and did some digging.

There is an Ubuntu bug report here: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/221363

I think I ended up just replacing all instances of allow_active with allow_any in the policykit policy files, probably by running something like the following commands (make a backup first, though):

    cd /usr/share/polkit-1/actions/
    sudo sed -i 's/allow_active/allow_any//' ./*

On Wed, Nov 2, 2011 at 9:13 AM, Ralph Sikau <r.sikau@parabol-pictures.de> wrote:
Hi,

I have created a fresh Xen domu after all, based on Ubuntu Oneiric with the x2goserver from the Ubuntu PPA. And big surprise, it works: I can suspend and resume gnome sessions correctly.
So I would say, Linux Mint is not a good choice to work with through x2go.
But now I have another strange behaviour: I login via x2go / ssh to a gnome session, using my login name and a private sha key. Within this session I can execute root commands with sudo, but I cannot change any system preferences or modify users and groups within gnome. Obviously I'm lacking admin rights, although I am a member of the admin group.
Might this have to do with LDAP or is the reason somewhere in x2go? Any hints?

Cheers,

Ralph


Am 19.10.2011 21:30, schrieb Mike Gabriel:
Hi,

On Mi 19 Okt 2011 14:34:21 CEST Ralph Sikau wrote:

I'm using the x2goserver (latest version) on a virtual xen machine running an LMDE desktop.
The strange behavior is that the x2go sessions are never resumed but whenever I login, a new session is created and all programs have to be started again.
The client is a Windows XP PC, and it makes no difference whether I use the windows client or the pyhoca gui to connect.
Can anybody tell me what is going wrong here?

please do the following...

1.
Become a watcher on the x2goserver (ssh -l<remote_user> <x2gserver>)...

2.
Then start a session on that server as user <remote_user> (where <remote_user> is to be replaced by the username that you connect to the server with).

3.
From the ssh session run ,,x2golistsessions'' (and if not promiscuous: send the output here).

4.
Suspend the X2go session (describe us how you do that!!!)

5.
From the ssh session run ,,x2golistsessions'' again (and if not promiscuous: send the output here).


Thanks,
Mike 




_______________________________________________
X2go-User mailing list
X2go-User@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-user

--


Parabol Pictures
Sikau, Kohlwey & Pettelkau GbR
Königstraße 76

D-53115 Bonn

Fon +49 228 264858
Fax +49 228 213287

Mail contact@parabol-pictures.de



_______________________________________________
X2go-User mailing list
X2go-User@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-user




--
- Ben S.