Unable to contact settings server

[buzz]

Greetings,

I am having a problem accessing a NoMachine server.  This problem starting about a week ago, and I have been accessing this server via NoMachine for a couple years without issue.

Environment:

Arch Linux 4.18.9.arch1-1

NoMachine 6.2.4-1

dbus 1.12.10-2

When I connect to the server via NoMachine, all appears normal at first.  However, after entering my username and password, the screen goes white for ~10-15 seconds.

Then I see a dialog box on the remote machine:

Unable to contact settings server

Failed to connect to socket /tmp/dbus-xxxxxxxxxx: Connection refused

Interestingly, at the same time I see a notification on the remote desktop:

“User me connected”

The rest of the remote desktop is just black.

When I click the the close button for the settings server dialog box, I receive another message:

Unable to load a failsafe session

Unable to determine failsafe session name. Possible causes:

xfconfd isn’t running (D-bus setup problem); environment

variable $XDG_CONFIG_DIRS is set incorrectly (must

include “/etc”), or xfce4-session is installed incorrectly.

When I click the “quit” button on this dialog box, I am taken back to the local NoMachine connections interface.

I have attached the nxd.log, nxerror.log, and nxserver.log files.

Your help is greatly appreciated!

buzz

[Britgirl]

Hi Buzz, can you send the logs directly to us? To forum[at]nomachine[dot]com.

[buzz]

Hi, BritGirl,

I just emailed the log files to you at the address you provided.

Again, thank you for helping me with this!

buzz

[kroy]

Hi

Please try to run session with dbus command. Edit as root /usr/NX/etc/node.cfg file, uncomment (if it’s commented) and modify DefaultDesktopCommand key.

The entire line should look like this:

DefaultDesktopCommand "/usr/bin/dbus-launch /usr/bin/startxfce4"

[buzz]

Hi, kroy,

I modified the node.cfg file per your instructions, and my problem is resolved!  Thank you!

Do you have an idea why this change is required?  I’ve been connecting to this machine via NoMachine for years, so I am curious what changed recently to require this update to the NoMachine configuration.

Thank you again!

buzz

[kroy]

We are pleased that we could help. The problem was caused by the system update.

[Britgirl]

We have opened a Trouble Report concerning this issue. Please sign up to the notify me tool to receive news of the patch.

Cannot start a virtual session on Arch Linux
https://www.nomachine.com/TR10P08907

Further reference:

Incorrect error message to modify during installation on Arch Linux
https://www.nomachine.com/TR10P08902

[Author]

Posts