Impossible to say what fixed it. qt was updated today. Did a lot of forensics on the NX server trying to fix a dhcp problem - don't see what these could have had to do with it. Rebooted many, many times. When I got home, the client machine took a long time, but, connected... Not much help to others, except, maybe time helps - could have been a lingering lock file from a previous session, or somesuch...

On 12/15/2011 02:31 AM, Claude Jones wrote:
I need any suggestions for diagnosing this problem:
I'm running F16, fully patched up
I run KDE with all the latest 4.7 updates
I run F16 on my server machine at my office as well, also fully patched up
I access the Fedora machine at my office from my home Fedora machine
using NX nomachine and all this has been working extremely reliably for
a long time, through F15 to F16 preupgrades, and through multiple yum
upgrades since
This weekend, system upgrades appear to have broken things:
When I try to connect, I just get a non-helpful message from the NX client:


--
Claude Jones
Brunswick, MD, USA
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to