Forum Replies Created
I guess the link provides the reason NoMachine need that account, but it doesn’t provide any insight into the issue I have in trying to get filevault up and running. Any ideas about that?
Based on the original post that said the fix was incorporated into subsequent releases, I’ve been using the latest published releases. As I noted in my response to the patch, behavior is much improved over the unpatched version although it still had a couple issues. I’m currently running 6.9.2 – what do you recommend I do at this point?
I’d be happy to provide you with a video, but it’s 2020 already and the TINY 1MB limit on file size attachments isn’t working for me. After recording my screen for about 30 seconds highlighting the issues my video is 80MB. I tried compressing it and got down to 12MB but some of my menu commands now are too blurry to read. Memory so cheap these days so it’s very frustrating to bang into these limits. Do you have an alternate way for me to get you the file.
In other news, I’ve noticed that NoMachine will often disconnect while unattended and start itself up again seconds later. I believe that when that occurs all the covered windows show as blank (or nearly blank) during an expose event. You have to manually select each window to refresh the view so that subsequent expose events show their contents during the expose. Hopefully that’s another clue.
Has anybody been able to confirm this behavior?
So your hint did reveal a dependence on the annoying behavior being exhibited. It turns out I had my mouse tracking speed set to maximum and that did appear to play a role in all this. I’d like to see if you have the same behavior as me. Open up nedit (floating window mode) and make the window big (so that a screen redraw takes a longer time). Copy in about 5-10 pages of text. Here’s where I hope you have a Magic Mouse. To more highlight this problem, set the tracking speed to maximum and now in one action quickly scroll up, down, up, down using long strokes for each swipe and watch the screen redrawing itself. If you see what I see then your screen will be busy redrawing for a while. Now set the tracking speed to something lower and the performance should be much better. That being said, sometimes even at the lower tracking speed I do still see the issue, but just not as often. Again, I don’t recall seeing this issue in OS X Sierra (before upgrading to Mojave).
Thanks for your response graywolf. I didn’t know to mention it earlier, but the primary reason I use NX is because I can display individual linux windows onto my Mac desktop (and manipulate them using Expose etc.). Displaying the linux desktop on my Mac is simply not ever going to be an option for me. The scrolling used to work just fine when my Mac was running Sierra, but ever since I upgraded to Mojave I’ve had this ultra slow scrolling issue through large text files (and also other sluggish redrawing issues). I did try restarting the server with the X11 vector graphics disabled as you suggested (but still using a custom session) and the issue persisted. Still looking for help! 🙁
Thought I’d pass along another observation. If I have a long text file and I scroll through it using my magic mouse by swiping up/down then I believe the swipe action simply transmits a long sequence of e.g. up or down commands to the host. What I see in the window is that each up/down command in that sequence is treated separately i.e. the window receives a down command so the screen contents moves down a little and the full contents redraw. Then it operates on the next down command and another redraw follows etc. etc. A simple swipe can yield a couple minutes of continuous screen redraws where each redraw yields a slightly shifted screen of information. It never used to do that and I’m darned if I can find a way to prevent it. If anybody out there is able to help me I’d really appreciate it! Please!
The server side is running Centos 6.9 and the client side is running OS X Mojave 10.14.6. Pictures of the display settings and connection information are attached.
So just looking for clarification – did all this house cleaning solve your sluggishness issue?October 14, 2019 at 15:13 in reply to: Upgraded from Sierra to Mojave and now get Error is 60: Operation Timed Out #24012
I tried an experiment on Friday before leaving for the weekend and I just came in this morning to find that NX is still up and running. The experiment was to run a program called Amphetamine, which prevents your Mac from going to sleep, and it appears to have worked. So it turns out the problem was with the Mac going to sleep and that somehow those settings were changed/reset when I upgraded OS X. Anyway, I’m back up and running.
That being said, I think it’s worth alerting the user when installing NX that this is an issue and to either instruct the user to alter the preferences or have the installer do it for him/her.October 10, 2019 at 07:08 in reply to: Upgraded from Sierra to Mojave and now get Error is 60: Operation Timed Out #23930
Actually, the time out delay is much smaller than I first thought. I just ducked out for an hour at lunchtime and when I got back it had timed out again :-(.
Well I spoke too soon. While it’s true that the poorly rendered windows are greatly improved in 6.7.6, I did subsequently see a couple windows come up with much of their contents missing that would only reappear if I resized the window. Whatever you did in 6.7.6 – keep doing it, only better!
I am using the Cadence Virtuoso design suite running on my Linux box and displaying the windows back on my Mac. I have attached a screen recording of the issue.
Regarding pixellation – you’re right in that it is a jpeg compression issue. When I look I can see that the jpeg compression is way lower than what I specified. Wouldn’t the right answer to be to look at the user’s preferences upon reconnection (which specify the desired compression) and just do right thing i.e. I’m saying this unexpected behavior is a bug.
Many thanks for your response!
Even though I’m currently connected to a server via NX, there is nothing in my Documents/NoMachine folder :-/. When I disconnect later tonight I’ll see if I can save a connection file there.
I think you have given me enough information to move forward with. I’ll try it out and get back to you within a couple days.