https://bugs.kde.org/show_bug.cgi?id=512442
Mike <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #5 from Mike <[email protected]> --- Alright, I have found a scenario this can happen and it appears to be related to a CUPS dbus-notifier lock that is not released or is "stuck". Plasma version doesn't matter, but if for some reason, a dbus-notifier get stuck (hangs), we stop getting notified of CUPS events, like for example, a print job finishing. Even restarting the plasma shell has no effect. Short of a complete logout, the following seems to put CUPS back into a working state: Logout of plasma Switch to a TTY login systemctl stop cups rm /etc/cups/subscriptions.* rm -rf /var/cache/cups systemctl restart cups logout Switch back to SDDM, start the plasma session As to why this happens, I'm not really sure. It's possible a crashing process that holds a notification subscription would prevent a clean "unlock" of the notifier, but I see no evidence that is happening. Plasma will generally have two processes running that "listen" for CUPS events, one is the marker level checker (kded process) and the other is the plasmoid, (plasmashell process). Both seem to operate normally and react properly to signals that are received and they log no errors or warnings in this scenario. -- You are receiving this mail because: You are watching all bug changes.
