https://bugzilla.novell.com/show_bug.cgi?id=481112 Summary: KDE Updater Applet doesn't show all backend-provided upgrades with ZYpp plugin Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: bugreports@tittel.net QAContact: qa@suse.de Found By: --- Created an attachment (id=276503) --> (https://bugzilla.novell.com/attachment.cgi?id=276503) Screenshot visualizing the problem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 My KDE updater applet is set to the following settings: "Show available upgrades when backend provides them" is activated. The backend is set to "ZYpp plugin", because the PackageKit plugin doesn't support the "show available upgrades when backend provides them" option. I noticed for numerous times that the updater applet still doesn't catch all upgrades provided by the backend (of course I clicked on "Check Now" and made "zypper refresh" to be sure the updater applet has up-to-date package information). More precisely: If I choose "All Packages" -> "Update if newer version is available" in the YaST software manager more packages will be upgraded than by the updater applet. For instance at the moment I have the situation that the updater applets wants to upgrade 11 packages, but the YaST software manager wants to upgrade 12 packages. Specifically: The updater applet doesn't want to upgrade lucview. I'll attach a screenshot to demonstrate the problem. Also I will not perform any of the updates, so in case somebody has a patch, I can test if it solves the issue. In the past I also had the case that the updater applet missed far more (like YaST says 20 upgrades, updater applet doesn't see a single update) than just one package as it does now. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.