SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There are no errors during the compilation and no error messages while using. But there is a big trouble while I login with the NX client:
After I login to my KDE4 desktop, no matter what I do, the screen would freeze immediately. And then the connection would be broken (NX client said server has no response).
I don't know what's going wrong, is there anyone successful installing freenx for logining to KDE4 desktop?
BTW, I've tried the tightvnc coming with the 13.0 release, but the quality of the remote KDE screen is ugly, even setting the lowest compression ratio.
I think (but i'm only guessing) that there's some problem with starting the kde session: you can try it selecting in your nx client another kind of session for that host.
in the official nomachine client you can do that by going in "configure", select "custom" in the desktop session selection and then select "run the following command", putting as command argument "xterm", and "new virtual desktop". save and connect.
connecting to the server should run a simple xterm full screen from where you can even "startkde" and eventually look at errors.
you can also enable logging for nx in /etc/nxserver/node.conf setting two variables
Code:
NX_LOG_LEVEL=6
NX_LOGFILE=/tmp/nxserver.log
I'm making you log in /tmp because it looks logging is done as the user nx and it does not have write permission in /var/log
if you want it to log there you have to "mkdir /var/log/nx; chown -R nx /var/log/nx" and edit node.conf to log in /var/log/nx/nxserver.log
then restart the freenx server with "/etc/rc.d/rc.freenx stop; /etc/rc.d/rc.freenx start"
just for curiosity:
- which video driver are you using in your client?
- have you tried also connecting from another pc (you can also from windows/mac)?
P.S. if someone is willing to try them, I built for me on a clean slack64 the updated versions of nx components (got 'em here) with alien slackbuilds, and it looks they're working fine: packages (also server one, but that's basically the same) are 1 and 2 here you can find updated slackbuilds and sources (preconfigured for 32bit)
I'm sure that there are no problems on my client side, because I can connect to the other nxservers (on Slackware 12.2) with it.
My sys/configuration of my client side is the following:
- Microsoft Windows XP with Service Pack 3
- ATI Mobility Radeon X600, using Radeon Omega Driver v4.8.442 (not official driver)
The sys/configuration of the two nxservers (which can be successfully connected)
- Slackware Linux 12.2 (up-to-date)
- (MAYBE) Intel Graphical Chipset, vesa driver
- KDE 3.5.10
The sys/configuration of the one which would disconnect while using KDE
- Slackware Linux 13.0 (clean-installation)
- NVIDIA GeForce 6200, using NVIDIA DISPLAY DRIVER-x86 version 185.18.36 (released on 2009.8.21)
- KDE 4.2.4
I'll go on finding what goes wrong by watching the log files, thanks for your advices.
-- NX SERVER START: -c /usr/bin/nxserver - ORIG_COMMAND=
-- NX SERVER START: - ORIG_COMMAND=
Info: Using fds #4 and #3 for communication with nxnode.
HELLO NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: user1
NX> 102 Password:
Info: Auth method: ssh user1@127.0.0.1's password:
NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 716 Slave mode started successfully.
nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
nxnode_reader: NX> 716 finished
nxnode_reader: NX> 1001 Bye.
NX> 103 Welcome to: localhost user: user1
NX> 105 listsession --user="user1" --status="suspended,running" --geometry="1280x768x32+render" --type="unix-kde"
NX> 127 Sessions list of user 'user1' for reconnect:
Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
NX> 148 Server capacity: not reached for user: user1
NX> 105 startsession --link="wan" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="localhost.pas.csie.ntu" --type="unix-kde" --geometry="1280x740" --client="winnt" --keyboard="pc102/us" --screeninfo="1280x740x32+render"
still absolutely not sure if related, but: if you have an ~/.xinitrc in the home of the user you're trying to connect, rename it and try to connect again.
had to do it now for one machine I was trying to connect with a user i never connected with nx (one user, the usual, with no .xinitrc, let me in, another one no dropping connection).
btw, you probably already know, you can check if everything is working server-side with
Code:
nxsetup --test
if you copied/moved keys to a different machine/installation be sure to remove known_hosts file from /var/lib/nxserver/home/.ssh to let it reload the new localhost key.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
