This would correctly be diagnosed as a backend error. The bug lies in the packagekit backend itself, not kpackagekit.
This would correctly be diagnosed as a backend error. The bug lies in the packagekit backend itself, not kpackagekit.