Description of problem: Never check for new updates Apper option ignored. Version-Release number of selected component (if applicable): Steps to Reproduce: 1. Start F19 Alpha TC3 live image 2. 3. Actual results: Apper option "Check for new updates" set to Never but updates checked when KDE started that slows down live image. Expected results: Updates should not be checked. Additional info: After I removed "Software Updater" from systray and restarted KDE session new updates notification still appeared.
Version-Release number of selected component (if applicable): apper-0.8.0-3.fc19
Nominating as Beta blocker and Alpha freeze exception because bug #948685 is nominated as these and it's a duplicate of this bug.
*** Bug 948685 has been marked as a duplicate of this bug. ***
Actually, it looks like the problem is not the plasmoid, but the underlying kded4 service (which is also part of the apper package).
This has been already proposed as beta blocker: bug #928296 (http://qa.fedoraproject.org/blockerbugs/milestone/19/beta/buglist).
*** Bug 928296 has been marked as a duplicate of this bug. ***
why close the older one as a dupe of the newer one? oh well, no biggy.
This bug not only about live image, ignoring apper settings should be fixed also for installed systems.
Discussed at 2013-04-24 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-24/f19beta-blocker-review-1.2013-04-24-16.00.log.txt . Accepted as a blocker per criterion https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria#Update_notification : "Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image."
Is it a is the bug about checking for new updates or about showing notification about updates? Right now there is no way to disable the later, and the text is NOT about notification it's about to check with servers if there are updates.
The former. In short, we really do not want packagekitd to fetch repo metadata *at all* on the live image.
(at least, not automatically on it's own accord)
So if the former I believe this is a yum backend bug, if you set to never check for updates what kded module will do is a call to GetUpdates just to see how much it has without asking to refresh-cache, I dunno why yum thinks it needs to be smarter and got refresh the cache first.
BTW not sure Richard told me this should fix something around yum: https://bugzilla.redhat.com/show_bug.cgi?id=953239 Tho doesn't seem much related imo you should actually disable apper kded module on the live cd, it will eat less RAM and avoid this issue.
apper-0.8.0-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/apper-0.8.0-4.fc19
Package apper-0.8.0-5.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing apper-0.8.0-5.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6940/apper-0.8.0-5.fc19 then log in and leave karma (feedback).
Arg, still seeing /var/cache/yum ... get re-populated when empty Try harder, by disabling apper kded module too: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=19912d72a1b0751532980a03a9520a88174c1361 Reassigning to PackageKit... Richard, Daniel asserts this to be a yum backend bug in comment #13 , can you verify or refute that claim?
Tried the upstream fix referenced in comment #14 (see below), doesn't seem to help here. ----------------------------------------------------- From 34f4863060ef804c075f3f0a1fc2ff88d458eb1f Mon Sep 17 00:00:00 2001 From: Richard Hughes <richard> Date: Wed, 24 Apr 2013 10:59:54 +0100 Subject: yum: Ensure conf.cache is set before repo.cache is created This should fix the offline updates failures reported in https://bugzilla.redhat.com/show_bug.cgi?id=953239 and others. --- backends/yum/yumBackend.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backends/yum/yumBackend.py b/backends/yum/yumBackend.py index 7c6f6f0..a5cbb18 100755 --- a/backends/yum/yumBackend.py +++ b/backends/yum/yumBackend.py @@ -3101,9 +3101,9 @@ class PackageKitYumBackend(PackageKitBaseBackend, PackagekitPackage): # we are working offline if not self.has_network: + self.yumbase.conf.cache = 1 for repo in self.yumbase.repos.listEnabled(): repo.metadata_expire = -1 # never refresh - self.yumbase.conf.cache = 1 # choose a good default if the client didn't specify a timeout if self.cache_age == 0: -- 1.8.1.4
resorted to killing the plasma-update-applet altogether on kde live: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=95e68dc29e12c3777794fa27e1d2c7425418be7e
That kickstart should have been used for Beta TC2, so can people please check with Beta TC2 and verify that this is fixed? Thanks!
Still appears notification about 96 updates on Fedora-Live-KDE-i686-19-Beta-TC2-1.iso
Both enabled Apper Monitor service and Software Updater in systray.
Odd, the kickstart referenced here, http://koji.fedoraproject.org/koji/taskinfo?taskID=5322177 Doesn't seem to include my latest commits. Looking closer... oh fooey, looks like I only made the commits to spin-kickstarts master/ branch, not f19 yet. :( OK, cherry-picked things to f19 branch now too.
Apper service disabled on TC3 but Software Updater in systray still shows 173 available updates.
TC3 was built with the latest kickstart, but it did not have the changed 'apper' package; rdieter didn't think it was needed, but just noting this for the record.
Unfortunately, the kickstart changes try to disable the plasmoid using X-KDE-PluginInfo-EnabledByDefault. That just cannot work, that key has no effect for plasmoids. http://pkgs.fedoraproject.org/cgit/apper.git/tree/01-fedora-apper-updater.js needs to get disabled for live sessions instead. The reasons Rex did not notice this during testing is that Plasma update scripts are run only once. So once you remove the plasmoid, it stays removed. Plasmoids are not autostarted on log in, they're added persistently and removed persistently.
OK, prepping new apper builds with modified plasma scriptlets to not add applet for liveuser.
nucleo confirmed that my first attempt apper-0.8.0-6.fc19 was a botch job on my part. apper-0.8.1-0.2.20130511.fc19 (with PackageKit-Qt-0.8.8-1.fc19) should work better.
If you can submit it as an update that'd be great, I'll ensure it's pulled into the next compose.
Updates are not checked on live images, so this is fixed in F19 Beta RC1.
Thanks!
apper-0.8.1-0.2.20130511.fc19, PackageKit-Qt-0.8.8-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
Bodhi's not closing things again...
https://bugzilla.redhat.com/show_bug.cgi?id=1039923