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)
Created attachment 2037915 [details] The attached pdf file has the photos having output of journalctl, DMESG, lscpu and uname.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.