|
Bugzilla – Full Text Bug Listing |
| Summary: | packagekit is slowwwwwwly running so soon after first boot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | David Martin <dmartinjr> |
| Component: | Update Problems | Assignee: | Vincent Untz <vuntz> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P2 - High | CC: | dmacvicar, vuntz, wstephenson |
| Version: | RC 2 | Flags: | dmacvicar:
SHIP_STOPPER?
|
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screen shot of packagekit
auth required. |
||
|
Description
David Martin
2011-11-07 08:33:07 UTC
Created attachment 460654 [details]
screen shot of packagekit
Created attachment 460657 [details]
auth required.
I am aware that there is a fix for packagekit but it has not yet available. Unless I am familiar with the source code I have really little to nothing to go by.
Duncan has the fix for slowness. The fact that it starts early after boot is probably because some app is talking to it early after boot; that'd be something from KDE, in this case. On Factory you can try request id 90224 (In reply to comment #4) > On Factory you can try request id 90224 I guess I did that via zypper up...? Maintenance: Duncan's fixes won't make it in GM, but we'd like to have them for 12.1. Can we do a maintenance update for PackageKit? Unfortunately I can't start an maintenance-update for 12.1, before it isn't released. But I will provide one as soon as possible. what information is needed from whom? (In reply to comment #7) > Unfortunately I can't start an maintenance-update for 12.1, before it isn't > released. But I will provide one as soon as possible. Is it possible now that openSUSE:12.1 is set in stone? :-) We have already released the update for that. Thanks, so closing. *** This bug has been marked as a duplicate of bug 679650 *** |