[FreeNX-kNX] blank screen issue
Aidan Marks
aidan at cisco.com
Sat Jul 26 22:21:43 UTC 2008
Hi Alastair,
(sorry i wasn't on the mailing list, i now am, apologies for messing up
the thread, copied from the archive).
see inline.
Aidan Marks wrote:
> Hi
>
> gentoo hardened server with nx-3.2.0-r3, nxserver-freenx-0.7.2-r2,
> xorg-server-1.4.2, kde 4.0.5
>
> gentoo laptop client, nxclient-3.2.0.13
Desktop profile with xorg-server-1.3.0.0-r6 here, but not too dissimilar
> client sees a blank screen after the !m. this used to work fine, can't
> pinpoint the regression.
>
> startx on the server locally starts kde fine.
What does it do with startkde, or whatever COMMAND_START_KDE is set to
if it isn't the default?
I have nxclient set to start unix-kde. COMMAND_START_KDE is the default
and not set.
my .xinitrc is simply exec startkde. hence startx on the console is
fine, I do not use kdm.
> session log:
>
> NXAGENT - Version 3.2.0
>
> Copyright (C) 2001, 2007 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Agent running with pid '4413'.
> Session: Starting session at 'Fri Jul 11 09:24:06 2008'.
> Info: Proxy running in server mode with pid '4413'.
> Info: Waiting for connection from '127.0.0.1' on port '5000'.
> Info: Accepted connection from '127.0.0.1'.
> Info: Connection with remote proxy completed.
> Info: Using LAN link parameters 1536/24/1/0.
> Info: Using agent parameters 5000/0/50/0/0.
> Info: Using pack method 'adaptive-9' with session 'unix-kde'.
> Info: Not using NX delta compression.
> Info: Not using ZLIB data compression.
> Info: Not using ZLIB stream compression.
> Info: Not using a persistent cache.
> Info: Listening to X11 connections on display ':1000'.
> Info: Established X client connection.
> Info: Using shared memory parameters 1/1/1/2048K.
> Info: Using alpha channel in render extension.
> Info: Not using local device configuration changes.
> Session: Session started at 'Fri Jul 11 09:24:09 2008'.
> Info: Screen [0] resized to geometry [1016x706].
> Session: Terminating session at 'Fri Jul 11 09:26:05 2008'.
X just terminated. Check the session errors file. If there's nothing
there then it thinks your X session terminated cleanly. It may be worth
setting the log level to maximum (7?) as it might log something useful.
yes the ~/.nx/T-C*/errors file is empty. I already have NX_LOG_LEVEL=7 set.
just this in the session log:
Session: Session started at 'Sun Jul 27 08:07:43 2008'.
Info: Screen [0] resized to geometry [1016x706].
xrdb: Connection refused
xrdb: Can't open display ':1000'
xsetroot: unable to open display ':1000'
xrdb: Connection refused
xrdb: Can't open display ':1000'
xset: unable to open display ":1000"
xset: unable to open display ":1000"
xset: unable to open display ":1000"
xsetroot: unable to open display ':1000'
startkde: Starting up...
xprop: unable to open display ':1000'
how do i debug why X is terminating? how do you see what nxagent is doing?
the nxserver.log seems uninteresting:
-- NX SERVER START: - ORIG_COMMAND=
HELLO NXSERVER - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
NX> 105 hello NXCLIENT - Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: amarks
NX> 102 Password:
Info: Auth method: ssh
NX> 103 Welcome to: wumpyr user: amarks
NX> 105 listsession --user="amarks" --status="suspended,running"
--geometry="1024x768x24+render" --type="unix-kde"
NX> 127 Sessions list of user 'amarks' for reconnect:
Display Type Session ID Options Depth
Screen Status Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------
NX> 148 Server capacity: not reached for user: amarks
NX> 105 startsession --link="lan" --backingstore="1" --encryption="1"
--cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
--composite="1" --media="0" --session="wumpyrl" --type="unix-kde"
--geometry="1024x737" --client="linux" --keyboard="pc105/us"
--screeninfo="1024x737x24+render"
&link=lan&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&media=0&session=wumpyrl&type=unix-kde&geometry=1024x737&client=linux&keyboard=pc105/us&screeninfo=1024x737x24+render&clientproto=2.1.0&user=amarks&userip=192.168.0.58&uniqueid=589D1BD03D008210DC4ECACC0A1A0639&display=1000&host=127.0.0.1
Password:
NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
server_nxnode_echo: NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using
backend: 3.2.0)
NX> 700 Session id: wumpyr-1000-589D1BD03D008210DC4ECACC0A1A0639
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 81f724b9573145335b3d7f158f2e6cd4
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 81f724b9573145335b3d7f158f2e6cd4
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
server_nxnode_echo: NX> 700 Session id:
wumpyr-1000-589D1BD03D008210DC4ECACC0A1A0639
server_nxnode_echo: NX> 705 Session display: 1000
server_nxnode_echo: NX> 703 Session type: unix-kde
server_nxnode_echo: NX> 701 Proxy cookie: 81f724b9573145335b3d7f158f2e6cd4
server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
server_nxnode_echo: NX> 706 Agent cookie: 81f724b9573145335b3d7f158f2e6cd4
server_nxnode_echo: NX> 704 Session cache: unix-kde
server_nxnode_echo: NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
server_nxnode_echo: NX> 1009 Session status: starting
NX> 710 Session status: running
server_nxnode_echo: NX> 710 Session status: running
NX> 1002 Commit
server_nxnode_echo: NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 session_status 589D1BD03D008210DC4ECACC0A1A0639 Running
server_nxnode_echo: NX> 1006 Session status: running
bye
Bye
NX> 999 Bye
NX> 1009 Session status: terminating
session_status 589D1BD03D008210DC4ECACC0A1A0639 Terminating
server_nxnode_echo: NX> 1009 Session status: terminating
NX> 1006 Session status: closed
session_close 589D1BD03D008210DC4ECACC0A1A0639
server_nxnode_echo: NX> 1006 Session status: closed
NX> 1001 Bye.
server_nxnode_echo: NX> 1001 Bye.
More information about the FreeNX-kNX
mailing list