rkward-devel Digest, Vol 86, Issue 12

[Anders Fridberger]

Hi Thomas
I actually enjoy the detective work 😊


1)

Thread 6 (Thread 0x7fffc491c700 (LWP 152261)):
#0  0x00007fffec48591d in syscall () at /lib64/libc.so.6
#1  0x00007fffed38df1c in forkfd_wait4 () at /lib64/libQt5Core.so.5
#2  0x00007fffed371f24 in QProcessPrivate::waitForDeadChild() () at /lib64/libQt5Core.so.5
#3  0x00007fffed36bfea in QProcessPrivate::_q_processDied() () at /lib64/libQt5Core.so.5
#4  0x00007fffed371a1e in QProcessPrivate::waitForReadyRead(int) () at /lib64/libQt5Core.so.5
#5  0x000000000062b725 in RKFrontendTransmitter::waitReadLine(QIODevice*, int) ()
#6  0x000000000062b493 in RKFrontendTransmitter::run() ()
#7  0x00007fffed229450 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#8  0x00007fffea5291cf in start_thread () at /lib64/libpthread.so.0
#9  0x00007fffec485dd3 in clone () at /lib64/libc.so.6


2)
I can't help thinking that it's a config/permissions issue, somehow. If
it isn't SELinux, perhaps its fapolicyd, or something?
I agree but I can’t find what that would be. SElinux would generate an access violation in the logs and there is nothing. And running with SElinux in permissive mode doesn’t help. Fapolicyd is not installed.


3)
I don't think it's a good idea as a "solution", but I intend to add a
"--quirkmode" option to allow to skip the handshake check. Essentially
to make sure, that the current problem is the "only" obstacle. Not sure,
whether I'll make that in time for the next AppImage build, but I'll
keep you posted.

4)
Once more thanks for your continued patience!

Regards
Thomas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20220803/ae8b0487/attachment.htm>