Bug 1298356

Summary: Gnome software doesn't see updates
Product: [Fedora] Fedora Reporter: Marek Doležel <marekdolezel>
Component: gnome-softwareAssignee: Richard Hughes <rhughes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 24CC: cra, klember, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-28 14:59:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screencast of problem none

Description Marek Doležel 2016-01-13 21:44:06 UTC
Created attachment 1114509 [details]
Screencast of problem

Description of problem:
In Gnome Software under updates tab click on "check for updates" icon in top left corner. It never shows available updates. 
Result: Software is up to date

Version-Release number of selected component (if applicable):
gnome software 3.18.3-2.fc24

How reproducible:


Steps to Reproduce:
1.In Software under updates tab click on icon in top left corner - updates icon.
2.In terminal run sudo dnf update
3. Compare if both terminal and software report same results. Eg. both say updates are available or both say up to date

Actual results:
Terminal: dnf update shows available updates
Gnome Software says all is up to date. 


Expected results:
Gnome Software sees updates when available.

Additional info:

Comment 1 Jan Kurik 2016-02-24 15:38:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 2 Charles R. Anderson 2016-05-28 14:59:56 UTC

*** This bug has been marked as a duplicate of bug 1266703 ***