jdcordell

[jdcordell]

Graywolf,

Thanks for the support. This a solved the issue!

Apologies, as a logout/login worked. There was no need to edit ‘/usr/share/sddm/scripts/Xsession’.

Thanks,

Joe

[jdcordell]

Yes. If i launch a custom session as run the console.

startkde returns:

Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified

[VGL] ERROR: Could not open display :0.

several times

[jdcordell]

Thanks for the support. Sorry for my delay.

Yes – SDDM is the display manager.

1.

The first line in /etc/X11/xdm/Xsetup  is xhost +LOCAL:

It appears VirtualGL setup changed it correctly.

2/3. Sleep command was applied to both: /etc/X11/xdm/Xsetup and /usr/share/sddm/scripts/Xsetup

4. sddm was restarted

I still cannot open a virtual desktop with user2. I received the error “the connection with the server was shutdown”

 

In DISPLAY:0 as user1(liam), xhost returns:

access control enabled, only authorized clients can connect

LOCAL:

 

 

Should be possible for user2 to spawn their own virtual desktops. Even when DISPLAY:0 belongs to user1?

[jdcordell]

Hi,

Thanks for your rapid response. Digging through these suggestions it is clear I might have deeper issues.

On restarting the server/host machine I can no longer see any display:0 (as expected) or load a virtual desktop (Makes sense if VirtualGL requires access to the display :0)

Opening a console into server/host machine to start display:

liam@NEESON:~> startkde

Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified

[VGL] ERROR: Could not open display :0.

startkde: Starting up...

Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified

[VGL] ERROR: Could not open display :0.

kdeinit5: Communication error with launcher. Exiting!

Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash

kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__1002) failed: : Connection refused

Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified

[VGL] ERROR: Could not open display :0.

startkde: Shutting down...

kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__1002) failed: : Connection refused

Error: Can not contact kdeinit5!

startkde: Done.

These errors are in “Troubleshooting problems when enabling VirtualGL support for NoMachine virtual desktops” https://www.nomachine.com/AR04Q01024

So, following B)

VirtualGL has been setup following your guide. It is working:

How to check if VirtualGL is in use: glxinfo | grep -i “renderer\|vendor” returns:

liam@NEESON:~> glxinfo | grep -i "renderer\|vendor"

server glx vendor string: VirtualGL

client glx vendor string: VirtualGL

OpenGL vendor string: NVIDIA Corporation

OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2

liam@NEESON:~> env DISPLAY=:0 xhost

Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified

xhost:  unable to open display ":0"

Local is not returned

liam@NEESON:~> systemctl restart display-manager

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to restart 'display-manager.service'.

Authenticating as: root

Password:

==== AUTHENTICATION COMPLETE ===

Nothing changes.

“startkde” and “env DISPLAY=:0 xhost” return the same problems

I am assuming my problem stems from here.

As a work around:

By physically logging into the server/host (NEESON) machine as liam, display:0 appears and can be accessed remotely and virtual desktops can be created as user 1.

However user2 is still unable to create their own virtual desktops!

Just to make sure NoMachine is able to achieve what I am trying to do:

NoMachine virtual desktops can be spawned by user1.

Then User2 can access these, but then appears as user1 within the virtual desktop.

Should be possible for user2 to spawn their own virtual desktops.

Even when DISPLAY:0 belongs to user1?

[Author]

Posts