KPackageKit can't resolve dependencies and recommends Synaptic or Aptitude

[Scott Kitterman]

Binary package hint: kpackagekit

See the attached screenshot. KPackageKit recommends Synaptic or Aptitude to work around being unable to fix 'broken' packages, but doesn't even bother to say what the package is that's broken. This is seriously unsuitable.

[coldbluelight (coldbluelight)]

i found how to fix this problem its due to a broken dependency in the package list to fix it go to your terminal and run the following command sudo apt-get -f install :follow the on screen instructions and it should fix your problem hope that helps .
-coldbluelight

[Scott Kitterman (kitterman)]

Yes, but if kpackagekit aspires to be a proper package manager, it needs to
be able to solve these problems.

[Oded Arbel (oded-geek)]

@Scott Kitterman: Also, the fact that an advanced user can figure out how to solve the problem is not an indication that its not a problem. As far as I'm concerned, the fact that KPackageKit recommends synaptic might have been acceptable if synaptic is installed (which it isn't in Kubuntu).

If the KPackageKit error dialog would have said "Open a terminal, run 'sudo apt-get -f install' and follow the on-screen prompts", that would have been an acceptable (though not optimal) solution. For KPackageKit to be valid as the main package manager for Kubuntu Lucid, one of these things have to happen:
1. The broken dependencies error should instruct the user exactly on how to solve the problems using the tools available by default on Kubuntu. i.e. not suggest Synaptic (which is not installed) or aptitude (which is hard to figure out).
2. The error message can stay the same if Synaptic is made available by default on KUbuntu (which is valid IMHO, even though Synaptic is not a KDE application - similarly to how Ubuntu Software Center is the support method to install software in GNOME Ubuntu and synaptic is still available under the System menu).
3. KPackageKit should be changed so it can solve broken dependencies by itself.

As it stands now, a Kubuntu use that encounters this problem has no way to solve it by themselves.

[Scott Kitterman (kitterman)]

Installing Synaptic is no solution. KPackagekit needs to be fixed.

[Daniel Nicoletti (dantti)]

First it is important to note that resolving deps is not KPackageKit task, it is the backend's.
aptcc (default in Maverick), does what apt-get does when a dep problem happens, it shows to the user why that happened. The user just need to read and take the proper action.
Aptitude and Synaptic are very close to apt which is why it easier to suggest changes (not counting the AI that aptitude has...).

IMO this is a closed bug (for aptcc), otherwise apt-get should be included too :P