FS#5737 - Freenx times out to a screensaver very quickly

Attached to Project: Arch Linux
Opened by Glyn Adgie (glyn) - Thursday, 02 November 2006, 13:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Freenx has recently started behaving wierdly. When you log in to a recently-updated machine, the KDE desktop comes up as normal. If you then start using the session, there appears to be a very rapid inactivity timeout (a fraction of a second), then a simple screensaver appears, with an X logo jumping around. This makes the system unusable. The bug has been reported by someone else on the Freenx mailing list: http://mail.kde.org/pipermail/freenx-knx/2006-November/004248.html.

The problem appears to be on the remote machines. I do not think it is a Freenx update that did it, because machines that still work have the same version as the updated machines that fail. Perhaps it is SSH, KDE, or X libraries, as there were updates to those on the affected machines.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 05 November 2006, 07:20 GMT
Reason for closing:  Fixed
Comment by Glyn Adgie (glyn) - Thursday, 02 November 2006, 15:34 GMT
The same thing happens when I connect from a Windows XP machine, using the free NX client for Windows from Nomachine.
Comment by Glyn Adgie (glyn) - Friday, 03 November 2006, 09:15 GMT
The problem seems to be KDE, which was updated on the machines that do not work with freenx. I installed a basic Gnome desktop on the remote machine, and started an NX session using Gnome instead of KDE as the remote desktop. This did not time out.
Comment by Glyn Adgie (glyn) - Friday, 03 November 2006, 16:44 GMT
It is definitely KDE. Machines running KDE 3.5.5 do not work with Freenx.

Reverting to an older version (3.5.4) on the remote machine made Freenx work. The reversion was done by making a tar archive of /opt/kde on a working machine, renaming the /opt/kde on the target machine, then unpacking the archive on the target machine.
Comment by David Baylis (castro) - Saturday, 04 November 2006, 19:34 GMT
The problem seems to be fixed with the new version of nxserver 2.1.0

Loading...