graywolf

[graywolf]

I downloaded and tried Valentina Studio, created a diagram with two tables, and can resize/move them without problems. Do I miss some detail?

[graywolf]

It looks the server desktop is running on Wayland. Is the server a virtual machine? In that case, you can revert to Xorg by uncommenting line #WaylandEnable=false in /etc/gdm/custom.conf and restarting the display manager with systemctl restart gdm.

[graywolf]

Sorry, HTML formatting corrupted the double quotes, retrying with unformatted text:

lsmod | grep "nvidia\|nouveau"
dmesg | grep "nvidia\|nouveau"

[graywolf]

Please, in the remote session run these commands in a terminal:

lsmod | grep “nvidia\|nouveau”
dmesg | grep “nvidia\|nouveau”
nvidia-smi
env | grep DISPLAY

[graywolf]

With session connected, would you open the NoMachine Menu (ctrl+Alt+0) and take screenshots of panels:

Connection information (NoMachine Menu > Connection)
Display settings (NoMachine Menu > Display > Change settings)

[graywolf]

Hello cwernham,
is that a screen sharing or a virtual desktop session?

Could you provide details about the server host? Is it a physical or virtual machine? Any video card installed on it?

Client side: have you changed something in the “Display settings” panel?

• This reply was modified 6 years, 7 months ago by graywolf.

[graywolf]

Would you try with “Disable multi-pass display encoding” unchecked?

[graywolf]

Could you run these commands in the Konsole window and tell me the output:

sudo lshw -C display
and
env | grep DISPLAY

[graywolf]

Difference in “time” field of those events is 93 ms. It doesn’t look so short. Events are produced and consumed in the same way for any application. So it looks something different than an “event flooding” (the same flooding would happen for xterm as well as any other app).

Maybe a video could help us to understand what is happening.

Could you provide some detail about the Linux OS of client and server host? I’d like to try to reproduce the same issue.

[graywolf]

Are you trying to share the physical display of the Linux machine or is it a virtual display session?

Could you provide some details about the the Linux distribution and the desktop environment in use?

[graywolf]

What if you ran xterm and then you launched xev from there? Are such scrolling events logged by xev?

[graywolf]

I’m going to open a Trouble Report for that. It looks the sequence of input event is correct, so the source of the problem is not completely clear. At least we know how to reproduce and that should help.

[graywolf]

I can reproduce in Windows file manager:

1. Open an Explorer window
2. Select a file
3. Press Shift+Delete: a confirmation dialog will be shown
4. Press Esc to cancel

After a such sequence – almost all the times – clicking in the file manger window does nothing or selects multiple files. Explorer only got confused about the Shift key state: the key is not actually stuck as things work as expected in other applications. By the way, pressing the left or right Shift key once restores the normal behavior.

[graywolf]

Create the script /usr/NX/share/AfterSessionStart.sh:

#!/bin/sh

sessionID=$1
userName=$2
sessionType=$3
displayNumber=$4

HOME=$(getent passwd $userName | awk -F : '{print $6}')
export HOME

setxkbmap -layout us,ru -option grp:lctrl_lalt_toggle -display :$displayNumber

exit 0

Make it executable:
chmod +x /usr/NX/share/AfterSessionStart.sh

Edit /usr/NX/etc/node.cfg and change the keys UserScriptAfterSessionStart and UserScriptAfterSessionReconnect (if you edit the existing lines remember to remove the heading “#”):
UserScriptAfterSessionStart "/usr/NX/share/AfterSessionStart.sh"
UserScriptAfterSessionReconnect "/usr/NX/share/AfterSessionStart.sh"

Start remote session as usual. You’ll be able to toggle US and Russian layouts just pressing left Ctrl + left Alt combo.

• This reply was modified 6 years, 9 months ago by graywolf.
• This reply was modified 6 years, 9 months ago by graywolf.
• This reply was modified 6 years, 9 months ago by graywolf.

[graywolf]

We need the folder “node” for troubleshooting. It is located under “log” but missing in the zip archive.

[Author]

Posts