Bugzilla – Bug 728612
packagekit is slowwwwwwly running so soon after first boot
Last modified: 2011-11-24 09:11:13 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 within minutes after first boot, packagekit does it's 30 minute thing which blocks me from testing "kdeinit could not launch /usr/bin/apper". Reproducible: Always Steps to Reproduce: 1.install from openSUSE-DVD-Build0025-x86_64.iso change boot from / to MBR 2.pc hangs, hard reset to reboot 3.reboots OK 4.packagekit runs and runs and runs Actual Results: When package kit is done it has 1 e.g. one update. did them. Expected Results: when will fixed packagekit come in? this is my third install and test. Apper which has known problems is also giving me problems, probably related to packagekit. I see that bugs have been resolved. But how do I find if a fix has been applied and how can I apply to my system.
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 ***