[FreeNX-kNX] Re: freenx server + NoMachine client - black window after disk clone

[Brian Keen]

Ok - I think we have finally found a solution.


I searched the internet for the warning message I mentioned earlier

"Cannot open ConsoleKit session: Unable to open session: Failed to execute program
/lib/dbus-1.0/dbus-daemon-launch-helper: Success."


Other users have also seen this problem and it appears to be related to another issue:-

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 http://ubuntuforums.org/showthread.php?t=1022421

We also saw these problem on the cloned PC.

 

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.

Unfortunately after doing this, the PC would no longer boot into KDE!

We eventually discovered the contents of /usr/X11/default-display-manager were incorrect:-

It contained "/opt/kde3/bin/kdm" but should have been "/usr/bin/kdm". (we don't have kde 3 installed).

I can only think that the file was changed as part of the package upgrades.

 

After correcting this issue and rebooting, everything now works as it should:-

The ConsoleKit warning no longer appears.

The "Users & Groups" and "Time & Date" menus now work without the "The configuration could not be loaded" message.

NX now connects properly and runs KDE.

 

I am still unsure why we did not see the problems on the original PC we cloned the disk from.

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.

 

Thanks to all for the replies while trying to crack this.

 

Brian.


To: freenx-knx at kde.org
From: chris at ccburton.com
Date: Tue, 28 Sep 2010 13:39:04 +0100
Subject: [FreeNX-kNX] Re: freenx server + NoMachine client - black window after disk clone


Brian Keen <brian_mk at hotmail.co.uk> wrote on 28/09/2010 07:56:14:

> Some more clues...
> 
> 1) We tried re-cloning the hard disk from the original PC just to be
> sure that the first clone attempt was not corrupt in some way.
> This fails in the same way.

Did you fsck after cloning ?? 

You could try creating a new user on the clone and seeing if that 
account has the same problem. 

>  
> 2) If I configure the NoMachine client to use XDM instead of KDE, 
> then I get a console window inside an X window.
> From the console window, I can successfully start KDE by executing 'startkde'.
> (We should be able to use this as a temporary workaround until a fixis found).
>  

I can't quite see why the agent would be segfaulting. 

You say you re-installed the 
                 NX libraries (which supply nxagent) 
on the server ?? 



If you log into the server locally, start a terminal session and run 
         nxagent :2001 
then in another terminal 
        su -l to-a-different-user-account 
and run 
        export DISPLAY=:2001 
        startkde 
you will get a minimalist nxagent session (with lots of kde 
status in the another teminal session) 

See if the agent falls over. 









________________________________________________________________ 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/20100928/43670828/attachment.html>