|Summary:||KPackageKit sometimes forgets setting not to auto-install security updates|
|Product:||[Fedora] Fedora||Reporter:||Kevin Kofler <kevin>|
|Component:||kpackagekit||Assignee:||Steven M. Parrish <tuxbrewr>|
|Status:||CLOSED DUPLICATE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||9||CC:||andreas.petzold, balajig81, kevin, mathias.v44, ogldelphi, rdieter, rick.hendricksen, tuxbrewr|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-03-17 14:01:34 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Kevin Kofler 2008-12-08 20:29:51 UTC
Description of problem: Sometimes, seemingly at random, KPackageKit suddenly resets its "Install updates automatically" setting from "None" to "Security only". This is really bad. Version-Release number of selected component (if applicable): kpackagekit-0.3.1-5.fc9.i386 Also seen on F10. How reproducible: No idea, happens seemingly at random. Steps to Reproduce: See above. Actual results: The setting suddenly changes to "Security only", and with the next update set, KPackageKit starts installing security updates without asking. Expected results: The setting stays at "None", which is also the default setting from kde-settings.
Comment 1 Fedora Update System 2008-12-09 01:10:42 UTC
kpackagekit-0.3.1-8.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kpackagekit-0.3.1-8.fc10
Comment 2 Fedora Update System 2008-12-10 04:35:05 UTC
PackageKit-0.3.12-1.fc10, gnome-packagekit-0.3.12-1.fc10, kpackagekit-0.3.1-9.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
Comment 3 Kevin Kofler 2008-12-19 03:19:00 UTC
This still happens with both kpackagekit-0.3.1-6.fc9.i386 and kpackagekit-0.3.1-9.fc10.x86_64!
Comment 4 Kevin Kofler 2009-01-09 02:50:59 UTC
Still not fixed. Moreover, when it does this, sometimes (always?), it also installs updates which are NOT security updates.
Comment 5 Steven M. Parrish 2009-01-09 05:03:06 UTC
Based on comments from RHughes this is not a kpackagekit issue but a packagekit one. He has got a fix for it and a new packagekit today that contains the fix. Will be sometime next week before it makes it into the repos.
Comment 6 Kevin Kofler 2009-01-09 05:10:38 UTC
But the option which is displayed in the KPackageKit UI also changes! How can PackageKit be causing this?
Comment 7 Steven M. Parrish 2009-02-06 15:25:38 UTC
Still waiting on upstream to advise. Patch we used locally should have fixed this issue. I am still unable to reproduce on any of my boxes.
Comment 8 Kevin Kofler 2009-02-06 15:30:01 UTC
It's still happening on both of mine and I'm unable to figure out why. One suspicion I have is that it's because the "Security only" entry is the first in the combobox - I guess there's some issue with the settings not always getting loaded and thus the default value of the combobox being used.
Comment 9 Kevin Kofler 2009-03-17 14:01:34 UTC
I haven't seen this happening, nor read any complaint about it, since the KDE 4.2 updates. I suspect this was due to some KConfig bug which got fixed in 4.2. If anybody can still reproduce this, we can reopen it.
Comment 10 German Pacenza 2009-09-10 22:50:16 UTC
Same bug here. Fedora 11 kpackagekit 0.4.2-0
Comment 11 RJ 2009-09-24 13:02:24 UTC
+1 for Comment #10 KPackageKit forgets "Automatic install" and "Check for updates" options. Please fix this issue, because sometimes I have to wait it's "hourly update checking" Thank you.
Comment 12 rick 2009-10-27 09:27:36 UTC
Same problem here. F11, [rick@localhost ~]$ kpackagekit --version Qt: 4.5.2 KDE: 4.3.1 (KDE 4.3.1) KPackageKit: 0.4.2
Comment 13 Mathias Védrines 2009-10-27 12:22:42 UTC
I experience the same annoying issue. [mathias@echoes ~]$ packagekit-bugreport.sh Distro version: Fedora release 11 (Leonidas) PackageKit version: 0.4.9 Same Qt, KDE, KPackageKit versions as Rick in Comment #12. Why “CLOSED WORKSFORME” ? It seems like we are several people to face to the same problem. Thanks in advance for fixing this bug.