saips

[saips]

Hi @fra81,

sorry for the late answer, the notifications mails did not seem to work.

I did a fresh install on the same system and then it worked. So it’s not a NoMachine issue but related to xorg. Nevertheless, thanks for the help.

 

I’m now on: X.Org X Server 1.18.4

[saips]

@fra81

I don’t know on which Xorg version the problem started, but after upgrading to:

X.Org X Server 1.18.4
xorg-server 2:1.18.4-0ubuntu0.7
xserver-xorg-video-intel (2:2.99.917+git20160325-1ubuntu1.2)

the problem still existed.

~ $ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt Microsoft USB Optical Mouse id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ Microsoft Wired Keyboard 400 id=10 [slave keyboard (3)]
↳ Eee PC WMI hotkeys id=12 [slave keyboard (3)]

Also, I can confirm that the problem does not exist on fresh installations.

[saips]

Thanks Britgirl and sorry for the delay. Finally found time to dig deeper.

Here’s what I got as soon as I closed the NoMachine player:

Thread 1 “Xorg” received signal SIGSEGV, Segmentation fault.

0x0000556d576b8feb in DeviceFocusEvents (mode=2, to=0x1, from=0x556d58a20270,

dev=0x556d58c5a970) at ../../dix/enterleave.c:1462

1462    ../../dix/enterleave.c: No such file or directory.

 

The stacktrace of gdb’s “bt f” is attached. Anything else I can do?

Attachments:

1. gdb.txt

[saips]

So I updated to Mint 18.3 today incl. new xorg versions, but the issue is still there:

X.Org X Server 1.18.4

xorg-server 2:1.18.4-0ubuntu0.7

xserver-xorg-video-intel (2:2.99.917+git20160325-1ubuntu1.2)

inxi -G:

Graphics:  Card: Intel Sky Lake Integrated Graphics

Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)

Resolution: 1920×1080@60.00hz, 1920×1080@60.00hz

GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2)

GLX Version: 3.0 Mesa 17.2.8

 

and the same error:

(EE) Backtrace:

(EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5628b1ac36ce]

(EE) 1: /usr/lib/xorg/Xorg (0x5628b1911000+0x1b6a69) [0x5628b1ac7a69]

(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f84d5def000+0x354b0) [0x7f84d5e244b0]

(EE) 3: /usr/lib/xorg/Xorg (0x5628b1911000+0x5afeb) [0x5628b196bfeb]

(EE) 4: /usr/lib/xorg/Xorg (0x5628b1911000+0x644e7) [0x5628b19754e7]

(EE) 5: /usr/lib/xorg/Xorg (0x5628b1911000+0x14bb32) [0x5628b1a5cb32]

(EE) 6: /usr/lib/xorg/Xorg (0x5628b1911000+0x53d9f) [0x5628b1964d9f]

(EE) 7: /usr/lib/xorg/Xorg (0x5628b1911000+0x57e13) [0x5628b1968e13]

(EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f84d5e0f830]

(EE) 9: /usr/lib/xorg/Xorg (_start+0x29) [0x5628b1953069]

(EE)

(EE) Segmentation fault at address 0x28

(EE)

Fatal server error:

(EE) Caught signal 11 (Segmentation fault). Server aborting

 

 

I removed ‘xserver-xorg-video-intel’ and “inxi -G” now shows:

Graphics:  Card: Intel Sky Lake Integrated Graphics

Display Server: X.Org 1.18.4 drivers: (unloaded: fbdev,vesa)

Resolution: 1920×1080@60.00hz, 1920×1080@60.00hz

GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2)

GLX Version: 3.0 Mesa 17.2.8

but the issue still exists. Also tried creating a config in /etc/X11/xorg.conf.d/20-intel.conf with the following content to use uxa:

Section “Device”

Identifier  “Intel Graphics”

Driver      “intel”

Option      “AccelMethod”  “uxa”

Option      “TearFree”     “true”

EndSection

 

Mint then shows a warning that it’s running in software rendering mode, but that also did not solve it and I still get the same seg fault.

[saips]

Hi kroy,

I deleted the logfiles before reproducing, so there’s only 1 file (Xorg.0.log). Nothing pops up there, so I searched a bit further…

There’s logs in /var/log/mdm which contained errors (attached as var-log-mdm.tar.zg),

“Segmentation fault at address 0x28”

and as some other guys on the web, I also have an intel (i7-6700k) with onboard graphics (HD530 iirc)

So I’m no longer sure that NoMachine can help me with this issue.

However, I don’t have any other issues whatsoever, only when using NoMachine and reconnecting after a session with “lock physical screen” checked.

Maybe it’s worth mentioning that I have the option to resize client resolution checked and both 2 screens are set at 1920×1080 – the same as the physical screens at work and at home.

 

Any ideas?

Attachments:

1. var-log-mdm.tar.gz

[saips]

Thank you, I’ve just sent over the logs.

This issue did not exist when I first installed NoMachine on that desktop ~2 years ago, so I’m not sure if/which package or software update might have caused it.

[Author]

Posts