Bug 488900

Summary: Kwin_wayland segfault on latest KDE update
Product: [Plasma] kwin Reporter: Gurshaan Tiwana <gurshaantiwana6>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: critical CC: xaver.hugl
Priority: NOR    
Version First Reported In: 6.1.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: The attached pdf has photos showing the outtput of journalctl, DMESG, lscpu and uname.
Coredumpctl --reverse
Output of trying to start kwin wayland.
Coredumpctl --reverse output after trying to start wayland
Coredump gdb ( of plasmashell). If you need this for any other app, just tell me.

Description Gurshaan Tiwana 2024-06-21 14:47:40 UTC
Created attachment 170756 [details]
The attached pdf has photos showing the outtput of journalctl, DMESG, lscpu and uname.

I am on fedora 40(KDE spin) and at kernel 6.9.4-200. I am pretty noob and new to Linux.
I am running Linux on AMD A8 pro 7600B R7.

My PC was working fine until, I updated it yesterday (June 21, 2024) via dnf. When I rebooted the GUI part had stopped working. All that I could see was a cursor flashing on the black screen. I looked upon the internet but could find any solution. I came across a fedora forum where a person has the same problem. The link to that forum is provided in the URL section of bug or 

https://forums.fedoraforum.org/showthread.php?332835-kwin-wayland-sddm

I got access to the tty2 via Alt+ctrl+F2 and got the logs, according to which the Kwin Wayland segfault. I have attached the pictures of the logs in the attachments.

Also,
According to the other person who also has same issue says that this issue is happening on the piledriver cpu.


Reproducible: Always

Steps to Reproduce:
Rebooting after updating to the latest version on fedora 40(KDE spin)
Actual Results:  
The GUI is not working (KWIN). A blank screen with flashing cursor appears.


This is the kwin_wayland error shown in DMESG.

[ 79.019104] kwin_wayland[1008]: segfault at 0 ip 0000000000000000 sp 00007ffd15b0b268 error 14 in kwin_wayland[55b853f93000+38000] likely on CPU 0 (core 0, socket 1)



SOFTWARE/OS VERSIONS

Linux/KDE Plasma: fedora 40, kernel: 6.9.4-200
(available in About System)
KDE Plasma Version: 6.1

ADDITIONAL INFORMATION
I have also filed a report in the redhat bugzilla : https://bugzilla.redhat.com/show_bug.cgi?id=2293604
Comment 2 Gurshaan Tiwana 2024-06-21 15:36:00 UTC
(In reply to Zamundaaa from comment #1)
> Please get a backtrace for the crash:
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

the output of coredumpctl --reverse has been added in attachments. Please tell me the pid of which you want the backtrace.
Comment 3 Gurshaan Tiwana 2024-06-21 15:39:49 UTC
Created attachment 170758 [details]
Coredumpctl --reverse
Comment 4 Zamundaaa 2024-06-21 15:55:58 UTC
Usually the latest one, but the coredumps are inaccessible... that's really weird.
Can you start a Plasma session manually, from the tty? So does either
> startplasma-wayland
or
> kwin_wayland -- plasmashell
work, or at least produce a coredump?
Comment 5 Gurshaan Tiwana 2024-06-21 16:05:06 UTC
(In reply to Zamundaaa from comment #4)
> Usually the latest one, but the coredumps are inaccessible... that's really
> weird.
> Can you start a Plasma session manually, from the tty? So does either
> > startplasma-wayland
> or
> > kwin_wayland -- plasmashell
> work, or at least produce a coredump?

The command    startplasma-wayland  made the display turn on and off.
The command.      kwin_wayland -- plasmashell   just gave error.

These commands generated the coredump. 
The output of these 2 commands is attached in attachments.
The output of coredumpctl --reverse is also attached.
Comment 6 Gurshaan Tiwana 2024-06-21 16:07:20 UTC
Created attachment 170759 [details]
Output of trying to start kwin wayland.
Comment 7 Gurshaan Tiwana 2024-06-21 16:10:45 UTC
Created attachment 170760 [details]
Coredumpctl --reverse output after trying to start wayland
Comment 8 Gurshaan Tiwana 2024-06-21 18:00:22 UTC
Created attachment 170766 [details]
Coredump gdb ( of plasmashell). If you need this for any other app, just tell me.
Comment 9 Gurshaan Tiwana 2024-06-21 18:03:10 UTC
(In reply to Gurshaan Tiwana from comment #8)
> Created attachment 170766 [details]
> Coredump gdb ( of plasmashell). If you need this for any other app, just
> tell me.

I am unable to produce the coredump for kwin_wayland
Comment 10 Bug Janitor Service 2024-07-06 03:47:26 UTC
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!
Comment 11 Bug Janitor Service 2024-07-21 03:46:28 UTC
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!