Fransis

[Fransis]

I have not tried gnome shell 3, but use cinnamon in different distros ” LMDE , debian testing, archlinux ” and cinnamon also freezes. If I work from the kde environment I do not have any problems , I can spend hours working remotely perfectly.

But if I start with cinnamon environment, just five minutes I’m working I’m 30 minutes, I do not get it.

I’ve tried different versions of cinnamon ( 2.0.16 , 2.2.4 and 2.2.5 new ) and all I just have the same problem .

I’m using the latest version of NoMachine 4.4.6 on both computers.

So if you say that gnome shell users have the same problem , cinnamon is a fork of gnome shell , so it seems to be a problem between NoMachine and gnome shell .

Thank You

[Fransis]

in the guide does not come any mail address . so is that I share on here.

I attached the log here “server ” .

this afternoon will activate the log of the “client ” .

of course , I’m using the latest version “27” on all my computers.

Thank you

Attachments:

1. logNXerror.tar.gz

[Fransis]

Rescuing the topic:
first apologize for the language, if something is not well understood, is the translator of google.
NoMachine I have been using since version 4.2.25 and 4.2.27 currently, I have more or less the same problem and searching the internet I found forums in 2012 describing exactly the same problem.

Really, my problem is that the graphical environment is frozen, can disconnect from the remote machine and re-connect without problems, equipment and service NX continue to respond correctly, the environment becomes unresponsive.

I’m currently using debian testing environment with cinnamon.
case problem was I tried graphical environment matte and xfce and also has happened to me.

case was the system, I come from very different test configurations as “antergos (archlinux)“
“Manjaro (archlinux)“
“LMDE (debian)“
“linux mint (debian / ubuntu)“
“solydXK (debian)
and probably some other I forget, different operating systems, with different kernels and different desktop environments with one thing in common, “NoMachine“.

so is that if I can, after 1000 go crazy and try different configurations and search the internet, confirm that the problem is triggered by “NX Nomachine“. It is a problem that does not always happen, maybe I can be an entire morning working remotely without any freezing, or other day, I just connect and after 2 minutes the environment freezes, I can move the mouse, and if pressure “ctrl + alt + f2 “I switch to restart the computer terminal. but it is very annoying.

I really like the performance NoMachine, and in spite of having purchased license teamviewer, I like that the application is native to linux NoMachine unlike the botched teamviewer requiring wine, and ease of NoMachine on a package as “deb or rpm “. but if you do not fix it I see I changed to look for other solutions.

Please tell me how I can help to try to solve this problem.

[Author]

Posts