Description of problem: Apper checks for updates even if automatic check has been disabled. I experienced this on many machines. Version-Release number of selected component (if applicable): KDE 4.11.3 apper-0.8.1-2.fc19.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=948099 resurfaced?
(In reply to Lukáš Tinkl from comment #1) > https://bugzilla.redhat.com/show_bug.cgi?id=948099 resurfaced? That bug about live images, where it actually fixed. But on installed systems disabling updates check needs also removing updater applet in tray, so option in apper settings actually can't stop automatic check if applet not removed.
What evidence do you have? Is it that apper notified you of available updates? If so, that could be because you ran yum, and PackageKit-yum-plugin was the "culprit" here.
and, fwiw, I found there was no way (or very difficult) to avoid PackageKit from querying it's own cache (and rebuilding it automatically, if it was not already present... that's what hit us before on live images)
(In reply to Rex Dieter from comment #3) > What evidence do you have? > > Is it that apper notified you of available updates? If so, that could be > because you ran yum, and PackageKit-yum-plugin was the "culprit" here. I run yum updates once in a week, instead Apper notifies everyday about new updates. yum active plugins: auto-update-debuginfo, fastestmirror, langpacks, refresh-packagekit
So, I think there's just a misunderstanding what "check for updates" means. As far as I understand the code, its the part about updating the PackageKit backend (yum) metadata. I *think* what it is doing in your case is simply checking the existing PackageKit cache (and yum metadata)... and it notices that updates are available... so provides a notification saying so. Now, if what you really want is to simply never see this kind of notification, you can just disable the apper applet in your systray.
I would like also to not be annoyed by Packagekit when I am trying to run yum in bash (yum says that the lock is busy due Packagekit checking for updates). I tought that disabling Apper "check for updates", would have disabled Packagekit checking for updates too.
you thought right, except... in cases where you've run yum *recently*, PackageKit-yum-plugin does one extra thing... from that pkg description: PackageKit-yum-plugin tells PackageKit to check for updates when yum exits. This way, if you run 'yum update' and install all available updates, it will almost instantly update itself to reflect this. So, there's a short period of time after every yum transaction that PK is updating itself.
So I'm going with NOTABUG, with explanation that: Check for updates: Never does not imply that apper won't (simply) notify of available updates If you have evidence tha apper is actually checking and updating yum metadata on it's own despite "Check for updates: Never", please do feel free to reopen.