| Summary: | Cannot disable software update notification | ||
|---|---|---|---|
| Product: | [Applications] apper | Reporter: | Dan Ciarniello <danny> |
| Component: | general | Assignee: | Daniel Nicoletti <dantti12> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | fredcwells, korossy, postix, squan, yaroslav.sapozhnik, zanetu |
| Priority: | NOR | ||
| Version: | 0.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Dan Ciarniello
2013-02-26 05:31:03 UTC
The first option is only for not refresh package cache. It doesn't say it won't display updates notification if you have some. I might add an option to disable notifications about updates, but the disabling apper monitor should do it (tho it does more than just show notifications). Are you sure the second option didn't disable it? I am positive that the second option did not disable it. According to the Service Manager, apper monitor is not running but I have a notification icon sitting on my task bar telling me I have 7 updates. A check of running processes shows that /usr/libexec/packagekitd is running and since that process only starts after I've logged in, I assume that it is the reason for the notifications. You say that the first option does not say that it won't display updates notification if one has some but that seems to me to be the most reasonable expectation of what should happen. After all, it shouldn't be possible to notify about updates if nothing is checking for them. Having a notification on the tray doesn't mean you started the session and the apper kded module was disabled. If you disable it and the notification is still there this just means you have to close it manually. Also packagekitd is a system service and can't put popups in user session. So in short you need to login with apper daemon disabled not to see a popup as a workaround. If you have 10 updates, and don't install them, if you don't check for more you will still have 10. Check for updates means that it goes to the web server and fetch more info about your package, so if you run manually yum refresh-cache (or something like that) it will now know about 30 updates and will notify you. check for updates == yum refresh-cache. but this sees to be causing some confusion... First, I did not mean to imply that packagekitd put popups in the user session just that there might be a connection between the fact that packagekitd gets started when I log in and the fact that I am still getting notifications. Also, the apper (system updater) icon has no option to close it and is always present on the system tray, updates or no. What is causing confusion is the fact that even though software update checking and the apper monitor are disabled I am still getting software update notifications. My expectation is that the apper icon should not appear and that I should not get notified of updates, period. That is the behaviour of I see from apper 0.7.2 as installed on a Fedora 17 machine. I have exactly this same problem. The only way to disable software update notifications seems to be to uninstall apper. This issue is still a problem. Is it ever going to get fixed? First off software updates for linux apps and system components are frequent and update notifications may not be desirable (on android this is a lot more unobtrusive but on a desktop machine i just prefer pullling with e.g. zypper). Then I have a linux machine for the whole family which is managed by a single person. Now every time one switches user one gets notified with whistles an bells. Also even in case of a single pending software update one gets two notifications. Please disable all these notifiications be default. Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. As this report hasn't seen any changes in 7 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. 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 mark the bug 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! 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! |