Forum / NoMachine for Linux / NoMachine refuses to re-attach to physical session
- This topic has 22 replies, 5 voices, and was last updated 4 years, 7 months ago by Britgirl.
July 13, 2018 at 08:27 #18999
Finally able to retest today.
Yesterday was physically on site, performed various OS updates, rebooted, and confirmed that there is a physical session initiated from the physical keyboard. (used the system all day)
Today attempted to remote, and the UI connects, however:
1. never gives me the option to “create a display”
2. never shows that there is an “existing display” to connect to
Let it sit there for a few minutes, nothing. Checked the server logs and it was spewing all sorts of stuff in a loop. (sending logs via e-mail)July 13, 2018 at 09:25 #19008
Logs received 🙂July 25, 2018 at 11:14 #19113brotechParticipant
Sorry for the delay in replying, I thought we had already replied with the workaround.
The problem you experience might be related to your recent OS updates, in particular to krb5-workstation package.
We suspect that it’s:
The problem was solved in our test environment by downgrading krb5-workstation
Version : 1.15.2
Release : 9.fc27
Version : 1.15.2
Release : 2.fc27July 26, 2018 at 08:26 #19129
Indeed, my system has a newer version of this.
$ rpm -qa | grep krb5-workstation
Come to think of it, it’s possible that it aligns with the system upgrade from Fedora26 -> Fedora27 (I think I noticed the problem much later post-upgrade, so the correlation did not come to mind).
That problem report linked seems quite light-weight. Is NoMachine planning to update it with more information + workaround + ETA for resolution?July 26, 2018 at 15:13 #19147CatoParticipant
The solution for the problem will be part of next NoMachine official release, which should come out in the next two-three months. Our advice to users experiencing the issue is to downgrade krb5-workstation packages for now.August 24, 2018 at 09:45 #19406
Status doesn’t really make sense.
I was already running 6.0.X version, and the KB says:
Added on: 2018-07-11
Last update: 2018-08-23
Due to be solved in: 6.0
What target release is it going to be fixed it?
It says last updated today, but I do not see any differences.August 24, 2018 at 10:10 #19411
@fermulator, a modification can occur for any number of reasons – from a typo to the closure/implementation. This is the general rule of our KB entries (articles, docs, FR and TR). It’s an indication of freshness.
In the case of this TR, its internal status has changed, for the developers. Showing the modified date could be misleading in the case where there is no visible change to the customer. I’ll bring it up with the web team and see what improvements can be made.
As for the release date, Cato gave an indication in his last reply just above.October 19, 2018 at 14:50 #20079
Make sure you update to the latest 6.3.6 as it includes the patch for TR07P08710.
This topic was marked as solved, you can't post.