| Summary: | kscreen backend crash | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | Samuel Bernardo <samuelbernardo.mail> |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | crash | CC: | b2c, kde, nate, sitter |
| Priority: | NOR | ||
| Version: | 5.26.3 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kwin crash
backtrace frombacktrace-kscreen_backend.txt kscreen_backend backtrace from KDE 5.26 / 2022-11-20 3 display screen layout and configuration |
||
|
Description
Samuel Bernardo
2022-01-22 19:03:22 UTC
I have the same issue with linux 5.15.16 and nvidia-drivers 5.10.93. when I try to log in with SDDM, kwin segfaults: [Tue Jan 25 15:20:04 2022] kscreen_backend[6550]: segfault at 8 ip 00007f06e0e583cd sp 00007ffd4535baf0 error 4 in KSC_XRandR.so[7f06e0e55000+19000] I opened a similar bug report (and some more logs) here: https://bugs.gentoo.org/831846 >Application: KWin (kwin_x11), signal: Segmentation fault
[KCrash Handler]
#4 0x00007f1e69ced425 in KWin::Workspace::initializeX11() [clone .cold] () from /usr/lib64/libkwin.so.5
Missing symbols
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! Created attachment 147868 [details] backtrace frombacktrace-kscreen_backend.txt Sorry for the late follow up, real life happened and I just now finally set up my system for debugging. I managed to get a crashdump from /usr/lib64/libexec/kf5/kscreen_backend_launcher which seems to be the binary causing the crash in the first place. Took me a while to figure that out, not used to stuff like this. I attached the full backtrace as text to the issue now, maybe you guys can take another look and make something of it? PS: I updated the gentoo bug at https://bugs.gentoo.org/832047 as well, not sure where the root cause is to be found. Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please see if you can reproduce the issue with Plasma 5.25 or 5.26? If you can, please change the status to CONFIRMED when replying. Thanks a lot! Created attachment 153904 [details]
kscreen_backend backtrace from KDE 5.26 / 2022-11-20
Created attachment 153905 [details]
3 display screen layout and configuration
Hi Nate, thanks for checking in, and again apologies for the late reply. So I just got back to testing this on the latest KDE 5.26.3 and the crash still happens for me. I uploaded a new backtrace, and also a screenshot with my display configuration, since I run 3x 27" displays in a non-standard layout - maybe this contributes to the problem I'm experiencing? Anyways here are my package configurations and versions: x11-base/xorg-drivers-21.1-r1::gentoo INPUT_DEVICES="evdev libinput -elographics -joystick -synaptics -vmmouse -void -wacom" VIDEO_CARDS="nvidia vesa -amdgpu -ast -dummy -fbdev (-freedreno) (-geode) -i915 -intel -mga -nouveau (-nv) (-omap) -qxl -r128 -radeon -radeonsi -siliconmotion (-tegra) (-vc4) -via -virtualbox -vmware (-glint%) (-i965%)" x11-base/xorg-server-21.1.4:0/21.1.4::gentoo USE="elogind udev unwind xcsecurity xorg -debug -minimal (-selinux) -suid -systemd -test -xephyr -xnest -xvfb (-dmx%) (-kdrive%)" x11-drivers/xf86-input-evdev-2.10.6::gentoo x11-drivers/xf86-input-libinput-1.2.1::gentoo x11-drivers/xf86-video-vesa-2.5.0::gentoo kde-plasma/libkscreen-5.26.3:5/7::gentoo USE="-debug -doc -test" kde-plasma/kwin-5.26.3:5::gentoo USE="lock plasma -accessibility -caps -debug -gles2-only -handbook -multimedia -screencast -test" kde-plasma/kscreen-5.26.3:5::gentoo USE="-debug -test" x11-libs/libXrandr-1.5.2::gentoo USE="-doc" ABI_X86="32 (64) (-x32)" dev-qt/qtcore-5.15.5-r3:5/5.15.5::gentoo USE="icu -debug -old-kernel -systemd -test" dev-qt/qtdbus-5.15.5-r1:5/5.15::gentoo USE="-debug -test" Thanks and all the best! Additionally I see this in dmesg: Nov 20 14:48:30 born2chill kernel: [ 26.072392][T13609] kscreen_backend[13609]: segfault at 8 ip 00007f984582141d sp 00007ffe7adeb450 error 4 in KSC_XRandR.so[7f984581e000+19000] Nov 20 14:48:30 born2chill kernel: [ 26.072407][T13609] Code: 00 00 00 4c 8b 60 10 8b 58 04 49 01 c4 e8 3b 28 01 00 0f b7 d3 31 f6 48 89 c7 4c 89 e1 e8 9b d4 ff ff 89 44 24 1c 85 c0 75 13 <8b> 04 25 08 00 00 00 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 e8 0b 28 Nov 20 14:48:30 born2chill kernel: [ 26.072434][ T8020] kactivitymanage[8020]: segfault at c ip 00007f39bf941101 sp 00007ffca9ee8690 error 4 in libQt5XcbQpa.so.5.15.5[7f39bf909000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072443][ T6867] kaccess[6867]: segfault at c ip 00007f4f42f6b101 sp 00007ffc265fed00 error 4 Nov 20 14:48:30 born2chill kernel: [ 26.072447][ T8020] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072460][ T6867] in libQt5XcbQpa.so.5.15.5[7f4f42f33000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072465][ T6867] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072494][ T5008] kwalletd5[5008]: segfault at c ip 00007fb59b18e101 sp 00007ffc86070890 error 4 in libQt5XcbQpa.so.5.15.5[7fb59b156000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072508][ T5008] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072521][ T6056] ksmserver[6056]: segfault at c ip 00007fc78ea43101 sp 00007ffdd8774380 error 4 Nov 20 14:48:30 born2chill kernel: [ 26.072526][ T7591] gmenudbusmenupr[7591]: segfault at c ip 00007fa916742101 sp 00007ffdf7b531f0 error 4 in libQt5XcbQpa.so.5.15.5[7fa91670a000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072541][ T6056] in libQt5XcbQpa.so.5.15.5[7fc78ea0b000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072545][ T7591] Nov 20 14:48:30 born2chill kernel: [ 26.072545][ T6056] Nov 20 14:48:30 born2chill kernel: [ 26.072548][ T6056] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072548][ T7591] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072751][ T6871] xembedsniproxy[6871]: segfault at c ip 00007f3e07f48101 sp 00007ffefe0983c0 error 4 in libQt5XcbQpa.so.5.15.5[7f3e07f10000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072763][ T6871] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Also I just noticed that other crashdumps have been generated too - if you need a backtrace from any of them please let me know: Crashdumps: ------------------- core-gmenudbusmenupr.7591.1668952110 core-kaccess.6867.1668952110 core-kactivitymanage.8020.1668952110 core-kded5.16071.1668952111 core-kded5.5994.1668952111 core-kglobalaccel5.16068.1668952111 core-kglobalaccel5.6028.1668952111 core-klauncher.5449.1668952110 core-kscreen_osd_ser.15892.1668952110 core-ksmserver.6056.1668952110 core-kwalletd5.5008.1668952110 core-org_kde_powerde.16069.1668952111 core-org_kde_powerde.6870.1668952111 core-plasmashell.6869.1668952111 core-xembedsniproxy.6871.1668952110 Please stop moving the bug back to KScreen. >Please stop moving the bug back to KScreen.
It's a kscreen backtrace with a bad title
The original bug report and backtrace were from KWin; now we have a KScreen one too, so I'm confused now because this bug report her morphed into something trying to report two different crashes. Samuel, now that this is a KScreen bug, can you file a new bug report for the original KWin crash, if you can still reproduce it? |