[FreeNX-kNX] Initial config problem - login denied

Mon Dec 15 21:30:48 UTC 2008

me again

Just in case anyone has the same problem(s).

Add gnome-panel to the list below and you should be ok

;)

alex

From: Marcelo Boveto Shima [mailto:marceloshima at gmail.com] 
Sent: lundi 15 décembre 2008 13:46
To: Alexandre Takacs; User Support for FreeNX Server and kNX Client
Subject: Re: [FreeNX-kNX] Initial config problem - login denied

Really... This could take too long. Install the packages: xorg and
gnome-session
and then you should have a working nx server. This will take some unneeded
deps,
but should work.

Or you can use FreeNX from freenx-team PPA instead of NX Server from
NoMachine. Then you can blame me for the missing deps, and I will fix it for
you.

Regards,
Shima

On Sun, Dec 14, 2008 at 7:33 PM, Alexandre Takacs <admin at atc.ch> wrote:

Hello

Many thanks for your help. I'm now getting a little bit further but still no
show... :(

Not sure where to look to further debug this...

DEBUG: Calling handler function: 'saveAgentPid' for 'save pid and uid of the
agent' event 'NXNodeExec::__onMessageRun'
Dec 14 22:16:09 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: Handler function
finished 'NXNodeExec::__onMessageRun'
Dec 14 22:16:09 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: received data in out
channel from NX Node: '\n' (NXNodeExec). Stored status. 'Logger::statusPush'
Dec 14 22:16:09 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: No registered
handler function for message: '988' 'NXNodeExec::__onMessageRun'
Dec 14 22:16:11 sd-16733 NXNODE-3.3.0-3[2949]: ERROR: run command: process:
2959 finished with: 127 Logger::log nxnode 3851
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: Read 43 byte/s from
nxssh stderr: [NX> 290 Failed read on channel descriptor^M\n]
'NXShell::handler_bye'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: Read 43 byte/s from
nxssh stderr: [NX> 280 Exiting from the server side loop^M\n]
'NXShell::handler_bye'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: Closed nxssh stdout:
nxssh is exiting ... 'NXShell::handler_bye'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: Closed nxssh stderr:
nxssh is exiting ... 'NXShell::handler_bye'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: waiting process:
with pid '2946' 'WaitProcess::waitProcess'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: waiting process:

using 5s as timeout 'WaitProcess::waitProcess'

Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: process with pid
'2946' has exited 'WaitProcess::waitProcess'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: process exit status
is '0' 'WaitProcess::getExitStatus'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2893]: DEBUG: nxssh finished
'NXShell::handler_bye'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: received data in out
channel from NX Node: 'NX> 1009 Session status: terminating\n' (NXNodeExec).
Stored status. 'Logger::statusPush'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: Calling handler
function: 'NXShell::nxsessionSetStatus' for message: 1009
'NXNodeExec::__onMessageRun'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: Setting status to
'Terminating' on session id: CDC8A7A6EAD376BE185C5BD37C3B4254
'NXShell::nxsessionSetStatus'
Dec 14 22:16:14 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: Handler function
finished 'NXNodeExec::__onMessageRun'
Dec 14 22:16:15 sd-16733 NXNODE-3.3.0-3[2915]: Session 'unix-gnome' on port
'1012' closed. Logger::log nxnode 6340
Dec 14 22:16:15 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: received data in out
channel from NX Node: 'NX> 710 Session status: Session on display '1012'
finished\nNX> 1001 Bye.\n' (NXNodeExec). Stored status. 'Logger::statusPush'
Dec 14 22:16:15 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: received message
'BYE' from NX Node (NXNodeExec). Stored status. 'Logger::statusPush'
Dec 14 22:16:15 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: closing nxssh's in,

out, err FDs (flagfinished is: 1) (NXNodeExec). Stored status.
'Logger::statusPush'

Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: waiting process:
with pid '2908' 'WaitProcess::waitProcess'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: waiting process:

using 5s as timeout 'WaitProcess::waitProcess'

Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: no process with pid:
'2908' to wait 'WaitProcess::waitProcess'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: Calling handler
function: 'NXUtmp::remove' for 'disconnected from node' event
'NXNodeExec::__onMessageRun'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: NXutmp: logging
disabled. 'NXUtmp::remove'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: Handler function
finished 'NXNodeExec::__onMessageRun'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: connection to NX
Node finished correctly (NXNodeExec). Stored status. 'Logger::statusPush'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: session
sessionId:CDC8A7A6EAD376BE185C5BD37C3B4254 finished
'NXShell::handler_session_start'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: SCRIPTS::
script_before_close_session
[CDC8A7A6EAD376BE185C5BD37C3B4254,alex,localhost,22]
'NXScripts::script_before_close_session'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: DEBUG: SCRIPTS::
script_after_close_session
[CDC8A7A6EAD376BE185C5BD37C3B4254,alex,localhost,22]
'NXScripts::script_after_close_session'
Dec 14 22:16:17 sd-16733 NXSERVER-3.3.0-8[2943]: Session
'CDC8A7A6EAD376BE185C5BD37C3B4254' closed by user 'alex'. 'NXShell::Static'

-----Original Message-----
From: Lars Heiermann [mailto:darmok at junien.org]
Sent: samedi 13 décembre 2008 22:14
To: freenx-knx at kde.org
Subject: Re: [FreeNX-kNX] Initial config problem - login denied

Alexandre Takacs schrieb:

>>> >>> Error: Aborting session with 'Could not open default font 'fixed''.
> >
> > I have tried to google this and I my best guess is that the problem has
> > something to do with X11 not being installed the way it should but I
muss
> > admit that I have no idea how to solve this...

You are missing a font, on Ubuntu installing xfonts-base should help.

Regards,

Lars

________________________________________________________________
    Were you helped on this list with your FreeNX problem?
   Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

        Don't forget to check the NX Knowledge Base:
                http://www.nomachine.com/kb/

________________________________________________________________
      FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
     https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

________________________________________________________________
    Were you helped on this list with your FreeNX problem?
   Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

        Don't forget to check the NX Knowledge Base:
                http://www.nomachine.com/kb/

________________________________________________________________
      FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
     https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20081215/3ec0f541/attachment.html>