loprain.blogg.se - Nomachine debian package

Maybe I unconciously clicked Yes to the question, which might explain an unability to connect to an existing session and CreateDisplay 1 in /usr/NX/etc/server.cfg (doesn't explain an unability to connect to the internet, though).ī's SSD is having some problems (my Linux partition there didn't boot up today before I did fsck -fy to it). Always create a new display for this server?". In Nomachine, I've since seen a dialog "Cannot detect a display on server xxxxx. When B crashed (as it occasionally does), Nomachine's server settings were corrupted / overwritten on next reboot. did a logout.Īs to the root cause of the mess, I have three theories: There's also a very slight possibility that I didn't reboot after changing B's /usr/NX/etc/server.cfg but e.g. Also possibly (but more unlikely), leaving the network cable disconnected on one of the reboots flushed some corrupted settings, and things worked after that. Possibly, the shutdown after the first reboot fixed some settings on B, and it rebooted correctly after that.

The first, obvious one is that the computer (probably B) needed multiple reboots. I have some theories concerning all this. 1.4.0.2-0alpha4 NoMachine NX - NX compression library ii libnxcompext0. I "forgot" the whole business for a couple of days and when I fired the computers up - bang! It worked. for APT ii apt-move 4.2.24-1.1 Maintain Debian packages in a package pool ii. Took a look at the server's configuration file (on B) at /usr/NX/etc/server.cfg, which contained some suspicious key values. Upgraded all packages and Nomachine on both machines to newest versions (they were different but this didn't interfere w/ using them (till they worked)). I solved the problem but am a bit unsure on how. Needless to say, I've rebooted both machines many times. This has suppressed the "System policy prevents control of network connections" messages and temporarily fixed the keyring nag ( login.keyring gets re-created and sometimes fires the nag again) but hasn't enabled me to connect to an existing X session on B. (this is a message I sometimes got) in /usr/share/polkit-1/actions/: System policy prevents control of network connections

commented out the following value of allow_any of.

(tried also versions w/ ResultAny=no and ResultInactive=no)

created /etc/polkit-1/localauthority/50-local.d/50-allow-network-manager.pkla:Īction=.modify.system -control.

Mv /home/j/.local/share/keyrings/login.keyring /home/j/.local/share/keyrings/ So it seems that something's preventing me from accessing the web over Nomachine, creating a new webless X session instead. If I open a web browser in the B session displayed only in A, the browser opens only in the existing X session on B (this is the only way I can interact w/ the X session there). Upon connecting, I lately also sometimes get warnings either about a keyring or not being allowed to control network, so I suspect a polkit issue. To my knowledge, I haven't done (installed, removed, changed, etc.) anything to deserve this. However, lately it always creates a new session on B while showing it on A only. The client machine A has always connected to an existing X session in the server machine B displaying it in both A and B.

I've used Nomachine for years to connect my 2 Linux laptops.