Comment 4 for bug 454424

@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.