Single user with black screen accessing NoMachine Terminal Server on Xenial

[thager]

Hi there,

we’re in the process of evaluating NoMachine Terminal Server on a few Linux servers. Runs pretty well, but one of the test users ends up with a black screen when connecting with the NoMachine Client.

Some details first:

• NoMachine Client 5.2.21 on Windows 7
• NoMachine Terminal Server Evaluation 5.2.21 on Ubuntu 16.04 LTS x86_64
• The Ubuntu server is running on a VMware farm
• Users are connecting to virtual Unity desktops

Other test users on the same NoMachine server work fine, NoMachine displays a virtual Unity desktop as expected. I can’t see any errors in the server logs, but I found some errors in the affected client’s session log:

[…]
65294 65294 10:40:42 160.888 MonitorDB: Adding user ‘xxx’.
65294 65294 10:40:42 160.978 ClientSlave: Starting config slave with command get.
65294 65294 10:40:42 165.139 MonitorDB: There are ‘1’ users.
[05.16.17 10:40:42.186] X Error: BadMatch 8
Major opcode: 62 ()
Resource id:  0x8003ac
[05.16.17 10:40:42.200] X Error: BadMatch 8
Major opcode: 62 ()
Resource id:  0x8003b1

I spent some time on Google, but didn’t find any clues. Does this error ring a bell in here?

Tia for any help 🙂

Cheers,
Tom.

[fra81]

Hi Tom,

please send a complete set of logs (client and server side) as explained here: https://www.nomachine.com/DT07M00098.

Also the ‘.xsession-errors’ file in the user’s home directory on the server could be useful.

You can send everything to forum[at]nomachine[dot]com.

[thager]

Hi,

sure, will do. Gonna take some time though, because I have to get hold of this particular test user first 🙂

Cheers,
Tom.

[thager]

Hi,

did you receive the files I sent?

Cheers,
Tom.

[Britgirl]

Yes, we did thank you. One of the team will get back to you soon.

[fra81]

Hi,

.xsession-errors shows the problem:

openConnection: connect: No such file or directory
cannot connect to brltty at :0
upstart: Failed to spawn upstart-udev-bridge main process: unable to execute: No such file or directory
upstart: unity-gtk-module main process (1889) terminated with status 127
upstart: dbus pre-start process (1891) terminated with status 127

This issue is known:

https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1537610

You could try the workaround reported here:

https://askubuntu.com/questions/763735/ubuntu-16-04-blank-screen-at-bootup/871156#871156

[thager]

Hi,

yeah, that sounds reasonable. I checked the user’s environment, he’s setting a custom path environment, which excludes /sbin.

He’s not available right now, but I’ll get in touch with him on Monday. I’ll update this thread as soon as we were able to test.

Thanks and have a nice weekend,
Tom.

[thager]

And for the records: After fixing the user’s PATH, NoMachine runs smoothly, no more black screen 🙂

Thanks a lot for your help!

Cheers,
Tom.

[Author]

Posts