kdeconnectd segfaults

[mkoloberdin]

Not that it matters since it is easy to disable hax11 for it, but it might be interesting to investigate why it crashes.

Application: kdeconnectd (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f922cc63c80 (LWP 1261))]
...
Thread 1 (Thread 0x7f922cc63c80 (LWP 1261)):
[KCrash Handler]
#6  0x00007f9230100440 in xcb_get_property_value_length () from /usr/lib/libxcb.so.1
#7  0x00007f922c7d3f43 in QXcbNativeInterface::atspiBus() () from /usr/lib/libQt5XcbQpa.so.5
#8  0x00007f922c7d4bb9 in QXcbNativeInterface::nativeResourceForIntegration(QByteArray const&) () from /usr/lib/libQt5XcbQpa.so.5
#9  0x00007f922c86940a in ?? () from /usr/lib/libQt5XcbQpa.so.5
#10 0x00007f922c869c36 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#11 0x00007f922c85d489 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#12 0x00007f922c7b5d10 in QXcbIntegration::accessibility() const () from /usr/lib/libQt5XcbQpa.so.5
#13 0x00007f92329a2437 in QAccessible::setRootObject(QObject*) () from /usr/lib/libQt5Gui.so.5
#14 0x00007f92329caca4 in QGuiApplication::exec() () from /usr/lib/libQt5Gui.so.5
#15 0x000055bd0281112f in ?? ()
#16 0x00007f9232059223 in __libc_start_main () from /usr/lib/libc.so.6
#17 0x000055bd0281119e in _start ()
[Inferior 1 (process 1261) detached]

[CyberShadow]

With what hax11 settings?

[mkoloberdin]

Enable=1
Debug=0
JoinMST=1
MainX=0
MainY=0
MainW=5120
MainH=2880
DesktopW=5120
DesktopH=2880

[CyberShadow]

Can you check if it crashes with JoinMST=0, and then with Dumb=1 ?

[mkoloberdin]

Yes, it crashes in both cases.

[CyberShadow]

I assume you already tested with Enable=0 and it doesn't crash in that case.

If it crashes with Dumb=1 but not with Enable=0, it sounds like it's sending some non-data stuff through the pipe (via some side channel). The last time this happened, it was related to DRI, and I had to switch from send/recv to sendmsg / recvmsg. I'm not sure what else it might be though. That, or it's expecting the connection to be the real socket to the X server somehow.

Probably a simpler explanation is more likely. It does not crash with Enable=0, right?

[mkoloberdin]

Correct, with Enable=0 it works fine.

[CyberShadow]

I haven't been able to reproduce this, back then and now; I use kdeconnect too and have not seen this problem.

I'm going to close the issue but let's reopen if more details come up.