Bug 727788 - Error autoremove not available on every uninstall using kpackagekit
Summary: Error autoremove not available on every uninstall using kpackagekit
Alias: None
Product: Fedora
Classification: Fedora
Component: kpackagekit
Version: 15
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-03 08:58 UTC by Fabien Archambault
Modified: 2011-10-25 03:30 UTC (History)
6 users (show)

Fixed In Version: apper-0.7.1-0.3.20111021.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-10-22 08:24:20 UTC

Attachments (Terms of Use)

Description Fabien Archambault 2011-08-03 08:58:24 UTC
Description of problem: Every time I remove something with kpackagekit I have an error message even if it deletes the package

Version-Release number of selected component (if applicable):
# kpackagekit --version
Qt: 4.7.3
KDE Development Platform: 4.6.5 (4.6.5)

How reproducible: always

Steps to Reproduce:
1. Install any package using kpackagekit
2. remove it with kpackagekit
3. See the error message:
10:57:29 - The parameter was invalid
the yum backend does not support autoremove
Actual results: Error message

Expected results: As in PackageKit with gnome it should not give an error...

Additional info:

Comment 1 Richard Hughes 2011-08-03 09:13:06 UTC
kpackagekit probably shouldn't be setting autoremove=true by default; that option was designed for embedded systems like mobile phones.

Comment 2 Kevin Kofler 2011-08-03 09:18:37 UTC
FWIW, current versions of yum track the information required to support autoremove in their database, so at least in theory it should now be possible to implement. Now, whether it makes sense to use it in KPK in the first place is another question.

Comment 3 Richard Hughes 2011-08-03 09:35:36 UTC
Yes, I know. The two big problems with turning on autoremove in yum as as follows:

* If the user uses raw rpm then the yumdb does not get updated and bad things happen

* That the user is not expecting tons of packages (that they might still be using) to also be removed. The only way to solve that, is with a little checkbox in the UI ([x] also remove other software installed with this package) but the designers would shoot me for that.

Comment 4 Kevin Kofler 2011-08-03 09:53:19 UTC
The KDE folks might actually go with the extra checkbox though. :-) (I'd have to ask Daniel what he thinks.) In any case, the backend should support it; whether the UI supports it or not is the UI's business.

If the yum database has no information about a package, the safe thing to do is to not autoremove it.

But for now, the best thing to do is probably to just patch out the use of autoremove from KPK.

Comment 5 Rex Dieter 2011-10-13 02:40:39 UTC
Overheard someone on irc report seeing this.

I can't seem to reproduce this, I can add/remove apps, and not see any such errors.  

$ rpm -q PackageKit kpackagekit

Comment 6 Fedora Update System 2011-10-13 03:09:35 UTC
kpackagekit- has been submitted as an update for Fedora 15.

Comment 7 Fedora Update System 2011-10-13 03:10:19 UTC
kpackagekit- has been submitted as an update for Fedora 16.

Comment 8 Fedora Update System 2011-10-13 18:12:51 UTC
Package kpackagekit-
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kpackagekit-'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2011-10-22 08:24:20 UTC
kpackagekit- has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2011-10-25 03:30:22 UTC
apper-0.7.1-0.3.20111021.fc16, kde-settings-4.7-13.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.