Bug 84486 - packagekitd 1.0.0 fails to update system with ALPM backend
Summary: packagekitd 1.0.0 fails to update system with ALPM backend
Alias: None
Product: PackageKit
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Richard Hughes
QA Contact:
Depends on:
Reported: 2014-09-29 18:16 UTC by Balló György
Modified: 2018-08-21 15:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Console output of '/usr/lib/PackageKit/packagekitd --verbose' (11.51 KB, text/plain)
2014-09-29 18:16 UTC, Balló György

Description Balló György 2014-09-29 18:16:16 UTC
Created attachment 107078 [details]
Console output of '/usr/lib/PackageKit/packagekitd --verbose'

When I'm trying to update the system with gpk-update-viewer, nothing happens, the transaction fails without an error.

Distribution: Arch Linux (ALPM backend used)

Package versions:
- packagekit 1.0.0
- gnome-packagekit 3.14.0

I attached the console output of the packagekitd command.
Comment 1 Richard Hughes 2014-09-30 10:42:06 UTC
According to that debug log, the transaction actually succeeded, but the update still shows. If you restart packagekitd, does the update still show? I.e. is it a cache somewhere we have to invalidate?
Comment 2 Balló György 2014-09-30 11:54:58 UTC
Yes, the packages are still shown on the update list after I restart packagekitd. Even if PackageKit reports as succeeded, it doesn't do anything, the old package versions remain on the system. I can't see anything in pacman.log except the following line:
[PACKAGEKIT] synchronizing package lists
Comment 3 Richard Hughes 2018-08-21 15:52:40 UTC
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.