Currently the Gnome SW update mechanism seems to run faulty

Michael Schwendt mschwendt at gmail.com
Wed Apr 29 17:27:17 UTC 2015


On Wed, 29 Apr 2015 12:11:39 -0400, Joerg Lechner wrote:

> Hi,
> this error disappeared after the update of today (2015-04-29). Before this update, when I said to Gnome SW please update, the update procedure was started as usual, and the system rebooted - I know there is a cross in the left upper corner....., but the updates where not done, because as I see in the logs the modules -at least firefox and Gwenview- had not to be updated. What's about Kernel, I don't know, because my Linux knowledge is too low.
> 
> If it's useful for analysis I add the log (/var/log) of the last updates:
> 
> Apr 25 17:37:36 Installed: python3-decorator-3.4.0-5.fc21.noarch
> Apr 25 17:37:37 Installed: libselinux-python3-2.3-9.fc22.x86_64

Which log file is that? /var/log/yum.log is specific to Yum (and Yumex)
and is _not_ used by programs based on PackageKit.

If you use Yumex *and* gnome-software, this can result in temporary
confusion. They don't use shared data. They don't sync with eachother.
If you update with Yum frequently, you don't give gnome-software a
chance to catch up. In that case you need to click the top-left button
so it refreshes the repo metadata it has cached.

You can ask the PackageKit console client about what updates are
available:

  pkcon get-updates

You can also ask it about the status of the last offline update:

  pkcon offline-status

"man pkcon" for the manual page.

The current situation is not pretty, but IMO some of the problems are
caused by users having false expectations with regard to how these
various package tools work.



More information about the test mailing list