What is packagekitd and should I let it connect?

Hello World,

When I wake up in the morning the first thing I do is fire up my pc, then while it’s booting I finish the rest of my morning routine before sitting down in front of it.
And because the rest of my routine takes several minutes, for the last few days, when I finally do sit down at my pc I notice this temporay rule gets created in my firewall(automatically set to deny because the timer ran out) for packagekitd.

What exactly is this packagekitd and why is it trying to connect? I found a github page for packagekit(without the D at the end) but couldn’t understand a thing from the description they give it there…
So is this thing safe, should I just create a permanent allow rule for it or what?

Thank you.

You forgot to state your Fedora version and edition.

I would guess packagekitd is checking for new package updates.

What exactly is this packagekitd and why is it trying to connect?

$ dnf info packagekit
Updating and loading repositories:
Repositories loaded.
Installed packages
Name : PackageKit
Epoch : 0
Version : 1.3.4
Release : 3.fc44
Architecture : x86_64
Installed size : 3.4 MiB
Source : PackageKit-1.3.4-3.fc44.src.rpm
From repository : fedora
Summary : Package management service
URL : ``http://www.freedesktop.org/software/PackageKit/
License : GPL-2.0-or-later AND LGPL-2.1-or-later AND FSFAP
Description : PackageKit is a D-Bus abstraction layer that allows the session user
: to manage packages in a secure way using a cross-distro,
: cross-architecture API.
Vendor : Fedora Project

The site: https://www.freedesktop.org/software/PackageKit/pk-intro.html

should answer your first question. As to your second question, I’m not sure. It might be checking for software updates, but I can’t confirm that.

Short answer is that packagekitd is part of PackageKit, which provides access to the underlying update mechanism for GUI tools that manage (install/remove/update) software packages.

If you use any graphical package management tools (i.e., GNOME Software), you’re using packagekit as middleware to the back end software management system.

I really recommend checking out the link above. It’s quite informative.

K, thanks guys, guess I’ll make an allow rule for it then.

If you haven’t come across this before, it’s a common naming pattern for daemons (services running in the background) to have the d added as a suffix.

So the packagekit daemon is packagekitd, the ssh daemon as sshd, upower daemon is upowerd and so on.

It’s not a 100% rule, but something you will probably encounter again.