No subject

Fri Jan 17 03:57:02 UTC 2014

kde'.

(We should be able to use this as a temporary workaround until a fix is fou=
nd).

=20

3) I'm not sure if this is significant but when I reboot the PC that exhibi=
ts the problem=2C I get the following warning message in a pop-up window:-

=20

"Cannot open ConsoleKit session: Unable to open session: Failed to execute =
program

/lib/dbus-1.0/dbus-daemon-launch-helper: Success."

=20

I do not get this message when I boot the machine from which the disk was c=
loned.

=20

From: brian_mk at hotmail.co.uk
To: freenx-knx at kde.org
Date: Mon=2C 27 Sep 2010 17:29:41 +0100
Subject: [FreeNX-kNX] Re: freenx server + NoMachine client - black window a=
fter disk clone

OK=2C I tried nxagent :2001 from an NX console.
=20
I get a black xterm window and the following messages in the NX console win=
dow:-
=20
ffei at pcctp4:~$ nxagent :2001
NXAGENT - Version 3.4.0
Copyright (C) 2001=2C 2010 NoMachine.
See http://www.nomachine.com/ for more information.
Info: Agent running with pid '27751'.
Session: Starting session at 'Mon Sep 27 17:25:24 2010'.
Info: Using alpha channel in render extension.
Info: Using local device configuration changes.
InitOutput: Locale en_GB.UTF-8 not supported by X
InitOutput: cannot set locale modifiers.
SessionPath not defined
Session: Session started at 'Mon Sep 27 17:25:24 2010'.
Info: Screen [0] resized to geometry [1280x1002] fullscreen [1].

=20

To: freenx-knx at kde.org
From: chris at ccburton.com
Date: Mon=2C 27 Sep 2010 11:14:33 +0100
Subject: [FreeNX-kNX] Re: freenx server + NoMachine client - black window a=
fter disk clone

Brian Keen <brian_mk at hotmail.co.uk> wrote on 27/09/2010 10:37:55:

[SNIP]=20
> Session: Session started at 'Mon Sep 27 10:04:26 2010'.
> nxagentExportProperty: WARNING! Failed to look up window 0 exporting
> property _NET_ACTIVE_WINDOW type WINDOW on window 0x28897c0.
> c-60-iso10646-1
> xterm:  fatal IO error 11 (Resource temporarily unavailable) or=20
> KillClient on X server ":2001.0"

This NX server is a clone right ?? Try fscking the NX server.=20

Start a local terminal session on the NX server and run=20

/wherever/it/is/nxagent :2001=20

See if you get any errors messages in the terminal window.=20

________________________________________________________________ Were you h=
elped on this list with your FreeNX problem? Then please write up the solut=
ion in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/B=
erliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: htt=
p://www.nomachine.com/kb/ _________________________________________________=
_______________ FreeNX-kNX mailing list --- FreeNX-kNX at kde.org https://mail=
.kde.org/mailman/listinfo/freenx-knx ______________________________________=
__________________________=20
________________________________________________________________ Were you h=
elped on this list with your FreeNX problem? Then please write up the solut=
ion in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/B=
erliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: htt=
p://www.nomachine.com/kb/ _________________________________________________=
_______________ FreeNX-kNX mailing list --- FreeNX-kNX at kde.org https://mail=
.kde.org/mailman/listinfo/freenx-knx ______________________________________=
__________________________ 		 	   		  =

--_e70e07ca-bb3e-49d3-8f19-dc5b69919f7f_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'>
Some more&nbsp=3Bclues...<BR><BR>
1) We tried re-cloning&nbsp=3Bthe hard disk from the original PC just to be=
 sure that the first clone attempt&nbsp=3Bwas not corrupt in some way.<BR>
This fails in the same way.<BR>
&nbsp=3B<BR>
2) If I configure the NoMachine client to use XDM instead of KDE=2C then I =
get a console window inside an X window.<BR>