I am trying to initiate a remote Plasma session via X2Go but several crashes prevent Plasma from fully loading (e.g. no control panel). In dmesg, I see segfaults in kscreen_backend: [ 62.403979] kscreen_backend[2749]: segfault at 8 ip 00007fa77db17e83 sp 00007ffcd7be9b70 error 4 in KSC_XRandR.so[7fa77db00000+22000] [ 62.903996] kscreen_backend[2795]: segfault at 8 ip 00007f1f15b9fe83 sp 00007ffcef389b30 error 4 in KSC_XRandR.so[7f1f15b88000+22000] [ 62.941714] kscreen_backend[2811]: segfault at 8 ip 00007fc62e79be83 sp 00007fff8abf8f70 error 4 in KSC_XRandR.so[7fc62e784000+22000] [ 63.233484] kscreen_backend[2842]: segfault at 8 ip 00007fd3059f0e83 sp 00007ffcf12715c0 error 4 in KSC_XRandR.so[7fd3059d9000+22000] [ 187.681617] kactivitymanage[2754]: segfault at 7fcc7c03bc50 ip 00007fcc8b5ca071 sp 00007ffe917a2e38 error 4 in libQt5Sql.so.5.5.1[7fcc8b5b6000+3f000] Reproducible: Always Host (where Plasma is installed): Gentoo Linux Linux Kernel 4.2.6
Created attachment 95720 [details] systemd journal The systemd journal produced by journalctl -b. Search for "x2go" to find the start of the faulty Plasma session.
See also related bugs: Bug #353825 - Login by x2go in Plasma 5 crashes KCMInit Bug #355878 - Segfault in kactivitymanagerd
How can I get a full backtrace for those segfaults?
*** Bug 377388 has been marked as a duplicate of this bug. ***
I have a similar problem when I initiate a remote X2Go session dmesg output: [lun. nov. 20 14:13:22 2017] kscreen_backend[5644]: segfault at 8 ip 00007f2e671b04d7 sp 00007ffde41eef60 error 4 in KSC_XRandR.so[7f2e6719a000+23000] [lun. nov. 20 14:13:23 2017] kscreen_backend[5713]: segfault at 8 ip 00007f5032e964d7 sp 00007ffff5782870 error 4 in KSC_XRandR.so[7f5032e80000+23000] [lun. nov. 20 14:13:23 2017] kscreen_backend[5731]: segfault at 8 ip 00007f3be221e4d7 sp 00007ffee44a8650 error 4 in KSC_XRandR.so[7f3be2208000+23000] [lun. nov. 20 14:13:36 2017] kscreen_backend[5917]: segfault at 8 ip 00007fd0c62d24d7 sp 00007fff33fb4dd0 error 4 in KSC_XRandR.so[7fd0c62bc000+23000] [lun. nov. 20 14:13:36 2017] kscreen_backend[5923]: segfault at 8 ip 00007f13b52474d7 sp 00007ffcca5989b0 error 4 in KSC_XRandR.so[7f13b5231000+23000] Bat I can't see any error in journalctl -b nov. 21 09:47:18 jaden2 /usr/bin/x2gomountdirs[99599]: successfully mounted me@127.0.0.1:40050/home/me to /tmp/.x2go-me/media/disk/_home_me nov. 21 09:47:19 jaden2 /usr/bin/x2gosetkeyboard[99823]: Setting X keyboard according to /home/me/.x2go/C-me-50-1511254037_stDKDE_dp24/keyboard nov. 21 09:47:19 jaden2 /usr/bin/x2gomountdirs[99599]: successfully mounted me@127.0.0.1:40050/home/me/.x2go/S-me-50-1511254037_stDKDE_dp24/spool to /tmp/.x2go-me/spool/C-me-50-1511254037_stDKDE_dp24 nov. 21 09:47:19 jaden2 /usr/bin/x2goruncommand[99898]: launching session with Xsession-x2go mechanism, using STARTUP="startkde" nov. 21 09:47:19 jaden2 /usr/bin/x2goruncommand[99901]: dbus wrapper available as /usr/bin/dbus-run-session PS : When I try to logout, ksmserver and drkonqi crash as well (also a segfault for both). I don't know it's related Reproducible: Always Host: Debian Stretch Linux Kernel 4.9.0
Erratum: Actually, I can see the kscreen_backend segfault in journalctl -b sept. 19 11:20:23 $hostname kernel: kscreen_backend[101351]: segfault at 8 ip 00007fd1a6bda4d7 sp 00007ffd950e7280 error 4 in KSC_XRandR.so[7fd1a6bc4000+23000] It happens as soon as I login.
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!