Bug 477911 - Logout screen does not work correctly after KWin crash
Summary: Logout screen does not work correctly after KWin crash
Status: RESOLVED DUPLICATE of bug 449948
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-12-02 13:32 UTC by Жора Змейкин
Modified: 2023-12-03 02:48 UTC (History)
1 user (show)

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

Attachments
The screen recording was made after the KWIn crash. As you can see on it - the shutdown, reboot and so on buttons don't work. Only hibernation mode works (it made the video hang a bit) (1.61 MB, video/quicktime)
2023-12-02 13:32 UTC, Жора Змейкин 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Жора Змейкин 2023-12-02 13:32:50 UTC 
Created attachment 163759 [details]
The screen recording was made after the KWIn crash. As you can see on it - the shutdown, reboot and so on buttons don't work. Only hibernation mode works (it made the video hang a bit)

After a crash, KWin automatically restarts with plasmashell, but the logout screen stops working properly. Shutting down, rebooting, and logging out of a session do not work. Only hibernation works. Attached a video with a demonstration.

STEPS TO REPRODUCE
1. Crash KWin, e.g. by killing the process.
2. Invoke Logout Screen via the application menu or other convenient way.
3. Try shutting down or restarting the PC. Or log out of the session. Nothing will work.

OBSERVED RESULT
The buttons are not responsive in any way.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon (Unstable), Wayland
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0

ADDITIONAL INFORMATION
You can see everything in the video
Comment 1 Patrick Silva 2023-12-03 02:48:13 UTC 

*** This bug has been marked as a duplicate of bug 449948 ***