A "The package update has completed" notification popped up. "What package update?" I thought. Sure enough, looking in the logs.. Dec 14 16:03:13 localhost yum: Installed: createrepo-0.9.6-3.fc10.noarch Dec 14 16:03:14 localhost yum: Installed: 1:anaconda-yum-plugins-1.0-3.fc10.noarch Dec 14 16:03:14 localhost yum: Installed: preupgrade-1.0.0-1.fc10.noarch I hadn't initiated this, and the 'automatically install' option is set to 'nothing'.
Right, this is because you did a check for a distro upgrade (for instance F10 to F11) and the preupgrade package contained the data file. I agree installing stuff automatically like this is bad, and this is why the next PK release will just have a straight dep on preupgrade.
I also got this "What the hell"? situation. Fedora 9 livecd install ( no upgrade ). I hit "update system" and put the PackageKit window in the background while I ran another program. I have it set to NOT automatically install. I actually forgot about it until the "The package update has completed" notification popped up. I also got an EMPTY window pop-up with the string "the following packages have been updated" (or something similar). I checked the Software Log Viewer (gpk-log) and it did not show anything. I thought to myself, that this is the kind of OS strangeness that I used to only experience on MS Windows. This is definitely a patented MS Windows "why did my computer just do that" moment. And it wasn't until reading this bugzilla that I checked /var/log/messages and found: Dec 15 07:39:04 localhost yum: Installed: createrepo-0.9.5-2.fc9.noarch Dec 15 07:39:05 localhost yum: Installed: anaconda-yum-plugins-1.0-1.fc9.noarch Dec 15 07:39:06 localhost yum: Installed: preupgrade-1.0.0-1.fc9.noarch
On my system the same thing happened just now with preupgrade-1.0.1-1.fc9. In the desktop I have specifically disabled installing updates (Preferences -> System -> Software Updates), but it still happened. I am, ehr, not too fond of this behaviour. I have not been able to find out how I can actually disable it.
Armijn, it's been fixed in newer versions of PackageKit. Sorry for the inconvenience.
I don't understand. This update was installed yesterday. The last PackageKit update I installed was on December 13, which is 3 weeks ago. Obviously it was not fixed in that release :-)
Armin, ahh, you're on F9. I'll have to do an update for that.
F9 is now EOL closing this -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers