https://bugs.kde.org/show_bug.cgi?id=511499
--- Comment #9 from Kevin Krammer <[email protected]> --- I have now stopped the systemd unit and restarted it manually in a shell with debug logging enabled QT_LOGGING_RULES=org.kde.*.debug=true /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier --check-delay 20 :( org.kde.plasma.discover.notifier: Not triggering, state is DiscoverNotifier::NoUpdates org.kde.plasma.discover.notifier: refreshUnattended: not notifying about updates org.kde.plasma.discover.notifier: updateStatusNotifier: hasUpdates false hasSecurityUpdates false org.kde.plasma.libdiscover.backend.packagekit: using... PackageKit::Transaction(0x624d62a4c5b0) "/4697_edeadbeb" org.kde.plasma.discover.notifier: updateStatusNotifier: hasUpdates true hasSecurityUpdates false org.kde.plasma.discover.notifier: Not triggering, earliestNextTriggerTime is QDateTime(2025-11-11 17:37:09.827 UTC Qt::TimeZone UTC ) org.kde.plasma.discover.notifier: showUpdatesNotification: not notifying about updates org.kde.plasma.discover.notifier: refreshUnattended: useUnattendedUpdates false isOnline true isConnectionAdequate true So at least the problem at startup is not the missing check but the timestamp comparison. Which is should probably not do on startup otherwise logging out and logging in again loses UI state. Will keep this running until Wednesday when at least one interval check should have happened -- You are receiving this mail because: You are watching all bug changes.
