No desktop available (Kubuntu 22.04)

[boospy]

Hello all,

I am using here Kubuntu 22.04 as Server and as client. On other computers with the same system NX is working fine. But this one doesn’t really want to. At some point in 20.04, nx stopped working properly. Meaning: When you log in, you come to the normal NX menu and see “no desktop available”. The PHY screen is not available.

I have now completely uninstalled NoMachine here on 22.04, deleted all remaining files with rm, rebooted and reinstalled. Same behaviour.

What could be the problem here? What logs do you need to help me? NX Version 8.1.2-1

Very thanks

Best Regards 🙂

[Britgirl]

Hi, we are aware of an issue related to Wayland and the workaround for the moment is to disable Wayland and user X.org. Can you send us the logs of the remote Kubuntu server so we can check it’s the same issue we are currently investigating? Please consult the following document for instructions on how to extract the logs and submit them here, or send them directly to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!

https://kb.nomachine.com/DT07S00243

[epiphany123]

I am suffering from the same bug in Gnome Wayland sessions. The server doesn’t always start at boot.

 

Nov 06 18:44:09 systemd[1]: nxserver.service: Deactivated successfully.

Nov 06 18:44:09 systemd[1]: nxserver.service: Consumed 4.054s CPU time.

[boospy]

Ok, I have debugged. I have found out that it is the pam_automount. When I move the file, I can connect immediately. I also noticed that although I ignore the user NX in the file pam_mount.conf.xml, this option of the file is ignored. This means that no screen is started.

Here are the Log during the login process: (sorry, didn’t find a code block for the post)

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:68): Messages from underlying mount program:

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): mount error(13): Permission denied

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Nov 11 19:12:04 kitten kernel: CIFS: VFS: cifs_mount failed w/return code = -13

Nov 11 19:12:04 kitten nxexec[106020]: (pam_mount.c:522): mount of Programme failed

Nov 11 19:12:04 kitten audit[909]: AVC apparmor=”DENIED” operation=”open” profile=”/usr/sbin/sssd” name=”/proc/106039/cmdline” pid=909 comm=”sssd_nss” requested_mask=”r” denied_mask=”r” fsuid=0 ouid=0

Nov 11 19:12:04 kitten kernel: CIFS: Attempting to mount \\data.tux.lan\iso-images

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:68): Messages from underlying mount program:

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): mount error(13): Permission denied

Nov 11 19:12:04 kitten nxexec[106020]: (mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Nov 11 19:12:04 kitten kernel: CIFS: VFS: cifs_mount failed w/return code = -13

Nov 11 19:12:04 kitten nxexec[106020]: (pam_mount.c:522): mount of iso-images failed

Here is n line from the “/etc/security/pam_mount.conf.xml”

rootsddmnx

I have also a NoMachine Workstation Version here, and there it works fine. Both are 8.2.3-4. I have the logs when it failed also attached. Maybe someone can read out a useful error message.

Thank you

Best Regards 🙂

Attachments:

1. NoMachine-log-2022.11.11-16.23.07.zip

[Britgirl]

Logs show multiple lines like:

mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(13): Permission denied
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
(pam_mount.c:522): mount of Programme failed
(mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(13): Permission denied
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
(pam_mount.c:522): mount of iso-images failed

Why this is happening, we can’t say. It indicates problems with your system, and not NoMachine, given that on your other server, everything is working without any issues.

[boospy]

I was able to solve it, I don’t know why this is the case with this machine. Apparently something is really bent. In any case, the solution was this:

In addition to the exclude, you must add an “or”. This does not make sense. But since then, NoMachine works again with pam Automount.

File: /etc/security/pam_mount.conf.xml

root sddm nx root sddm nx

[Britgirl]

Thanks for letting us know. We’ll consider this resolved and unrelated to NoMachine.

[Author]

Posts