Upon startup, 'UpdatingSoftware - Checking Updates' updater applet keeps running

Hi all,

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…:frowning:

Thank you for any hints, tips, and/or suggestions about this issue.

What output do you get when you enter

zypper lr -d

in a terminal?

Hi Ratzi,

Here’s the ‘zypper lr -d’ output:

Repository priorities are without effect. All enabled repositories share the same priority.

# | Alias         | Name                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                   | Service
1 | Google-Chrome | Google-Chrome               | Yes     | (r ) Yes  | No      |   99     | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64                  |        
2 | Mozilla       | Mozilla                     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed |        
3 | repo-debug    | openSUSE-Tumbleweed-Debug   | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/               |        
4 | repo-non-oss  | openSUSE-Tumbleweed-Non-Oss | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/tumbleweed/repo/non-oss/                 |        
5 | repo-oss      | openSUSE-Tumbleweed-Oss     | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/tumbleweed/repo/oss/                     |        
6 | repo-source   | openSUSE-Tumbleweed-Source  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/              |        
7 | repo-update   | openSUSE-Tumbleweed-Update  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/                       |        

I don’t see anything amiss here when I checked it previously. I mean, both the repos (debug & source) are not supposed to be ‘enabled’, right? Everything else looks normal except for (this I’ve wondered about) should that ‘Google-Chrome repo’ be set on “refresh”, and thus it is what is causing the updater applet to spins forever without finding anything?? The Google Chrome repo settings were placed there automatically when I installed Chrome as we are supposed to in OpenSUSE.

If it is not the Google Chrome repo setting—and I know this sounds probably extreme-----but is there any reason I cannot just ‘delete’ this “packagekitd” (it’s a daemon, right, or is it a script??) inside my /usr/lib/ folder? I mean, I absolutely do not need this updater applet in the ‘system menu’ part of the taskbar checking for updates upon every startup. I really do not need it at all. I already, from past habits for updating openSUSE, go straight to a terminal (root) and do: # zypper up . But I do need the other stuff that is in the 'system menu" applet in the taskbar, but I don’t see a way to just remove the updater applet (if it is even possible).

Thanks for replying so fast to my question :slight_smile:

In a console run ps -A find the packagekit PID then using it kill PID

Hi again!

I tried to, but I couldn’t reproduce the behavior you observed with the Tumbleweed installed on one of my desktops.
As far as I got, there seems to be no issue with the Mozilla repo of openSUSE.

I added the Google-Chrome repo - and accepted the signature key.
I got stuck during the installation of Chrome from there with the message:

Package google-chrome-stable is broken, integrity check has failed.
Error: INVALID:google-chrome-stable-55.0.2883.87-1.x86_64(Google-Chrome): Signature verification failed

I stopped there.

The usual setup when you have a fresh install of Tumbleweed is with the oss, non-oss, and update repositories of download.opensuse.org.
You could disable the other two repositories at least temporarily, in order to check if that weird behaviour of PackageKit then persists.

The update process for Tumbleweed is different than for the other openSUSE distros:
You won’t achieve anything in Tumbleweed running YaST->Online Update.

And there isn’t even a directory (or symlink)


which you can check yourself looking at


PackageKit for my tumbleweed installation works fine, so I never had a look at: # zypper up

Good luck

And my guess rather is that there is an issue with the Chrome repo, and that # zypper up in that situation may not work either.