https://bugs.kde.org/show_bug.cgi?id=482713
Ambareesh Balaji <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #89 from Ambareesh Balaji <[email protected]> --- ddcutil 2.2.1 did not fix it, it just moved the assert to a new line number 308 ``` Jun 18 19:55:35 evo org_kde_powerdevil[78816]: [ 79012] Assertion failed: "bus_info" in file ddc_packet_io.c at line 308 Jun 18 19:55:35 evo org_kde_powerdevil[78816]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread Jun 18 19:55:35 evo org_kde_powerdevil[78816]: QtDBus: cannot relay signals from parent QObject(0x556680f25150 "") unless they are emitted in the object's thread QThread(0x556680ed58e0 "Qt mainThread"). Current thread is QThread(0x556680f475b8 ""). Jun 18 19:55:35 evo org_kde_powerdevil[78816]: [ 79012] Watch thread terminated. Jun 18 19:55:35 evo org_kde_powerdevil[78816]: QMutex: destroying locked mutex Jun 18 19:55:35 evo systemd[1008]: plasma-powerdevil.service: Consumed 3.894s CPU time, 8.9M memory peak. Jun 18 19:58:40 evo systemd[1008]: Starting Powerdevil... ``` The problem is the systemd service for powerdevil is configured to only restart on failure (non-zero exit code), in the above log i manually restart the service. Powerdevil should fail loudly to indicate to systemd that it should be restarted automatically upon the assertion failure as a stopgap until upstream figures it out -- You are receiving this mail because: You are watching all bug changes.
