Neal Becker wrote: > F25, all current > > All I ever get it "the task was forcibly cancelled...". > > Manually running sudo dnf update works fine. When this happens next, try 2 things (probably in separate konsoles): 1. monitor things: $ pkmon 2. refresh cache: $ pkcon refresh force 3. trigger update: $ pkcon update and report any warnings/errors/crashes from PackageKit. Do you happen to have any copr repos enabled? One thing I ran into (that I'm not sure I've filed a bug for yet), is an unfortunate interaction with copr repos that (sometimes?) fail to provide appdata, and PackageKit will choke on that. For example, I just tried, and hit this (doing 'pkcon refresh force'): $ pkcon refresh force Refreshing cache [=========================] Loading cache [=========================] Downloading repository information[=========================] Finished [=========================] Fatal error: Error when getting information for file '/var/cache/PackageKit/25/metadata/group_kdesig- qtwebengine/repodata/44b15acf0e2c6d4f1d05be1fa46ac910ba2349730cc69dea898b1c389edb9c0d- appstream.xml.gz': No such file or directory Only workaround I see at the moment is to manually set: enabled_metadata=0 in affected repo configurations, in my example here, editing: /etc/yum.repos.d/_copr_@xxxxxxxxxxxxxxxxxxxxxxx -- Rex _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
