Bug 581597

Summary:	PackageKit-yum-plugin causes delays for second yum transaction
Product:	[Fedora] Fedora	Reporter:	Christopher Beland <beland>
Component:	PackageKit	Assignee:	Richard Hughes <richard>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	bgilbert, dan.mashal, jonathan, rhughes, richard, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-15 20:16:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christopher Beland 2010-04-12 18:12:57 UTC

When a user takes one action with "yum" (e.g. update, install, remove) from the command line, and then immediately thereafter attempts to run a second "yum" command, a message such as the following is printed:

>>
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: PackageKit
    Memory :  96 M RSS (549 MB VSZ)
    Started: Mon Apr 12 13:15:07 2010 - 17:45 ago
    State  : Sleeping, pid: 4194
<<

The user must wait for PackageKit to finish its metadata update before yum will function.  This delay is annoying.  Sometimes it only lasts a minute or two, but in the instance copied above, it lasted almost 18 minutes.  

This problem was discussed in this mailing list thread:
http://lists.fedoraproject.org/pipermail/test/2010-April/089883.html

The variable StateChangedTimeoutPriority in /etc/PackageKit/PackageKit.conf is by default set to 5 seconds.  Uses can work around this annoyance by raising this value or by removing PackageKit-yum-plugin entirely.

This bug is requesting that the default behavior be improved.  Possible solutions include increasing the default value, making the yum lock mechanism more granular, and deferring download of update details until later.  Delaying updated information to PackageKit may require changing the desktop icon to some sort of "checking" status so it does not incorrectly display, for example, "33 updates" after "yum update" has already been run.

Tested with PackageKit-yum-plugin-0.5.7-2.fc12.i686, also reported in F13 Branched.

Comment 1 Richard Hughes 2010-04-14 10:06:18 UTC

(In reply to comment #0)
> Possible solutions include increasing the default value

I think this is the best idea.

> making the yum lock mechanism more granular

Impossible in the current yum code.

> and deferring download of update details until later

The client can already do this, due to the StateChanged signal. It's up to the client to do whatever is sensible whenever it gets this signal. In the case of the update icon, it's probably sensible to just hide until the new updates are available from the StateChangedTimeoutPriority derived callback.

So, for F13, how about we make the StateChangedTimeoutPriority to something like 300 seconds?

Richard.

Comment 2 Christopher Beland 2010-04-18 17:47:58 UTC

Sounds good to me.

Comment 3 Bug Zapper 2011-06-02 15:27:10 UTC

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Christopher Beland 2011-06-04 19:06:43 UTC

I still have this happen with PackageKit-yum-plugin-0.6.12-2.fc14.i686.

Comment 5 Dan Mashal 2012-04-15 20:16:34 UTC

This no longer happens in a normal Fedora 14 setup, however this is happening in newer versions of Fedora I am adding this bug as a reference to a new bug that will be proposed as a Fedora 17 blocker. This needs to get fixed.