Bug 483804 - kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X
Summary: kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AM...
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: 6.0.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-17 01:11 UTC by Musikolo
Modified: 2024-04-06 15:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kwin_wayland command on X11 + coredump + lspci + lsmod outputs (8.74 KB, application/zip)
2024-03-17 01:11 UTC, Musikolo
Details
coredumpctl gdb bt content (8.91 KB, application/zip)
2024-03-23 01:07 UTC, Musikolo
Details
coredumpctl backtrade 2nd attempt (17.47 KB, text/x-log)
2024-03-24 15:35 UTC, Musikolo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Musikolo 2024-03-17 01:11:31 UTC
Created attachment 167356 [details]
kwin_wayland command on X11 + coredump + lspci + lsmod outputs

SUMMARY
When logging in to SDDM with Wayland,  it crashes. If I enabled SDDM to use kwin_wayland, it crashes too. When I logging in to Plasma 6 in X11 and launch a wayland window, it crashes too.

STEPS TO REPRODUCE
1. Start SDDM in X11
2. Log in to Plasma 6
3. From a shell run the commands:  export $(dbus-launch); kwin_wayland --xwayland

OBSERVED RESULT
A Segmentation fault error occurs.

EXPECTED RESULT
It should display something in Wayland.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: yes
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Attached files with as much information as possible. If anything thing is needed, I'll be happy to help.
Comment 1 Nicolas Fella 2024-03-17 13:56:05 UTC
Please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to get a proper backtrace for the crash and past it here
Comment 2 Musikolo 2024-03-23 01:07:42 UTC
Created attachment 167634 [details]
coredumpctl gdb bt content
Comment 3 Musikolo 2024-03-23 01:12:22 UTC
Backtrace provided as indicated in the given link. I attached 2 file in the last zip file, one with debug info, and another without.

I hope that contains the info you need to squeeze this miserable bug!

If anything else is needed, I'll be happy to help.

Thanks!
Comment 4 Nicolas Fella 2024-03-23 11:06:11 UTC
In the file with debug symbols the step of running 'bt' to actually show the backtrace is missing. Can you please do that?
Comment 5 Musikolo 2024-03-24 15:35:59 UTC
Created attachment 167703 [details]
coredumpctl backtrade 2nd attempt

I hope I got what you need this time. Please let me know what I'm missing, if you still didn't get what you need.

Thanks.
Comment 6 Musikolo 2024-04-06 15:31:16 UTC
I've been trying out different things, and I found solution for my issue. I was using mesa-amber because mesa wasn't working for me since version 22.00. For some reason, the newer mesa drivers were causing my screen get out of sync and we could see nothing in SDDM. Today, I've been testing different options, and I found the problem was that, for some reason, my primary graphic device was i915 (intel) rather than radeonsi. I also found the radeonsi driver is not available in mesa-amber. So, I upgraded to mesa and switched the devices. I restarted and I could use SDDM with Wayland. From there, I can log in to Plasma with kwin_wayland. So, I'm marking this bug as resolved. I'll add new notes if I find something else others could get advantage of.

As always, thanks for the great work you're doing!
Comment 7 Musikolo 2024-04-06 15:38:19 UTC
One last thing, I forgot to add the following. My laptop only works with X11 (SDDM + Plasma) with mesa-amber (classic drivers), while for Wayland (SDDM + Plasma), it only works with mesa (newer drivers). Really weird and a huge source of confusion, at least for me, but it is the way it is.

Thanks again!