hchan

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • in reply to: Lagging and weird keyboard strokes #2507
    Avatarhchan
    Participant

    @fra81, thanks for the tip.

    Unfortunately, that lightweight mode mentioned in your link is not for free version of NX 4. I am using the free version…

    in reply to: Lagging and weird keyboard strokes #2488
    Avatarhchan
    Participant

    @drichard, thanks for the tips.

    I just upgraded both client and server to 4.1.29 but I don’t see much improvement…

    Are you running LXDE?

    in reply to: Lagging and weird keyboard strokes #2424
    Avatarhchan
    Participant

    Anyway, since CentOS doesn’t have to LXDE package, so I have to build from sources.

    LXDE has many components: http://sourceforge.net/projects/lxde/files/

    Do you know which LXDE components NX 4 requires to launch IDEs on top of LXDE?

    Thanks!

    in reply to: Lagging and weird keyboard strokes #2374
    Avatarhchan
    Participant

    I think I am the minority (though I am surprised that majority needs to remote back to watch netflix and play video games).

    Anyway, since CentOS doesn’t have to LXDE package, so I have to build from sources.

    LXDE has many components: http://sourceforge.net/projects/lxde/files/

    Do you know which LXDE components NX 4 requires to launch IDEs on top of LXDE?

    Thanks!

    in reply to: Lagging and weird keyboard strokes #2332
    Avatarhchan
    Participant

    Hi Titan,

    Yes, I was comparing NX 4.x to NX 3.5 (sorry that I didn’t copy my original post to my reply so that you won’t miss it).

    Yes, I use NX to remotely connect back to my desktop for development purpose only, and so I don’t care about watching Netflix, doing videoconferencing and videogaming.

    When I upgraded to NX 4.x from 3.5 I didn’t know such a big revamp in NX, otherwise, I would just stick with NX 3.5 (though it is no longer available)….

    I will see whether I can somehow get LXDE on CentOS 6 (currently not available in its official repository)….

    Thanks for your suggestion 🙂

    in reply to: Lagging and weird keyboard strokes #2305
    Avatarhchan
    Participant

    FYI, I upgraded my server and client to 4.1 but I don’t see much latency improvement.

    I don’t do any graphic intensive things…just running IDEs (e.g. Eclipse).

    My server is on CentOS 6.5, and clients are on Windows 7 and CentOS 6.4 if it matters…

    in reply to: Lagging and weird keyboard strokes #2234
    Avatarhchan
    Participant

    In “display settings”, I have disabled “network-adaptive display quality” (this might cause the lag?), “multi-pass display encoding” and “client side image post processing”.

    Not sure whether they are what you refer to.

    in reply to: Authentication Failed? #1881
    Avatarhchan
    Participant

    Graywolf, thanks for your tip.

    I didn’t expect SELinux turned back on after I turned it off long time back.

    Now, I edited /etc/sysconfig/selinux to make it off completely, and it works!

    Thanks!

    in reply to: Authentication Failed? #1609
    Avatarhchan
    Participant

    Thanks for your reply.

    Here is the log:

    Info: Handler with pid 27473 terminated on Mon Jan  6 21:26:52 2014.

    24792 24792 21:37:54 201.416 System/System: WARNING! Child pid 27718 not handled in system at 0x7ff8bb2fa780.

    NX> 900 Session id: 0ED64C30C13C214CC0763D3D303E141A terminated.

    NX> 900 Session id: 52CF01FA3BDA9628769432EC4840C163 terminated.

    NX> 900 Session id: 0ED64C30C13C214CC0763D3D303E141A terminated.

    NX> 900 Session id: 52CF01FA3BDA9628769432EC4840C163 terminated.

    2785 2785 21:39:02 187.407 System/System: WARNING! Child pid 2809 not handled in system at 0x7f002f555780.

    Info: Handler started with pid 2896 on Mon Jan  6 21:39:04 2014.

    Info: Handling connection from 192.168.5.1 port 61510 on Mon Jan  6 21:39:04 2014.

    Info: Connection from 192.168.5.1 port 61510 closed on Mon Jan  6 21:39:34 2014.

    Info: Handler with pid 2896 terminated on Mon Jan  6 21:39:34 2014.

    Info: Handler started with pid 3115 on Mon Jan  6 21:39:35 2014.

    Info: Handling connection from 192.168.5.1 port 45123 on Mon Jan  6 21:39:35 2014.

    Info: Connection from 192.168.5.1 port 45123 closed on Mon Jan  6 21:40:01 2014.

    Info: Handler with pid 3115 terminated on Mon Jan  6 21:40:01 2014.

    Info: Handler started with pid 3135 on Mon Jan  6 21:40:02 2014.

    Info: Handling connection from 192.168.5.1 port 8280 on Mon Jan  6 21:40:02 2014.

    Info: Connection from 192.168.5.1 port 8280 closed on Mon Jan  6 21:40:27 2014.

    Info: Handler with pid 3135 terminated on Mon Jan  6 21:40:27 2014.

    Info: Handler started with pid 3151 on Mon Jan  6 21:40:27 2014.

    Info: Handling connection from 192.168.5.1 port 16468 on Mon Jan  6 21:40:27 2014.

    Info: Connection from 192.168.5.1 port 16468 closed on Mon Jan  6 21:41:47 2014.

    Info: Handler with pid 3151 terminated on Mon Jan  6 21:41:47 2014.

    Info: Handler started with pid 3202 on Mon Jan  6 21:41:48 2014.

    Info: Handling connection from 192.168.5.1 port 20589 on Mon Jan  6 21:41:48 2014.

    Info: Connection from 192.168.5.1 port 20589 closed on Mon Jan  6 21:42:54 2014.

    Info: Handler with pid 3202 terminated on Mon Jan  6 21:42:54 2014.

    Info: Handler started with pid 3220 on Mon Jan  6 21:42:55 2014.

    Info: Handling connection from 192.168.5.1 port 36964 on Mon Jan  6 21:42:55 2014.

     

    Avatarhchan
    Participant

    That explains.

    Thanks!

Viewing 10 posts - 1 through 10 (of 10 total)