Bug 1189602 - PackagetKit reports no updates are available
Summary: PackagetKit reports no updates are available
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-05 14:09 UTC by Assen Totin
Modified: 2015-11-17 15:27 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-17 15:27:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1188207 0 unspecified CLOSED Apper won't check for updates even when user asks it to, and misses updates 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1190970 0 unspecified CLOSED PackageKit can't fetch update list 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1201938 0 unspecified CLOSED pkcon refresh uses infinite cache age by default, making it a noop 2021-12-10 14:28:28 UTC
Red Hat Bugzilla 1206760 0 unspecified CLOSED Plasma live session notifies for available updates 2021-02-22 00:41:40 UTC

Internal Links: 1188207 1190970 1201938 1206760

Description Assen Totin 2015-02-05 14:09:22 UTC
Description of problem:
PackageKit always reports no updates are available (both via APi and the pkcon console client), even when such updates are available and visible in yum console client. 

Version-Release number of selected component (if applicable):
Fully updated Fedora 21 as of Feb 5,2014
- PackageKit-1.0.4-1.fc21.x86_64
- libhif-0.1.8-4.fc21.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Run on console 'yum check-update'; 
2. Observe a list of available updates displayed.
3. Run on console 'pkcon get-updates'.

Actual results:
A message saying there are no updates available is displayed by pkcon. 

Expected results:
A message saying updates are available. 

Additional info:
The PackageKit API is similarly broken; pk_client_get_updates_async() will pass its callback wha is ultimately an empty array of available updates. 

Do note that the system includes the latest updates to libhif which was the cause for a recent outage in offline updates via PackageKit.

Comment 1 Stuart Rogers 2015-02-28 10:33:36 UTC
I am suffering from exactly this problem and can reproduce it as already stated 100% of the time. This is on my KDE system so for me it is Apper which is showing the problem with zero updates. My libhif is the same version.

Comment 2 Paulo Fidalgo 2015-03-06 10:51:46 UTC
I have the same exactly problem... I've also reinstalled some packages (PackageKit, yum, dnf and libhif) but without sucess, still need to use yum manually to get the updates.

Comment 3 Paulo Fidalgo 2015-04-01 14:35:17 UTC
Since I have this issue in my main computer and in a virtual machine I would assume that Fedora KDE users are missing all the updates. So if anyone need some logs and other debug stuff let me know and I'll be glad to help.

Comment 4 Paulo Fidalgo 2015-04-07 09:24:22 UTC
This bug is a duplicate of #1201938 as if I run "pkcon -c 86400 refresh" in the console I get updates notifications.

Comment 5 Sergio Basto 2015-04-08 12:17:12 UTC
we got a few bug reports about this , I don't find on my email one message that point out, another 2 bug reports .

bug #1190970 for example ...

Comment 6 Sergio Basto 2015-04-08 21:36:14 UTC
and bug #1188207 and bug #1189602

Comment 7 Sergio Basto 2015-04-08 21:57:09 UTC
Sorry for so many emails, summarizing : 
bug #1188207 , this one #1189602 , bug #1189602 and bug #1190970 seems to me that they are duplicated .

Comment 8 Sergio Basto 2015-05-13 18:36:53 UTC
This isn't fixed ? 

pkcon get-updates seems works fine now .

Comment 9 3ndymion 2015-06-06 12:48:32 UTC
Hi.  I also posted this in Bug 1188207...

This problem still exists.  I have done a clean install of Fedora 22 KDE "stable" multiple times, & have come across this problem.  Neither Apper nor dnf can pull updates, no matter how many times a manual update is attempted, & no matter how much time goes by.  This goes on for days.

I just tried "pkcon refresh force", & that seems to have worked for Apper.  Apper can finally update packages, but dnf still doesn't see the updates.

Comment 10 Rex Dieter 2015-06-06 13:06:00 UTC
Re: comment #9

If dnf doesn't work either, you have a different problem ... this bug is specifically about PackageKit only

(first thing I'd check... is updates repo enabled in /etc/yum.repos.d/fedora-updates.repo )

Comment 11 3ndymion 2015-06-06 14:22:05 UTC
Thanks for that.  I checked to make sure, & yes, the repos are enabled, along with others such as Adobe for Flash, & Google for Chrome.  Of all the times I've been reinstalling for various reasons, the system actually found updates completely on its own, about 2 times.  It did that automatically.  When that happened, both dnf & Apper were able to see the updates & get them like normal.  I don't know how or why it only did this a couple of times.

Since both programs have the same issue, it seems like whatever central manager they're calling to would be where the problem lies.  I'm guessing that would be PackageKit, though admittedly, I don't know much about PackageKit.  I've seen other people mention that the problem is likely a cache that's not having its timestamp updated.  Supposedly, the timestamp of when to update is set to "never".  The "pkcon refresh force" seems to have updated that timestamp, & a whole bunch of updates appeared.  Apper & dnf were both able to see them like normal.  I wish I had more knowledge to directly help with this, but all I can do is report my experiences to try to help.

Comment 12 Fedora End Of Life 2015-11-04 11:20:20 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora  'version'
of '21'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 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 this bug is closed as described in the policy above.

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 13 Paulo Fidalgo 2015-11-17 11:00:01 UTC
This can be closed because it's working now.

Comment 14 Rex Dieter 2015-11-17 15:27:31 UTC
ok


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