You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to figure out why my shutdown process became very slow and I noticed that lpf-notify and inotifywait get SIGKILLed -- which means they don't quit normally
Indeed, trying to kill them manually while inside the UI session doesn't work:
This is still an issue - my shutdown went from several seconds to over 2 minutes~ until I realised it was this package causing the lockup. Using Fedora 34, recently freshly installed.
Jan 20 00:41:23 VivoBook systemd[1297]: app-gnome-lpf\x2dnotify-1792.scope: Stopping timed out. Killing.
Jan 20 00:41:23 VivoBook systemd[1297]: app-gnome-lpf\x2dnotify-1792.scope: Killing process 1792 (lpf-notify) with signal SIGKILL.
Jan 20 00:41:23 VivoBook systemd[1297]: app-gnome-lpf\x2dnotify-1792.scope: Killing process 2137 (inotifywait) with signal SIGKILL.
Jan 20 00:41:23 VivoBook systemd[1297]: app-gnome-lpf\x2dnotify-1792.scope: Failed with result 'timeout'.
It seems that the problem goes away if you go to the lpf-gui app and uncheck the Enable Notifications option from the Notifications menu.
I guess that you won't get updates notifications any more but it's better than having to wait 90 seconds extra for each shutdown...
I'm trying to figure out why my shutdown process became very slow and I noticed that lpf-notify and inotifywait get SIGKILLed -- which means they don't quit normally
Indeed, trying to kill them manually while inside the UI session doesn't work:
The text was updated successfully, but these errors were encountered: