Forum / NoMachine for Linux / Error 108 for Windows -> Ubuntu with version 9.3.7
- This topic has 8 replies, 3 voices, and was last updated 1 week, 6 days ago by
Britgirl.
-
AuthorPosts
-
January 26, 2026 at 09:46 #55345
danergoParticipantFolks, please help me.
I’m running the latest NoMachine on both my Linux Ubuntu (server), and on Windows 11 (client).
It was working before but now nxnode.bin segfaults.
Server: Ubuntu 24.04.3 LTS, Kernel: 6.8.0-90-generic
Journal log:
Journal log: jan 24 15:22:14 main nxexec[553821]: pam_unix(nx:session): session opened for user dan (uid=1000) by (uid=127) jan 24 15:22:14 main systemd-logind[2720]: New session c73 of user dan. jan 24 15:22:14 main systemd[1]: Started session-c73.scope – Session c73 of User dan. jan 24 15:22:15 main gnome-shell[4638]: Window manager warning: Invalid WM_TRANSI ENT_FOR window 0x1800007 specified for 0x18002e7. jan 24 15:22:20 main kernel: nxnode.bin[553542]: segfault at 0 ip 0000785dbfba721a sp 0000785dab7fd428 error 4 in libc.so.6[785dbfa28000+188000] likely on CPU 5 (core 1, socket 0) jan 24 15:22:20 main kernel: Code: 8b 04 82 29 c8 c3 66 2e 0f 1f 84 00 00 00 00 0 0 f3 0f 1e fa 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 3b 83 f8 30 77 36 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f jan 24 15:22:22 main nxexec[553821]: pam_unix(nx:session): session closed for user dan jan 24 15:22:22 main systemd[1]: session-c73.scope: Deactivated successfully. jan 24 15:22:22 main systemd-logind[2720]: Session c73 logged out. Waiting for processes to exit. jan 24 15:22:22 main nxexec[554047]: pam_unix(nx:session): session opened for user dan(uid=1000) by (uid=127) jan 24 15:22:22 main systemd-logind[2720]: Removed session c73
Problem is most probably in libnxdimi, because once I move it away, problem goes away (but then I can’t see the desktop, because it can not be detected):
sudo mv /usr/NX/lib/libnxdimi.so /usr/NX/lib/libnxdimi.so.disabled
I also did a gdb core backtrace for you:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp-sse4_2.S:173warning: 173 ../sysdeps/x86_64/multiarch/strcmp-sse4_2.S: No such file or directory
[Current thread is 1 (Thread 0x72c4755fd6c0 (LWP 793114))]
(gdb) bt
#0 __strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp-sse4_2.S:173
#1 0x000072c48365dc87 in MonitorConfiguratorGnome::getCoordinates(int, char const*, int*, int*) () at /usr/NX/lib/libnxdimi.so
#2 0x000072c48365936e in DrmGrabber::initFbInfo() () at /usr/NX/lib/libnxdimi.so
#3 0x000072c483659dd4 in DrmGrabber::init() () at /usr/NX/lib/libnxdimi.so
#4 0x000072c48363cb6a in WaylandPoller::setupGrabberObject() () at /usr/NX/lib/libnxdimi.so
#5 0x000072c48363fa3b in WaylandPoller::init() () at /usr/NX/lib/libnxdimi.so
#6 0x000072c483624092 in NXShadowInit () at /usr/NX/lib/libnxdimi.so
#7 0x000072c4864aa040 in nxagentShadowInit () at /usr/NX/lib/libnxdiag.so
#8 0x000072c486487b3b in nxagentShadowClientCallback () at /usr/NX/lib/libnxdiag.so
#9 0x000072c4831358ac in _CallCallbacks () at /usr/NX/lib/libnxdifb.so
#10 0x000072c48312e7bf in NextAvailableClient () at /usr/NX/lib/libnxdifb.so
#11 0x000072c483199710 in ??? () at /usr/NX/lib/libnxdifb.so
#12 0x000072c4831351cb in ProcessWorkQueue () at /usr/NX/lib/libnxdifb.so
#13 0x000072c4831a1af0 in WaitForSomething () at /usr/NX/lib/libnxdifb.so
#14 0x000072c48312ec8a in Dispatch () at /usr/NX/lib/libnxdifb.so
#15 0x000072c483152ca1 in dix_main () at /usr/NX/lib/libnxdifb.so
#16 0x000072c484a7a474 in ??? () at /usr/NX/lib/libnxc.so
#17 0x000072c485e9caa4 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:447
#18 0x000072c485f29c6c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78Can you please help me solving this?
January 27, 2026 at 17:11 #55357
BritgirlKeymasterHello, this looks similar to a Trouble Report already open, please take a look at the link here: https://kb.nomachine.com/TR01X11699. We can send you a test version with a possible fix implemented. Would you be willing to try it?
January 27, 2026 at 17:15 #55359
danergoParticipantHello @Britgirl, sorry for duplication, I didn’t find my earlier issue, hence I posted it again with more information and gdb logs.
Please go ahead and delete the other one for me if you can.
I took a quick look on your link, and it seems very similar if not the same issue as mine.
For the test version, yes please send it over, I’m willing to test it and get back with my results 🙂
January 29, 2026 at 17:03 #55381
BritgirlKeymasterCheck your inbox, I’ve just sent you an email with the link.
January 30, 2026 at 17:31 #55397
jdebisoParticipantI am having the same issue with MX Linux.
January 31, 2026 at 13:03 #55399
danergoParticipantDear Britgirl, the latest binary you’ve shared me fixed this issue.
Thank you very much!
One thing I don’t understand: my server has 2 displays (2* FHD 1920*1080), however the client sees them as one (3840*1080). Is there anything I can do with it?
February 2, 2026 at 13:33 #55422
BritgirlKeymasterHi, we are aware of an issue with multi-monitors not being detected in some cases and it will be fixed in the next update.
-
AuthorPosts
You must be logged in to reply to this topic. Please login here.
