https://bugs.kde.org/show_bug.cgi?id=482713
--- Comment #91 from Ambareesh Balaji <[email protected]> --- Actually upon further inspection it seems powerdevil does already exit with a nonzero exit code of 1, at least on the latest master commit: ``` (ddc_open_display ) Assertion failed: "bus_info" in file ddc_packet_io.c at line 308 QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread QtDBus: cannot relay signals from parent QObject(0x55e5667c00b0 "") unless they are emitted in the object's thread QThread(0x55e5666f08f0 "Qt mainThread"). Current thread is QThread(0x55e56679b2d8 ""). QMutex: destroying locked mutex (i2c_close_bus ) Unexpected error DDCRC_LOCKED from unlock_display_by_dpath(Display_Path[/dev/i2c-4]) ~/code/powerdevil master* 10h 10m 46s ❯ echo $? 1 ``` I had this happen on 6.3.5, but maybe since then there has been a change that adjusts the exit code, because i'm pretty sure systemd's Restart=on-failure should work if that is the case. I'll see if 6.4.0 helps with. -- You are receiving this mail because: You are watching all bug changes.
