Some issues on Workstation

[tweetiepooh]

I currently use OpenSuse 11.3 on an Sun x86 with Quadro card and the old 3.5 2 user server and all is well but we need to upgrade and there are some issues with OpenSuse 13.2 and restarting sessions linked to libcairo and I would like to use 42+ and plasma so evaluating Workstation at home prior to forking out my own money.

So setup at home is Laptop with OpenSuse 42.2 and latest Workstation/client.

Desktop with nVidia card multiboot with OpenSuse 42.1 and OpenSuse 13.2.  Both have latest Workstation/client.

At work I’m trying a virtual OpenSuse 13.2 and Windows 7 client.

In all cases I attach to a user only used for these remote connections so there is no mixup between using locally and remotely.

I also have Fit to window set as my client could be running on different monitors at different times.

1)Laptop to 42.1 desktop – plasma dies on connection and while I see something I can’t actually do anything.  I may need to look at the nomodeset I’ve seen mentioned elsewhere.

2)Desktop to 42.2 laptop – session start OK and works fine but

3)Any connection – If I autohide the KDE taskbar (I’d want to) I get very odd behavior.  In a windowed client I can’t open the task bar, if I full screen the client I can.  This is actually OK as it is how I want to run things anyway except although I can now open the taskbar it doesn’t always do anything.  I can sometimes get the tool tips but nothing actually works.  If I set the taskbar to fixed then in window it works but still doesn’t always work in full screen.  In window I can see there is a hidden taskbar but moving mouse to bottom of window doesn’t open it.  (This could be if I set the hidden to “small” maybe in Window it’s less than a pixel so never activates – just thinking that.)

I’d really like to get all this working so I can rebuild my workstation and get it relocated as KDE/Nomachine gives me the environment I am used to and am productive in.

Thanks and sorry if this has been asked before but finding the answers isn’t always easy.

[fra81]

Hello,

as for your points above:

1) Are you using proprietary nVidia drivers? You can try to send us the logs for inspection. NoMachine logs can be gathered by following the instructions in https://www.nomachine.com/DT07M00098. Also the .xsession-errors file in the user’s home on the server, if present, could be useful. You can send everything to forum[at]nomachine[dot]com.

3) Please try to disable the Fit to window mode and check if the hidden taskbar is still unreachable. It could be an effect of the scaling of the session, where the 1-pixel sensible area could be rounded down to 0 pixels. Ragarding the strange behaviours of the taskbar, we will try to reproduce them in our labs, but, if possible, a screen recording could help to clarify the issues.

[tweetiepooh]

Hi and thanks for the reply.

The server side does and will use propitiatory nVidia drivers.  The client side isn’t nVidia at all.  This has all been fine with the current setup (Server on Sun X86 and OpenSuse 11.3 KDE 4).  The client will be the same in new setup just for work will be Windows not Linux.

I guessed the autohide issue may be due to that.  It’s not really a biggie as I will always run fullscreen.  I need the autofit as the client screen size can vary, normally it’s on a 4:3 ratio 19″ so plenty of vertical pixels.

I’m emailing the log files.

I hope I can get this working, I’d have to pay for the software out of own pocket and so want to get it working.  (From reading I think the license can be move as long as basic distro remains the same.)

[fra81]

Hi,

it looks like the same problem reported here:

https://bugs.kde.org/show_bug.cgi?id=377335

I suspect the problem is related to libGL.so provided by nVidia. As a workaround, you can try to set the LD_LIBRARY_PATH in order to use the Mesa version of libGL. To do so, you have to modify the DefaultDesktopCommand key in the /usr/NX/etc/node.cfg configuration file:

DefaultDesktopCommand “env LD_LIBRARY_PATH=<directory where Mesa’s libGL.so is in> <command to start KDE>”

You can find the path to Mesa’s libGL by issuing this command:

ldconfig -p | grep libGL

For example:

DefaultDesktopCommand “env LD_LIBRARY_PATH=/usr/lib64 /usr/bin/dbus-launch –exit-with-session startkde”

[tweetiepooh]

Hi

I can see that the Mesa libGL is in /usr/lib64 and tried to setup as shown but plasma still crashes.

DesktopCommandLibraryPath=”/usr/lib64″  is also set

Do I need to try anything else as I still see plasma crashing and then blank screen?

What I can’t try yet is on an install with noveau drivers

Thanks

[fra81]

Hi,

can you send the new logs?

Besides trying open source drivers, you can try to enable VirtualGL:

https://www.nomachine.com/AR11K00737

[tweetiepooh]

I tried the VirtualGL and I just get the client screen flash briefly and disappear.  Rolled back and I see Plasma failing but at least session starts.

I may look at seeing if Tumbleweed will work as I’d use the non-Nvidia drivers with that.  (This is so O/S keeps upto date for longer)

[tweetiepooh]

Tried adding nomodeset to kernel parameters but no joy.

[tweetiepooh]

I installed OpenSuse Tumbleweed and I can connect to that.  It’s not especially “nice” yet and still have issue with the bottom panel not unhiding where the old KDE4 did work fine.

I push mouse to bottom and I see a  blue glow but the panel doesn’t display.

At least though I have a session, this is with the noveau drivers not recommended with KDE.

I want to try against 42.2 see if it works on a basic install then if the NVidia drivers break things.

I will attach logs from earlier session to email as requested.

[fra81]

I assume the logs you sent are from your attempts with VirtualGL (and not from previous attempts with adjusting LD_LIBRARY_PATH). So it looks like VirtualGL couldn’t access the display:

Invalid MIT-MAGIC-COOKIE-1 key[VGL] ERROR: Could not open display :0.

Maybe you didn’t run the command shown in the article?

/usr/NX/scripts/vgl/vglserver_config -config +s +t +f

[Author]

Posts