Bug 482120 - Unable to shut down or restart KDE neon from plasma
Summary: Unable to shut down or restart KDE neon from plasma
Status: RESOLVED DUPLICATE of bug 481938
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-01 07:53 UTC by BOF
Modified: 2024-03-01 08:33 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
no restart or shutdown action performed (1.40 MB, video/webm)
2024-03-01 07:53 UTC, BOF
Details

Note You need to log in before you can comment on or make changes to this bug.
Description BOF 2024-03-01 07:53:19 UTC
Created attachment 166235 [details]
no restart or shutdown action performed

SUMMARY
Since the update to KDE 6.0 (from 5.27) the buttons to shut down or restart the system do no longer work. When I press the power button (it's left at the default behaviour of starting the fullscreen shutdown menu) the shutdown menu does not appear.


STEPS TO REPRODUCE
1. Try to restart or shut down the system

OBSERVED RESULT
KDE neon does just nothing. The buttons can be clicked, but neither a restart not a shutdown are triggered.
When the power button (with default settings) are pressed, the shutdown menu is not displayed.

EXPECTED RESULT
The OS performs the restart or shutdown action as ordered to do so.
When the power button is pressed, the shutdown menu is displayed.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Micro-Star International Co., Ltd.
Product Name: Bravo 17 A4DDR
System Version: REV:1.0

ADDITIONAL INFORMATION
A restart via the terminal ("reboot") works.
Comment 1 Titouan Camus 2024-03-01 07:59:57 UTC

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