OpenSUSE Tumbleweed, 64-bit, latest image:
Was wondering if anyone could help me.
When I startup OpenSUSE, and I get to the desktop environment, I look down & over at the updater applet and it is constantly running. This thing will not stop, and also, it never finds “any” updates, until a few hours have passed.
I cannot (easily) terminate this updater applet either… if I try to open any updating in YAST (i.e. Software Install), I first get this message in a popup notification:
*Packagekit is blocking software management. This happens when the updater applet or another software management application is running.
Ask PackageKit to quit? YES or NO?
*So I chose "YES’, to get it to stop, then I get this popup:
*PackageKit is still running (probably busy). Ask PackageKit to quit again? “YES” or “NO”
*This does not help either. You keep checking “YES”, it keeps popping back up the same line above. The udater applet just refuses and keeps running. So then you have to click “Abort”, to get out of trying to get into YAST, and then this message pops up:
System management is locked by the application with pid 2428 (/usr/lib/packagekitd).
Well, no kidding! This is obvious!!!
So then (letting this freaking updater applet gremlin play itself out, finally, after about an hour or two, a message pops up after the updater applet finally runs (seemingly) out of steam:
*Problem connecting to software origins.
*Again, no kidding. I checked VAr messages and details, and even checked the software origins, and nothing seems amiss. Is this a known bug occurring in the latest Tumbleweed install? Anyone else seeing this?? Furthermore, could anyone help me in directing me what I should do/configure look at to make this updater applet function correctly? Or at least kill it permanently so it stops its constant spinning & running upon startup (and for an hour or two afterwards) saying it is “checking updates” but never finding anything?!
This dang applet is like the ghost from Christmas past, and this Tumbleweed experiment is driving me nuts sometimes (about ready to go back to LEAP, as the number of things I have to either fix and/or stay on top of makes Tumbleweed even more of a headache than Debian Unstable/Testing…
Thank you for any hints, tips, and/or suggestions about this issue.