On Fri, Aug 17, 2012 at 11:20 PM, Carlos E. R.
On 2012-08-17 23:06, C wrote:
On Fri, Aug 17, 2012 at 10:44 PM, Dominik Baumann <> wrote:
Conclusion: A beginner isn't able to keep his operating system up to date (even important security patches will miss).
Has anyone tried a little patience here?
After years of apper, I don't have much left.
I agree... Apper is the new Beagle, and we all want it gone... myself included. I get that same exact annoying error with Apper, but, it's only after a fresh install, or within a short period after booting (intermittent).
I get it always. Always, till it misconfigures and never starts again or I remove it.
For everyone having problems with it... have you tried a little patience (as a workaround)? Seriously. I've done two system installs in the past 3 weeks. Both exhibited the Apper problem... and on both systems it stopped being a problem after a couple of hours
Couple of hours? I'm the boss and apper obeys me now or I kill it. Not even two minutes wait.
And... you snipped the bit where I said.. that waiting wasn't a solution.... I just asked if anyone has tried it. It probably isn't a couple of hours.. more like a few minutes. I just know that consistently on every single install I've done since at least 11.3 (on all my computers plau all the ones my friends are running oS on), Apper has collided with YaST, and it always always happens immediately after the initial install, and if I wait for Apper to do its thing... then no more problems from then on (my systems stay on 24x7, but I have noticed the occasional collision after a reboot). Right now, the system I'm typing this email on... it's running oS12.1 w/KDE4.9. The install is 2 weeks old. Apper collided with YaST immediately post-install. The "Tell it to quit" song and dance did nothing... but I simply waited it out. I let Apper finish what it was doing, and now... Apper is still running (it's telling me I've got 155 updates I should apply), but it hasn't collided with YaST Software Installer since the initial problem. We still have to fix the root cause... but... waiting a few mins post-install beats hacking around renaming a binary or tabooing a part of the install. Why does it need to lock the RPM database anyway? If it is simply scanning the installed apps, can't it do it in a more passive mode? You should only have to lock the database if you're _changing_ content... not viewing. The fact it's locking the database is... stupid. If you click on it and tell it to apply updates.. then lock the database, but NOT during a scan. C. -- openSUSE 12.1 x86_64, KDE 4.9.0 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org