Bug 396170

Summary: PackageKit: Failed to reset get-updates
Product: [openSUSE] openSUSE 11.0 Reporter: Michael Glenn <mglenn>
Component: Update ProblemsAssignee: Scott Reeves <sreeves>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: claudiohfg, deerfieldtech, rawsausage, sontek, terjejhanssen
Version: RC 1   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: BugBuddy Report

Description Michael Glenn 2008-05-31 19:58:30 UTC
Tested in Gnome. Upon login and shortly after the desktop is displayed, the PackageKit Update Applet (v0.2.1) pops an error message: "Failed to reset client. Failed to reset get-updates." Upon hitting Close, BugBuddy pops up to file a bug report to the desktop, and the PackageKit tray icon closes. This occurs upon each login.
Comment 1 Michael Glenn 2008-05-31 20:02:24 UTC
Created attachment 219349 [details]
BugBuddy Report
Comment 2 Michael Glenn 2008-06-14 11:44:31 UTC
Okay; reinstalled to the test machine from Factory last night, and it looks like the problem has been cleared-up.I'll keep watching it for a few more days, but it looks like this bug can be closed.
Comment 3 John Anderson 2008-07-01 06:48:42 UTC
This happens to me also, I ran updates today, but I don't know when the dialog showed up, it opens without taking focus or showing itself in the task bar.
Comment 4 raw sausage 2008-07-04 14:50:28 UTC
This happens to me every day couple times, on fully updated 11.0. It's a constant nuisance.
Comment 5 Scott Reeves 2008-07-17 03:50:33 UTC
*** Bug 406624 has been marked as a duplicate of this bug. ***
Comment 6 Scott Reeves 2008-07-17 03:53:25 UTC
Fix is submitted and is in the update-test repo. Should hit the update repo in a couple days.
Comment 7 Scott Reeves 2008-07-17 03:56:19 UTC
*** Bug 396258 has been marked as a duplicate of this bug. ***
Comment 8 Vance Baarda 2008-07-18 18:06:54 UTC

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