Bug 332383 - statusnotifier does not detect when no updates are present
Summary: statusnotifier does not detect when no updates are present
Status: RESOLVED WORKSFORME
Alias: None
Product: muon
Classification: Unmaintained
Component: notifier (show other bugs)
Version: 2.1.70
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords: triaged
: 326810 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-21 00:01 UTC by Harald Sitter
Modified: 2018-10-27 02:41 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Sitter 2014-03-21 00:01:54 UTC
kind of related to bug 326173

the update statusnotifier does not disappear if one chooses to do an update WITHOUT clicking on the notifier. for example if one is currently in discover, and the notifier comes up, one may choose to upgrade right from within discover without ever clicking on the notifier. the result is that the notifier will not go away unless one clicks on it or logs out.

Reproducible: Always
Comment 1 Harald Sitter 2014-03-21 01:25:16 UTC
*** Bug 326810 has been marked as a duplicate of this bug. ***
Comment 2 Lukas Appelhans 2014-03-26 11:22:35 UTC
Is this with the latest Muon Alpha? Basically we call the notifiers via DBus in the UpdatesModel, but there could be a bug of course!
Comment 3 Harald Sitter 2014-03-26 11:45:23 UTC
Yeah. If you push your other change I can check with the latest 2.2 branch, but IIRC there were no changes in that stuff.
Comment 4 Aleix Pol 2015-01-14 16:44:29 UTC
This functionality was ported into the plasmoid.
Can you check if it's still a problem?
Comment 5 Andrew Crouthamel 2018-09-25 03:42:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:41:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!