Forum Replies Created
-
Posts
-
Hi, in the logs we see a number of different errors, both Wayland and X11 sessions fail. But first let’s investigate Wayland.
Can you show us the output of the following dbus method call ‘GetCurrentState’ to check if the monitor configuration looks correct? To do that you need to install the d-feet application and run the method as highlighted in the screenshot (below) by double clicking it.
Also, try connecting when the server machine’s screen is not locked. Do you still get the white screen?
Attachments:
Apologies for the delay in coming back to you. Upon further investigation we were able to reproduce the same error and have opened a trouble report which you can view at the following link: https://kb.nomachine.com/TR02W11278.
It could be that Pipewire in Manjaro may be causing problems (which we would like to investigate further). In the meantime, you could switch to Pulsewire instead. Please take a look at the article. You will have to adjust the commands for your own system:
How to enable audio on systems relying on PipeWire for sound
https://kb.nomachine.com/AR07T01168– Please tell us the exact version of your OS (manjaro version).
– And the version of the audio server. The easiest way to check is by command “pactl info”. What does it show? If the “pactl” command doesn’t exist, you can check the pipewire version by running “pw-cli info 0”.Gather logs from both server and client machines as per the instructions here please, https://kb.nomachine.com/DT07S00243, and send them to forum[at]nomachine[dot]com. Thanks.
Hi, we need complete logs from the macOS machine; the ones you attached were only from the server component (we’d need the agent/node logs as well).
You can extract all logs from the macOS server using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
li_simo_hayha_il
please update to the latest 8.16 and let us know if you are still encountering the issue.
Hi, the logs didn’t include the user’s home which is strange, the automatic procedure should include it. Can you try again, this time with the manual procedure?
https://kb.nomachine.com/DT07S00244
Hi, what version of Ubuntu is on your RPi?
On your macOS client (what OS version btw), do you mean you cannot see the Ubuntu host advertized on your same LAN? (it has a pipe icon).
From the Windows client, can you see the Ubuntu host?
Have you tried connecting to the Ubuntu host by creating a connection manually?
To be honest, this looks to be a job for NoMachine Support and not something that can be handled in the forums. It would require quite a deep investigation as to why this is happening with Cadence Virtuoso only in one particular environment (MATE), but yet in Gnome everything works correctly. That said, we can suggest you disable X11 vector graphics to see if that helps.
In the node.cfg set:
AgentX11VectorGraphics 0
https://kb.nomachine.com/AR02L00779
The X11 vector graphics mode in X-Window virtual desktopWe went through our article and checked our configurations with what you posted. Bear in mind that the instructions in the article are for one type of many possible configurations. For your set up, this should work:
edit /etc/pam.d/nx like here:
# This is a default PAM configuration for NoMachine. It is based on
# system’s ‘su’ configuration and can be adjusted freely according
# to administrative needs on the system.auth [success=1 default=ignore] pam_unix.so nullok
auth requisite pam_deny.so
auth required pam_permit.so
auth required pam_ecryptfs.so unwrap
auth optional pam_cap.soauth required pam_google_authenticator.so
account include su
password include su
session include suWe’ve tested it and it works.
