Bug 962100 - Updates applet fails if there are unfinished yum transactions (PackageKit internal error) [NEEDINFO]
Updates applet fails if there are unfinished yum transactions (PackageKit int...
Product: Fedora
Classification: Fedora
Component: PackageKit (Show other bugs)
All Linux
unspecified Severity low
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-05-11 15:01 EDT by Assen Totin
Modified: 2014-02-05 18:09 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-02-05 18:09:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rhughes: needinfo? (assen)

Attachments (Terms of Use)

  None (edit)
Description Assen Totin 2013-05-11 15:01:19 EDT
Description of problem:

If there are unfinished yum transactions, the software updates applet (which uses Package Kit) will fail to display pending updates. 

Version-Release number of selected component (if applicable):


How reproducible:

Every time.

Steps to Reproduce:
1. Start 'yum update' as root in terminal; when asked to confirm pending updates, press "Enter". This will cancel the update leaving an unfinished transaction. 
2. The software updates applet will not show any pending updates until the cancelled transaction is completed. 

Actual results:

No 'pending updates' message is shown.

Expected results:

'There are pending updates" message.

Additional info:

The actual reason seems an to be issue with PackageKit. A simple program shows that when there is an incomplete transaction, the pk_results_get_package_array() function will fail with a message that assertion using macro PK_IS_RESULT() has failed. As a minimum, properl error handling/reporting here is a must. 

Similar behaviour observed in RHEL6, so this is probably a long existing case.

Obviously, if yum is not used in terminal for updates, this will never surface - but still the case might be worth taking a look at.
Comment 1 Richard Hughes 2013-12-11 04:08:58 EST
Does this still happen in Fedora 20?
Comment 2 Fedora End Of Life 2013-12-21 10:31:06 EST
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.
Comment 3 Fedora End Of Life 2014-02-05 18:09:26 EST
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.