Forum Replies Created
-
AuthorPosts
-
graywolfParticipant
Hello stanj.
It looks like your X server started but it is not fully functional because no screen is attached to the video out.
You can try one of the following:
1. Turn display manger and X server off. NoMachine would create its own virtual display server when you try to connect, but you lose the grahics hardware acceleration.
2. Setup the X server to run headless. This guide could be useful: Headless NVIDIA Mini How-TograywolfParticipantAlex, I see that in two cases over three the provided password was wrong. In the 2nd try the password was accepted but a helper process failed to start. Could you check if any crash of process “nxplayer” is reported in your system log or in the /var/crash folder?
graywolfParticipantI’ve observed VSC behavior and concluded it does not benefit of X11 vector graphics. It looks rendering the content of its user interface as images, text included.
The only way to handle this would be using PNG-encoded images as you’ve done. As you noticed, that would impact performance. Such impact could be reduced choosing a lower quality for png (adding a suffix to 16m-png string, e.g. 16m-png-5 would fix quality to level 5, with possible level ranging from 1 up to 9).
graywolfParticipantWould you create an archive of log folder on your server:
sudo tar zcf NoMachine-log.tar.gz /usr/NX/var/log
and send to address forum at nomachine dot com ?
January 4, 2019 at 16:54 in reply to: Problems with “Match the client resolution upon connecting" #21007graywolfParticipantI think the explanation is this.
KDE stores the size somewhere (.kde/share/config/systemsettingsrc, probably). The saved size is 800×600. After it starts, KDE set the saved size. If NoMachine sets its size after KDE, you get the “right” size, otherwise you get the “wrong” one.
I don’t think it is a bug, but I’d check whether KDE saves the correct screen size (at Logout or when size is changed through System Settings).
January 4, 2019 at 12:49 in reply to: Problems with “Match the client resolution upon connecting" #21000graywolfParticipantIt looks enough, just check if any X server is running with
ps -ef | grep X
.January 4, 2019 at 10:47 in reply to: Problems with “Match the client resolution upon connecting" #20996graywolfParticipantYou want to use the embedded X server: in NoMachine free edition a such thing is possible if display service is not running on the remote server.
So you should ensure you turned off the display service (KDM, GDM, LigthDM or whatever).
You wrote about a server with “physical resolution 800×600”, but if display service were turned off you’d have no “physical resulution” at all.
Did you turn off the display service?January 3, 2019 at 11:41 in reply to: Problems with “Match the client resolution upon connecting" #20988graywolfParticipantIt looks related to this problem: Automatic resize fails in GNOME virtual desktops
Which version of NoMachine are you using?
graywolfParticipantHello. I think the Cmd key is interpreted by Ubuntu desktop as a command to show the activities overlay.
The same action is bond to the “Activities” menu, so I think you could find useful disabling the hotkey. You can do that using this command:gsettings set org.gnome.mutter overlay-key ""
graywolfParticipantPlease, would you check if zenity is installed:
which zenity
and install in case it is not:
sudo apt-get install zenity
Then retry, watch if behavior changed, collect new logs.
graywolfParticipantWould you try to change this in node.cfg:
DisplayServerExtraOptions "-extension MIT-SHM"
It affects the way text and images are encoded for remote transfer.
graywolfParticipantCould you paste the output of command
ps -ef | grep X
?Please, change SessionLogLevel and SessionLogClean in /usr/NX/etc/node.cfg:
SessionLogLevel 7
SessionLogClean 0
Reproduce the issue, create an archive of log folder:
sudo tar zcf NoMachine-server-log.tar.gz /usr/NX/var/log
and send NoMachine-server-log.tar.gz to: forum (at) nomachine (dot) com .
graywolfParticipantPlease upgrade to the latest version (6.4.6). I’m going to build libraries with verbose logging for debugging.
graywolfParticipantMay I ask you this piece of info: just after you’ve provided username/password do you get message “Authentication failed, please try again” in the NoMachine Settings window? Or you get nothing?
graywolfParticipantHello. Conversion to a lower color depth is currently not in our plans. By the way, I understand you’d have found it useful for your case. We’ll evaluate such a feature request.
-
AuthorPosts