Bug 513226

Summary: After installing KDE 6.5.4 on CachyOS a few days ago, the computer freezes when it is about to enter automatic sleep mode defined by time.
Product: [Plasma] plasmashell Reporter: Chema <rondo.sp>
Component: Power management & brightnessAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bshah, nate
Priority: NOR Keywords: regression
Version First Reported In: 6.5.4   
Target Milestone: 1.0   
Platform: CachyOS   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=513151
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: CachyOS log of 2025-12-11.

Description Chema 2025-12-11 17:36:45 UTC
Created attachment 187529 [details]
CachyOS log of 2025-12-11.

When the computer is about to enter scheduled sleep mode, PowerDevil displays an error message in the log and the system freezes, with the only option being to restart the computer:

11/12/25 17:58	org_kde_powerdevil	Error detecting VCP version using VCP feature xDF: Error_Info[EIO in ddc_write_read_with_retry, causes: DDCRC_READ_ALL_ZERO, DDCRC_DDC_DATA(2), EIO]
11/12/25 17:58	org_kde_powerdevil	[  1535] Error detecting VCP version using VCP feature xDF: Error_Info[EIO in ddc_write_read_with_retry, causes: DDCRC_READ_ALL_ZERO, DDCRC_DDC_DATA(2), EIO]

I've attached the log to this post.

It appears to be a regression error; my system was working perfectly until I installed KDE 6.5.4.

Here are my system details:

Operating System: CachyOS Linux 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.18.0-5-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
Memory: 64 GiB of RAM (59,7 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
Manufacturer: GMKtec
Product Name: NucBox K8 Plus
Comment 1 Nate Graham 2025-12-11 17:43:25 UTC
Symptoms sound a bit like Bug 513151, but the log output is different.
Comment 2 Chema 2025-12-11 17:56:25 UTC
Thanks Nate, I think it must be the same problem since my symptoms are exactly the same. I already replied to the other thread, so I'm marking this one as a duplicate since I think it all ultimately refers to the same issue, even though some log messages might be different.

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