Bug 436840 – sometimes automated check occurs when network not available?

Bug 436840 - sometimes automated check occurs when network not available?

Summary:	sometimes automated check occurs when network not available?

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	PackageKit (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Robin Norwood
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-03-10 14:59 EDT by Jeremy Katz
Modified:	2008-03-26 09:59 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-03-26 09:59:13 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
What i've just merged into git (4.58 KB, patch) 2008-03-16 19:53 EDT, Richard Hughes	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jeremy Katz 2008-03-10 14:59:13 EDT

I've seen this now twice, but can't put a better set of circumstances around it.
 But I've got PK set to check for updates hourly and when I suspend, I've
resumed and had the notification bubble about a problem getting the info for a
network repo.

Comment 1 Richard Hughes 2008-03-16 19:53:31 EDT

Created attachment 298226 [details]
What i've just merged into git

When you resume, PK forces a check to make sure the caches are valid. It could
be we are doing that when the network is still coming up.

The attatched patch should fix things, which I'll merge into git after I've
tested it out and make check completes. Thanks.

Comment 2 Richard Hughes 2008-03-16 19:55:42 EDT

Committed to git.

Comment 3 Robin Norwood 2008-03-19 17:34:47 EDT

This seems to be fixed for me in git, and should be fixed in 0.1.10 or later.

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