On Saturday 02 February 2013 07:45:17 Carl Fletcher wrote:
Dare I even ask.... but I will Did you switch on KDF as in either via Yast SM or dup -r kdf (where kdf is the repo name) And so also the Apper update in kdf
I am not using KDF, but I am more on KUSC. But Apper should behave the same regardless of the repo's configured. What could be of course different is that Apper is no longer actively checking for new updates, but keeps you reminding of the already available updates. If you check in the notification area, do you see if PackageKit is checking the repo's to find new updates or do you just see that Apper is constantly indicating that there are updates available ? Normally directly after a reboot Apper initiates PackageKit to do a check of the repo's to find possible updates. This is what is controlled by the flag and this should no longer happen.
@sven zypper works fine so long as you use: zypper up NOT: zypper patch
Carl, if you check the bug then you will see that this is something that is wrong in libzypp. Of course there is a workaround to perform a zypper up, but you can't expect that all desktop update applets are now have to have this workaround implement, just because the backend has this issue. Also the last statement in the bug report is that this is resolved now in git and that it should be submitted to Factory soon. However in your case it will not be resolved for those users running 12.2 or lower. As indicated before, Apper is using PackageKit and PackageKit utilizes the Packagekit-zypp backend to communicate with zypper. As Sven already indicated we should make sure we blame the right one here. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org