Bug 32942 - Since powerdevil-6.0.0-1.mga10 the power management is very unstable
Summary: Since powerdevil-6.0.0-1.mga10 the power management is very unstable
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-07 11:42 CET by Marja Van Waes
Modified: 2024-03-07 15:33 CET (History)
0 users

See Also:
Source RPM: powerdevil-6.0.0-1.mga10
CVE:
Status comment:


Attachments
output of journalctl -b | grep power (4.20 KB, text/plain)
2024-03-07 11:42 CET, Marja Van Waes
Details

Description Marja Van Waes 2024-03-07 11:42:00 CET
Created attachment 14437 [details]
output of journalctl -b | grep power

Since powerdevil and many more KDE packages were updated, my laptop is insanely switching between loading the battery and unloading at a very high pace. I loads stably before starting Mageia

After the update, I had:

[marja@localhost ~]$ rpm -qa | grep powerdevil
lib64powerdevilui5-5.27.9-1.mga10
lib64powerdevilconfigcommonprivate5-5.27.9-1.mga10
lib64powerdevilcore2-6.0.0-1.mga10
lib64powerdevilconfigcommonprivate6-6.0.0-1.mga10
powerdevil-6.0.0-1.mga10
[marja@localhost ~]$

There is no lib64powerdevilui6 available

After removing lib64powerdevilconfigcommonprivate5 and rebooting, the problem persisted.

In my journal logs, I see that org_kde_powerdevil crashed. I'll attach the output of "journalctl -b | grep power"

mrt 07 10:53:30 localhost org_kde_powerdevil[7962]: KCrash: Attempting to start /usr/libexec/org_kde_powerdevil
mrt 07 10:53:30 localhost org_kde_powerdevil[7962]: KCrash: Application 'org_kde_powerdevil' crashing... crashRecursionCounter = 2
Marja Van Waes 2024-03-07 11:42:45 CET

Assignee: bugsquad => kde
Source RPM: (none) => powerdevil-6.0.0-1.mga10

Comment 1 Marja Van Waes 2024-03-07 15:33:02 CET
Never mind, now the problem already occurs when starting Grub2, so before starting Mageia. 

Nothing changed in /boot and /boot/grub2 since long before the recent KDE update.

So whatever causes this, it wasn't Mageia

Closing

Resolution: (none) => INVALID
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.