<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Ok - I think we have finally found a solution.<BR><BR>
I searched the internet for the warning message I mentioned earlier<BR>
"<FONT color=#17365d>Cannot open ConsoleKit session: Unable to open session: Failed to execute program</FONT><BR><FONT color=#17365d>/lib/dbus-1.0/dbus-daemon-launch-helper: Success."</FONT><BR><BR>
Other users have also seen this problem and it appears to be related to another issue:-<BR>
If you try and access the "Users & Groups" or the "Time & Date" configuration menus, then a message "The configuration could not be loaded" appears. See <A href="http://ubuntuforums.org/showthread.php?t=1022421">http://ubuntuforums.org/showthread.php?t=1022421</A><BR>
We also saw these problem on the cloned PC.<BR>
<BR>
I was unable to find a solution to the above so I decided to try ugrading to all the latest packages on the cloned machine.<BR>
Unfortunately after doing this, the PC would no longer boot into KDE!<BR>
We eventually discovered the contents of /usr/X11/default-display-manager were incorrect:-<BR>
It contained "/opt/kde3/bin/kdm" but should have been "/usr/bin/kdm". (we don't have kde 3 installed).<BR>
I can only think that the file was changed as part of the package upgrades.<BR>
<BR>
After correcting this issue and rebooting, everything now works as it should:-<BR>
The ConsoleKit warning no longer appears.<BR>
The "Users & Groups" and "Time & Date" menus now work without the "The configuration could not be loaded" message.<BR>
NX now connects properly and runs KDE.<BR>
<BR>
I am still unsure why we did not see the problems on the original PC we cloned the disk from.<BR>
My suspicion is that the fault is timing related and that slight differences in the hardware on the two machines caused one to hit the problem.<BR>
<BR>
Thanks to all for the replies while trying to crack this.<BR>
<BR>
Brian.<BR>
<HR id=stopSpelling>
To: freenx-knx@kde.org<BR>From: chris@ccburton.com<BR>Date: Tue, 28 Sep 2010 13:39:04 +0100<BR>Subject: [FreeNX-kNX] Re: freenx server + NoMachine client - black window after disk clone<BR><BR><BR><TT><FONT size=2>Brian Keen <brian_mk@hotmail.co.uk> wrote on 28/09/2010 07:56:14:<BR><BR>> Some more clues...<BR>> <BR>> 1) We tried re-cloning the hard disk from the original PC just to be<BR>> sure that the first clone attempt was not corrupt in some way.<BR>> This fails in the same way.<BR></FONT></TT><BR><TT><FONT size=2>Did you fsck after cloning ??</FONT></TT> <BR><BR><TT><FONT size=2>You could try creating a new user on the clone and seeing if that</FONT></TT> <BR><TT><FONT size=2>account has the same problem.</FONT></TT> <BR><BR><TT><FONT size=2>> <BR>> 2) If I configure the NoMachine client to use XDM instead of KDE, <BR>> then I get a console window inside an X window.<BR>> From the console window, I can successfully start KDE by executing 'startkde'.<BR>> (We should be able to use this as a temporary workaround until a fixis found).<BR>> <BR></FONT></TT><BR><TT><FONT size=2>I can't quite see why the agent would be segfaulting.</FONT></TT> <BR><BR><TT><FONT size=2>You say you re-installed the</FONT></TT> <BR><TT><FONT size=2> NX libraries (which supply nxagent)</FONT></TT> <BR><TT><FONT size=2>on the server ??</FONT></TT> <BR><BR><BR><BR><TT><FONT size=2>If you log into the server locally, start a terminal session and run</FONT></TT> <BR><TT><FONT size=2> nxagent :2001</FONT></TT> <BR><TT><FONT size=2>then in another terminal</FONT></TT> <BR><TT><FONT size=2> su -l to-a-different-user-account</FONT></TT> <BR><TT><FONT size=2>and run</FONT></TT> <BR><TT><FONT size=2> export DISPLAY=:2001</FONT></TT> <BR><TT><FONT size=2> startkde</FONT></TT> <BR><TT><FONT size=2>you will get a minimalist nxagent session (with lots of kde</FONT></TT> <BR><TT><FONT size=2>status in the another teminal session)</FONT></TT> <BR><BR><TT><FONT size=2>See if the agent falls over.</FONT></TT> <BR><BR><BR><BR><BR><BR><BR><BR><BR><BR>________________________________________________________________ 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@kde.org https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________ </body>
</html>