graywolf

[graywolf]

Hello. I’m assumining you are sharing the “Physical desktop” of RHEL7 server, where NVIDIA driver would be effective.

I’m observing some visual artifacts viewing the desktop through NoMachine. Those are transient and can be barely noticed, they affect a few line of the screen for a moment and don’t disrupt my workflow. So I’m assuming this issue is much more evident in your case (whole screen turning into blue?).

I also noticed that using nouveau open source driver no artifact is visible. So I’d suggest to switch to nouveau driver, if possible.

[graywolf]

Hello, I’ve just tried IDEA 14.1.4 on Ubuntu 14.04 and the Edit Configurations dialog shows no issue.

Could you provide more details (is it virtual desktop, physical session, single application?). If possible, please gather log files as described: https://www.nomachine.com/AR07K00677

[graywolf]

There is an option to ignore mouse and keyboard input coming from the client. Look at /usr/NX/etc/server.cfg:

#
# Set the interaction level for the session connected to the physical
# desktop:
#
# 0: View-only. The session is connected to the desktop in
# view-only mode, i.e. the user can't interact with the
# physical desktop.
#
# 1: Restricted. User connected to the physical desktop can
# interact with the desktop except for resize operations.
#
# 2: Interactive. User connected to the physical desktop has
# full interaction with the desktop.
#
PhysicalDesktopMode 1

The feature request you mentioned is not implemented yet, but you do not need it anyway: it is about the ability of changing the view mode at run-time.

• This reply was modified 8 years, 10 months ago by graywolf.
• This reply was modified 8 years, 10 months ago by graywolf.

[graywolf]

Hello.

Could you send the output of command “xinput” that you get on the display of the server (Lubuntu 15.04) you are trying to share?

 

[graywolf]

I tried your setup but cannot reproduce. Could you send client and server logs to forum (at) nomachine (dot) com?

[graywolf]

Keyboard input from client to the server always defaults to sending us layout signals, even when I have no layout and keyboards attached to both server and client.

Can you describe what happened exactly and what did you expect in such a case?

[graywolf]

Thanks for reporting. I can reproduce, actually we have issues with those shortcuts on Windows server. I’m going to create a Trouble Report about this issue.

[graywolf]

Some desktop are able to catch the shortcuts even if “Grab the keyboard input” is turned on.

Switch the client into fullscreen mode if you want to let “Grab the keyboard input” capture the keyboard completely.

[graywolf]

Hello <span class=”bbp-author-name”>songjiang</span>

1)  Double-click doesn’t work in the Mac Finder

I am not able to find this issue. I can open documents using double-click without problems. As you found this issue only in Finder, I think it is due to some application-specific configuration. I’d take a look of Mouse settings double-click speed.

2) I’m getting interference on the Linux side when I use the super and/or alt buttons in keyboard shortcuts.

Hit Ctrl+Alt+0, then chose “Input” and “Grab the keyboard” input. Sometimes this is not enough, but if you switch the display mode to full screen (Ctrl+Alt+0, “Display”, “Fullscreen”) it works more consistently.

As last resort, remove the Ubuntu keyboard shortcuts affecting your work. Install CompizConfig Settings Manager, launch it and choose to change settings of Ubuntu Unity Plugin. The interesting keys are in the Launcher tab.

 

[graywolf]

Sorry, it wasn’t clear in my post that suggestions about changing lightdm.conf and xserver-command would be useful only in case 2.

In your case you have a working X server as display :0 and you can connect by NoMachine: I would not tweak X11 configuration anymore. You should not even run Xvfb and Gnome manually.

So the only issue is about resolution:

1. Check if your X server supports other resolutions. Connect to display :0 and run command “xrandr -q”
2. Try to change resolution in Gnome. Search in the Gnome menu for something like “Preferences” or “System settings” then search for “Monitor” or “Display”. When you change resolution there, it is stored for the next time you log in.

The X server resolution can also be set in /etc/X11/xorg.conf, but I would prefer setting it in Gnome.

[graywolf]

AR10K00710 describes how to run Xvfb  and Gnome together. They are launched manually and not automatically restarted at reboot.

The error “Server is already active for display 0” is issued because file /tmp.X0-lock already exists, but it could be a leftover of a crashed X server.

So as first thing I’d check if any X server is running as display :0. Try this command:

ps -ef | grep X.*:0

There are to cases.

1. If X was already running as display :0 (and Gnome is  using it) you have to do nothing, you haven’t to run Xvfb even. Just run the NoMachine client and choose to connect to session on display :0.

2. In the opposite case, if you found that no X is running, you need to remove /tmp/.X0-lock. If you need to set Xvfb permanently, in order to run it at reboot, I think you could configure the lightdm scripts to run Xvfb in place of Xorg. I never tried this before, so I’m not aware of issues that could arise:

Edit /etc/lightdm/lightdm.conf to add a line to [SeatDefaults]:

[SeatDefaults]
xserver-command=/etc/X11/xserver-command

Create the script /etc/X11/xserver-command:

#!/bin/sh
display=$(echo "$@" | awk '{for (i=1;i<=NF;i++) {if ($i ~ /^:/) {print $i}}}')
auth=$(echo "$@" | awk '{for (i=1;i<=NF;i++) {if ($i ~ /^-auth/) {print $i,$(i+1)}}}')
exec Xvfb ${display} ${auth} -screen 0 1800x1200x24

Then restart lightdm and NoMachine:

/usr/NX/bin/nxserver –shutdown

service lightdm stop

service lightdm start

/usr/NX/bin/nxserver –startup

After that, Xvfb will be launched with services on boot.

• This reply was modified 8 years, 11 months ago by graywolf.
• This reply was modified 8 years, 11 months ago by graywolf.
• This reply was modified 5 years, 5 months ago by Britgirl.

[graywolf]

@javier

virtual desktops alredy use virtual display servers, so there is no need to run another one like Xvfb.

You found VLC and Mplayer work fine in the physical display. But this EC2 is a virutal machine, so I guess you followed the article https://www.nomachine.com/AR10K00710    or you installed any kind of virtual X server to emualte that physical display. Could you tell me which is the procedure you followed?

Could you provide the output of command “xdpyinfo” for such physical display on EC2 machine?

[graywolf]

Did you follow https://www.nomachine.com/AR10K00710   to create an X session on a headless Linux server?

Xvfb has no RandR extension, so it isn’t possible changing revolution (it sounds strange you have little choice among two resolutions: you should have none). By the way, you can chose the Xvfb resolution in the -screen command line option.

 

 

 

[graywolf]

May you get a gdb backtrace of frozen emacs process?

[graywolf]

Which is the start menu that pops up when you press the Windows key? The menu in the client-side desktop (Linux Mint)?

In that case, did you try to let the client grab the keyboard? With remote session running, Press Ctrl+Alt+0 then chose “Input” and check the box “Grab the keyboard input”.

[Author]

Posts