Created attachment 171831 [details] Kcrash file SUMMARY STEPS TO REPRODUCE 1. Start `Xnest -listen tcp :1` on linux desktop 1 (192.168.100.24) and allow connections with `xhost +` command 2. Login to console on linux desktop 2 3. run `export DISPLAY=192.168.100.24:1` on linux desktop 2 4. run `startplasma-x11` on linux desktop 2 5. Plasma starts to run, but crashes with segfault during start OBSERVED RESULT 1. Segfault with dialog about crash which allows to send report 2. Second, third, etc, dialog windows appearing every few seconds, looks like Plasma tries to start again and fails EXPECTED RESULT Plasma works over TCP connection SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Linux: 6.9.9-amd64 (64-bit) Xnest server: 21.1.12-1
Thread 1 (Thread 0x7f2d3b2006c0 (LWP 2748)): [KCrash Handler] #5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #6 0x00007f2d400a6b6f in __pthread_kill_internal (signo=11, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 #7 0x00007f2d400584e2 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #8 <signal handler called> #9 0x00007f2d4011947f in __GI___poll (fds=0x7f2d3b1ffac8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #10 0x00007f2d42cf7d82 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #11 0x00007f2d42cfa14a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #12 0x00007f2d3b8f8128 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #13 0x00007f2d406db141 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007f2d400a4dab in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444 #15 0x00007f2d401269f8 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Doesn't look like any of our code is involved. Regardless, this isn't a use case we formally support. It may work and it may not, but we offer no guarantees. We'll be happy to accept a patch to fix it, but won't consider it in scope to track as a bug report as it's out of what we support. Thanks for understanding!