Bug 480046 - Powerdevil stuck in infinite crash/reboot loop after update
Summary: Powerdevil stuck in infinite crash/reboot loop after update
Status: RESOLVED DUPLICATE of bug 480030
Alias: None
Product: Powerdevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.27.10
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-19 14:18 UTC by aquova
Modified: 2024-01-19 16:44 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aquova 2024-01-19 14:18:30 UTC
Last night, I updated my Arch Linux machine in the usual fashion which included an update of the powerdevil package to version 5.27.10-2, then proceeded to power off for the night. Upon booting up this morning, I quickly noticed that the KDE crash report tray widget was repeatedly, and rather quickly, appearing and disappearing. From what I can tell, /usr/lib/org_kde_powerdevil is starting up, crashing, and attempting to start up again, causing strain on the system. Attempting to use the Power Management menus in the systems UI confirms that it is not loaded. The KDE Crash Handler also is closing and reopening quickly, making it difficult to get any diagnostic information through it. I've included my entire "journalctl -b 0" output in the hopes that it's useful. I can attempt to get better dumps/stack traces if someone can point me to them. I typically use Wayland, but did switch to X11 as a test and was still seeing the same issue. My only other idea is to switch to an LTS kernel, which I will do after this and report back. I have not installed any new hardware in some time.

STEPS TO REPRODUCE
1. Boot up the system

OBSERVED RESULT
Powerdevil is stuck in an infinite boot loop

EXPECTED RESULT
Powerdevil will start up normally

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux KDE Plasma Wayland - Kernel 6.7.0-arch3-1
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12
Comment 1 aquova 2024-01-19 14:28:42 UTC
(In reply to aquova from comment #0)
> Last night, I updated my Arch Linux machine in the usual fashion which
> included an update of the powerdevil package to version 5.27.10-2, then
> proceeded to power off for the night. Upon booting up this morning, I
> quickly noticed that the KDE crash report tray widget was repeatedly, and
> rather quickly, appearing and disappearing. From what I can tell,
> /usr/lib/org_kde_powerdevil is starting up, crashing, and attempting to
> start up again, causing strain on the system. Attempting to use the Power
> Management menus in the systems UI confirms that it is not loaded. The KDE
> Crash Handler also is closing and reopening quickly, making it difficult to
> get any diagnostic information through it. I've included my entire
> "journalctl -b 0" output in the hopes that it's useful. I can attempt to get
> better dumps/stack traces if someone can point me to them. I typically use
> Wayland, but did switch to X11 as a test and was still seeing the same
> issue. My only other idea is to switch to an LTS kernel, which I will do
> after this and report back. I have not installed any new hardware in some
> time.
> 
> STEPS TO REPRODUCE
> 1. Boot up the system
> 
> OBSERVED RESULT
> Powerdevil is stuck in an infinite boot loop
> 
> EXPECTED RESULT
> Powerdevil will start up normally
> 
> SOFTWARE/OS VERSIONS
> Linux/KDE Plasma: Arch Linux KDE Plasma Wayland - Kernel 6.7.0-arch3-1
> KDE Plasma Version: 5.27.10
> KDE Frameworks Version: 5.114.0
> Qt Version: 5.15.12

Attempting to switch to the LTS kernel showed no changed. I've had to switch to a different DE for the time being, but I can attempt to assist in debugging if need be.
Comment 2 Dankity Mao 2024-01-19 16:10:52 UTC
(In reply to aquova from comment #1)
> (In reply to aquova from comment #0)
> > Last night, I updated my Arch Linux machine in the usual fashion which
> > included an update of the powerdevil package to version 5.27.10-2, then
> > proceeded to power off for the night. Upon booting up this morning, I
> > quickly noticed that the KDE crash report tray widget was repeatedly, and
> > rather quickly, appearing and disappearing. From what I can tell,
> > /usr/lib/org_kde_powerdevil is starting up, crashing, and attempting to
> > start up again, causing strain on the system. Attempting to use the Power
> > Management menus in the systems UI confirms that it is not loaded. The KDE
> > Crash Handler also is closing and reopening quickly, making it difficult to
> > get any diagnostic information through it. I've included my entire
> > "journalctl -b 0" output in the hopes that it's useful. I can attempt to get
> > better dumps/stack traces if someone can point me to them. I typically use
> > Wayland, but did switch to X11 as a test and was still seeing the same
> > issue. My only other idea is to switch to an LTS kernel, which I will do
> > after this and report back. I have not installed any new hardware in some
> > time.
> > 
> > STEPS TO REPRODUCE
> > 1. Boot up the system
> > 
> > OBSERVED RESULT
> > Powerdevil is stuck in an infinite boot loop
> > 
> > EXPECTED RESULT
> > Powerdevil will start up normally
> > 
> > SOFTWARE/OS VERSIONS
> > Linux/KDE Plasma: Arch Linux KDE Plasma Wayland - Kernel 6.7.0-arch3-1
> > KDE Plasma Version: 5.27.10
> > KDE Frameworks Version: 5.114.0
> > Qt Version: 5.15.12
> 
> Attempting to switch to the LTS kernel showed no changed. I've had to switch
> to a different DE for the time being, but I can attempt to assist in
> debugging if need be.

This appears to be related to the recent release of ddcutil 2.1.0, not a kernel change, and is similar to https://bugs.kde.org/show_bug.cgi?id=476375 -- downgrading to ddcutil 2.0.0 is a temporary fix until this is addressed.  For Arch, "sudo pacman -U https://archive.archlinux.org/packages/d/ddcutil/ddcutil-2.0.0-1-x86_64.pkg.tar.zst" will take you back.
Comment 3 Nicolas Fella 2024-01-19 16:44:08 UTC

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