Bug 513050

Summary: Powerdevil causes random system reboot
Product: [Plasma] plasmashell Reporter: Roby <kde>
Component: Power management & brightnessAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: kde
Priority: NOR    
Version First Reported In: 6.5.3   
Target Milestone: 1.0   
Platform: EndeavourOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Roby 2025-12-07 16:30:24 UTC
SUMMARY

Ever since buying a new monitor, I have had the problem that occasionally the system will instantly reboot itself without warning, usually just when I am reading a webpage, scrolling and clicking etc.

In the journalctl logs whenever this happens I always see this at the exact moment of the reboot:

> org_kde_powerdevil[1449]: [  1449] busno=5, All features that should not exist detected. Monitor does not indicate unsupported

Is there any more information on what this error means? Is it trying to do something related to power management with this monitor and failing? Shouldn't it fail gracefully without causing the entire system to instantly reboot?

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 4070 SUPER/PCIe/SSE2
Graphics Processor 2: NVIDIA GeForce RTX 4070 SUPER/PCIe/SSE2

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2025-12-08 12:13:29 UTC
The message itself is from ddcutil. Hopefully that helps a bit. There is a way to disable ddcutil if you need a shortterm workaround. 

Set this environment variable: POWERDEVIL_NO_DDCUTIL=1

>Shouldn't it fail gracefully without causing the entire system to instantly reboot?

Yes, but there is nothing indicating our code is causing that.  It'll most likely be the kernel. 
It could be both ddcutil and something else react to the same event, or ddcutil is triggering a kernel bug. 

If you do still believe it's us, add
QT_LOGGING_RULES=org.kde.powerdevil.debug=true  to your env before powerdevil and that will enable more logs.