Bug 1696193

Summary:	Gnome Software is unable to get info about possible updates on Silverblue
Product:	[Fedora] Fedora	Reporter:	Lukas Ruzicka <lruzicka>
Component:	PackageKit	Assignee:	Richard Hughes <rhughes>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	30	CC:	jonathan, klember, rdieter, rhughes, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-05 00:01:51 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:

Description Lukas Ruzicka 2019-04-04 09:58:31 UTC

Description of problem:

Whenever I want to see if updates are available on Silverblue, it ends up with time out error.

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

Gnome-Shell 3.32.0
pkmon 1.1.12

How reproducible:

Always

Steps to Reproduce:
1. Use Gnome-Software to see if upload are possible.
2. Start pkmon in a console to monitor.
3. Hit the Refresh button.
4. See the error appear on the console.

Actual results:

The operation times out with "Failed to get properties: Error calling StartServiceByName for org.freedesktop.PackageKit: Timeout was reached"

Expected results:

The operation runs successfully, even if updates are not available.

Comment 1 Kalev Lember 2019-04-04 10:16:13 UTC

This should be already fixed in gnome-software-3.32.0-5.fc30 build

Comment 2 Fedora Update System 2019-04-04 10:16:48 UTC

gnome-software-3.32.0-5.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e67aacc280

Comment 3 Fedora Update System 2019-04-05 00:01:51 UTC

gnome-software-3.32.0-5.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.