From: Martin Honermeyer (maze_at_strahlungsfrei.de)
Date: Sat 25 Jun 2005 - 16:11:55 BST
(I am cross posting this to the linux-vserver list, as it is of interest to
those people, too.)
many thanks!! I got it working!!! This is what I did:
* Deleted everything from /tmp.
* Tried to login again => same problem, window closes after a few seconds
* looked at the user's .xsession-errors file:
_IceTransmkdir: ERROR: Owner of /tmp/.ICE-unix must be set to root
_IceTransSocketUNIXCreateListener: mkdir(/tmp/.ICE-unix) failed, errno = 1
_IceTransMakeAllCOTSServerListeners: failed to create listener for local
* So I looked into /tmp. The directory .ICE-unix was already there, the
owner set to my user.
* So I did:
$ chown root /tmp/.ICE-unix
$ chown root /tmp/.X11-unix
* Login => works and runs like a shot!!! :-)
Note: I have to re-run those two commands every time I reboot the VServer.
It seems like starting an X-Server from within FreeNX doesn't set up those
permissions in /tmp correctly. Maybe that's because I don't have something
like KDM run beforehand.
VServer configuration: I didn't have to enable any additional capabilities!
Pablo A. Salgado wrote:
> Some time ago I tried to do the same and ran into troubles.
> First, I found no way to start xterm as normal user into vserver because
> some kind of problem with /dev/tty* into the vserver (the message was
> something like: "I couldn't create tty#"). The only user that could start
> xterm was root. That means that it seems to be posible to execute KDE as
> normal user but not xterm. Anyway I didn't find any documentation about
> this topic.
> Then, I installed freenx in the host system and run into the problem you
> describe starting KDE as normal user. After few attempts to start sessions
> I decided to erase any related KDE file in the /tmp directory and voilà!
> it worked. Perhaps it could help you.
> Let me know if you success running NXserver into vserver :)
> On 6/30/05, Martin Honermeyer <maze_at_strahlungsfrei.de> wrote:
>> I am trying to get an NXServer running inside a Linux VServer
>> (www.linux-vserver.org <http://www.linux-vserver.org>). It works as far
>> as this: KDE is starting, then the
>> splash screen says "initializing system devices" and pow! the session
>> just closes. It seems not to happen exactly at this point, but after the
>> is running for a few seconds. No errors in the nxserver log, no .xsession
>> file in the user home (it should be there??).
>> As the capabilities inside the VServer are very restricted, I need some
>> advice from the NX devs about which system capabilities are needed in
>> to get an NXserver running. A list is at
>> I am using the newest FreeNX 0.4.1 and the free NXServer components 1.5.0
>> r3. The problem was the same with FreeNX 0.2.8 and NXServer components
>> If there are direct suggestions for a solution, at least I'd like to know
>> how to get some more verbose log output! NX_LOG_LEVEL=7 doesn't tell
>> NX> 1000 NXNODE - Version 1.4.0-04-CVS OS (GPL)
>> NX> 700 Session id: nx32-1004-A2499FCF6F24DE826CBD8940338E63D3
>> NX> 705 Session display: 1004
>> NX> 703 Session type: unix-kde
>> NX> 701 Proxy cookie: a9588103ea86b8550176359e4255a222
>> NX> 702 Proxy IP: 220.127.116.11 <http://18.104.22.168>
>> NX> 706 Agent cookie: bd1745d567d62cf63fbdbbaee2ecdcb5
>> NX> 704 Session cache: unix-kde
>> NX> 707 SSL tunneling: 0
>> NX> 710 Session status: running
>> NX> 1002 Commit
>> NX> 1006 Session status: running
>> NX> 105 bye
>> NX> 999 Bye
>> NX> 1001 Bye.
>> NX> 105 quit
>> NX> 1009 Session status: terminating
>> NX> 1006 Session status: closed
>> (Btw, SSL encryption doesn't work at all. The client times out at
>> "Negotiating link parameters".
>> Thanks for any help. It would be REALLY great to have this running!
>> FreeNX-kNX mailing list
Vserver mailing list