Cannot create a new display

[Britgirl]

I am able to get a desktop connected with NoMachine if I use a barebones local user account. If I use my Active Directory login with sssd, it doesn’t work. So it could be something related to my AD user configuration, or something with sssd specifically.

This seems to be a different problem to the original one and we don’t understand how the two could be related without investigating further. This might warrant a separate topic so as not to confuse the thread. But first the original issue of not being able to create a display…

For some reason Gnome is failing and to understand why we would need to see the journalctl log of the server. Run (without the ‘grep’)

sudo journalctl -x

[Nuertey]

Hello @Britgirl,
Thanks for keeping this topic alive. Attached is ‘my’ journalctl log of the server.
Regards
Nuertey

[Britgirl]

Hi Nuertey, send it to forum[at]nomachine[dot]com. There must be a character in the file that is clashing with our filter.

[Britgirl]

Nuertey, your file shows

Oct 12 16:42:15 ip-10-102-91-113.xxxxxx.com gnome-session[3258]: gnome-session-binary[3258]: WARNING: software acceleration check failed: Child process exited with code 1

You can try adding --disable-acceleration-check option in the gnome-session command in the DefaultDesktopCommand key, in /usr/NX/etc/node.cfg.

[Author]

Posts