Users cannot login, xrdb can't open display

[Lukas Bernard]

Users can no longer log in using the free NX server. (while such action was possible only a few days ago, no system upgrade in the meantime). The following is the contents of ~/.nx/sessions log file:

xrdb: No such file or directory
xrdb: Can't open display ':1005'
xrdb: No such file or directory
xrdb: Can't open display ':1005'
2008-09-26 13:50:34,174 dbus.proxies ERROR Introspect error on :1.4:/org/freedesktop/ConsoleKit/Session884: dbus.exceptions.IntrospectionParserException:
xsetroot: unable to open display ':1005'
[: 41: ==: unexpected operator
xset: unable to open display ":1005"
xset: unable to open display ":1005"
xsetroot: unable to open display ':1005'
startkde: Starting up...
ksplash: cannot connect to X server :1005
xprop: unable to open display ':1005'
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kded: cannot connect to X server :1005
DCOP aborting call from 'anonymous-15939' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
kcminit_startup: cannot connect to X server :1005
ksmserver: cannot connect to X server :1005
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
xprop: unable to open display ':1005'
startkde: Done.

System is Ubuntu 8.04 amd64, Free NX 3.2.0-74

[Marcelo Boveto Shima (marceloshima)]

Do you have x11-xserver-utils installed?

If you have, please try to remove freenx-session-launcher and start a session.

[Lukas Bernard (bernard-arcig)]

I have removed the package freenx-session-launcher. However, login is
still not functional with only a minor change in the session log:

xrdb: No such file or directory

xrdb: Can't open display ':1005'

xrdb: No such file or directory

xrdb: Can't open display ':1005'

xsetroot: unable to open display ':1005'

[: 41: ==: unexpected operator

xset: unable to open display ":1005"

xset: unable to open display ":1005"

xsetroot: unable to open display ':1005'

startkde: Starting up...

ksplash: cannot connect to X server :1005

xprop: unable to open display ':1005'

kdeinit: Can't connect to the X Server.

kdeinit: Might not terminate at end of session.

kded: cannot connect to X server :1005

DCOP aborting call from 'anonymous-5767' to 'kded'

kded: ERROR: Communication problem with kded, it probably crashed.

kcminit_startup: cannot connect to X server :1005

ksmserver: cannot connect to X server :1005

startkde: Shutting down...

klauncher: Exiting on signal 1

startkde: Running shutdown scripts...

xprop: unable to open display ':1005'

startkde: Done.

Marcelo Boveto Shima napsal(a):
> Do you have x11-xserver-utils installed?
>
> If you have, please try to remove freenx-session-launcher and start a
> session.
>

[Marcelo Boveto Shima (marceloshima)]

Please post your
/home/profesori/maj/.nx/F-C-gamma-1005-829052F9BABE9BF63B6C2DAFE7231843/session

[Lukas Bernard (bernard-arcig)]

I'm sending requested file.
Lukas Bernard

[Marcelo Boveto Shima (marceloshima)]

Seems that nxagent has not been found, otherwise it would print "NXAGENT -
Version 3.2.0"

1 - "/usr/lib/nx/nxagent" should not exist. nxagent package put nxagent at
/usr/bin/
     If you have it, please remove.
2 - When you execute "$which nxagent" it should print "/usr/bin/nxagent"
3 - Try to purge freenx-* packages, remove every previous installation (ex.
/usr/lib/nx/*)
     and install again

[Lukas Bernard (bernard-arcig)]

I removed all old versions of freenx and purged directory /usr/lib/nx/,
then reinstalled package freenx-server.
Connection is still not functional, session log is shorter (attached).

nxserver.log:

nxnode_reader: NX> 1004 Error: NX Agent exited with exit status 1. To
troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate
"/home/profesori/bernard/.nx/F-C-gamma-1005-D9CB3B3E73223EB04F9F89CE95A61EEC/session".
You might also want to try: ssh -X myserver; /usr/lib/nx/nxnode --agent
to test the basic functionality. Session log follows:
nxnode_reader: /usr/lib/nx/nxnode: line 564: 18714 Terminated
    PATH="$PATH_BIN:$PATH" $COMMAND_NXAGENT $P $R -name "NX -
$user@$SERVER_NAME:$display - $session (GPL Edition)" -option
"$USER_FAKE_HOME/.nx/C-$sess_id/options" $K $G $B $FP
$AGENT_EXTRA_OPTIONS_X :$display 2>&3
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
SESSION_LOG_CLEAN=0 in node.conf and investigate
"/home/profesori/bernard/.nx/F-C-gamma-1005-D9CB3B3E73223EB04F9F89CE95A61EEC/session".
You might also want to try: ssh -X myserver; /usr/lib/nx/nxnode --agent
to test the basic functionality. Session log follows:
/usr/lib/nx/nxnode: line 564: 18714 Terminated
PATH="$PATH_BIN:$PATH" $COMMAND_NXAGENT $P $R -name "NX -
$user@$SERVER_NAME:$display - $sessio(GPL Edition)" -option
"$USER_FAKE_HOME/.nx/C-$sess_id/options" $K $G $B $FP
$AGENT_EXTRA_OPTIONS_X :$display 2>&3
NX> 105 nxnode_reader: xrdb: No such file or directory
nxnode_reader: xrdb: Can't open display ':1005'
nxnode_reader: xrdb: No such file or directory
nxnode_reader: xrdb: Can't open display ':1005'
xrdb: No such file or directory
xrdb: Can't open display ':1005'
xrdb: No such file or directory
xrdb: Can't open display ':1005'
nxnode_reader: NX> 1006 Session status: closed
NX> 1006 Session status: closed
server_nxnode_echo: NX> 596 Session startup failed.
NX> 596 Session startup failed.

[Marcelo Boveto Shima (marceloshima)]

Please execute
$nxloadconfig --help
and post the result.

[Marcelo Boveto Shima (marceloshima)]

Sorry. Wrong command.
$nxloadconfig --check
--check instead of --help

On Tue, Sep 30, 2008 at 10:39 PM, Marcelo Boveto Shima <
<email address hidden>> wrote:

> Please execute
> $nxloadconfig --help
> and post the result.
>

[Lukas Bernard (bernard-arcig)]

I found the error:
Display was blocked by old lock files /tmp/.X1000-lock, /tmp/.nX1000 and
others. After removing them connection is again ready.

Thank for your help.
Lukas Bernard

[Marcelo Boveto Shima (marceloshima)]

Couldn´t make this error happen

[john (jkrstev)]

I'm having the same problem, and no issues with lock files in /tmp

Can anyone offer any suggestions?

[Jeremy Wilkins (wjeremy)]

You have revived an old bug that is likely unrelated to yours. Please file a new bug with the exact description and log files from your computer similar to the ones above. I am replying to this only in courtesy, often most moderators would ignore a short message like this that is made on a two year old bug on a version that isn't even close the the current one. Especially a comment that contains no detail. It may be that others can gain more useful information from a separate bug report like that because it won't water down the details when they are searching for it using a search engine, so others can benefit too.