Software Application fails to load after upgrade to f31

After upgrade to f31 I receive error Software package error in notification window. When I click the notification I get the Software Package Manager window with an error box on top that says:

Detailed errors from the package manager follow:

failed to resolve package_ids: Error calling StartServiceByName for org.freedesktop.PackageKit: Timeout was reached

Any help appreciated!

1 Like

Try:

pkcon refresh force

That should recreate the cache etc., and hopefully fix it.

Please also run the post-upgrade cleanup steps if you haven’t yet:

3 Likes

I did run the post install “rpmconf -a” but the pkcon refresh force fails with this error:

SU: # pkcon refresh force
Failed to contact PackageKit: Error calling StartServiceByName for org.freedesktop.PackageKit: Timeout was reached
[root@cyclops: ~ ]

What is the output of this command?

systemctl status packagekit
1 Like

SU: # systemctl status packagekit
● packagekit.service - PackageKit Daemon
Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor p>
Active: failed (Result: core-dump) since Thu 2020-09-17 14:20:09 EDT; 3h 39m>
Process: 1500 ExecStart=/usr/libexec/packagekitd (code=dumped, signal=SEGV)
Main PID: 1500 (code=dumped, signal=SEGV)
CPU: 79ms

Sep 17 14:20:09 cyclops systemd[1]: Starting PackageKit Daemon…
Sep 17 14:20:09 cyclops PackageKit[1500]: daemon start
Sep 17 14:20:09 cyclops systemd[1]: packagekit.service: Main process exited, co>
Sep 17 14:20:09 cyclops systemd[1]: packagekit.service: Failed with result 'cor>
Sep 17 14:20:09 cyclops systemd[1]: Failed to start PackageKit Daem

1 Like

Could you issue

journalctl -b -u packagekit --no-hostname | fpaste

and provide the link produced by such command?

And what happens if you run the following command?

sudo /usr/libexec/packagekitd -v
2 Likes

I ran the command:

SU: # journalctl -b -u packagekit --no-hostname | fpaste
Uploading (0.6KiB)…

with result shown.

Also the command /usr/libexec/packagekitd -v with the following results:

[root@cyclops: ~ ]
SU: # /usr/libexec/packagekitd -v
10:30:43 PackageKit Verbose debugging enabled (on console 1)
10:30:43 PackageKit daemon shutdown set to 0 seconds
10:30:43 PackageKit setting config file watch on /etc/PackageKit/PackageKit.conf
10:30:43 PackageKit Trying to load : dnf
10:30:43 PackageKit dlopening ‘/usr/lib64/packagekit-backend/libpk_backend_dnf.so’
10:30:43 PackageKit-DNF Using libdnf 0.47.0
10:30:43 PackageKit-DNF Using librepo 1.11.3
Segmentation fault (core dumped)
[root@cyclops: ~ ]

1 Like

Could you try

sudo /usr/libexec/packagekit-direct -v refresh-force

Then again

sudo /usr/libexec/packagekitd -v

SU: # /usr/libexec/packagekit-direct -v refresh-force
12:45:02 PackageKit Verbose debugging enabled (on console 1)
12:45:02 PackageKit Trying to load : dnf
12:45:02 PackageKit dlopening ‘/usr/lib64/packagekit-backend/libpk_backend_dnf.so’
12:45:02 PackageKit-DNF Using libdnf 0.47.0
12:45:02 PackageKit-DNF Using librepo 1.11.3
Segmentation fault (core dumped)
[root@cyclops: ~ ]

SU: # /usr/libexec/packagekitd -v
12:46:24 PackageKit Verbose debugging enabled (on console 1)
12:46:24 PackageKit daemon shutdown set to 0 seconds
12:46:24 PackageKit setting config file watch on /etc/PackageKit/PackageKit.conf
12:46:24 PackageKit Trying to load : dnf
12:46:24 PackageKit dlopening ‘/usr/lib64/packagekit-backend/libpk_backend_dnf.so’
12:46:24 PackageKit-DNF Using libdnf 0.47.0
12:46:24 PackageKit-DNF Using librepo 1.11.3
Segmentation fault (core dumped)

[root@cyclops: ~ ]

Have you tried upgrading to F32 yet?
It may actually help resolve the issue.

I haven’t tried the upgrade to F32, still trying to verify that everything works properly in F31. Was this a known problem to be resolved in F32?

Oh well… I don’t know.
Well, packagekit-direct practically is invoked by packgakid as far as I understand, more or less, so the behavior is the same.
Core dump.
You should analyze the core dump, but I’m not much of help here.

Can packagekit be removed from system along with Software application?

Yes, you can remove it and clean all the relevant caches:

# Remove packages
sudo dnf remove PackageKit\* gnome-packagekit\* gnome-software\*

# Clean user cache
rm -R -f ~/.cache
dnf clean all

# Clean system cache
sudo rm -R -f ~root/.cache
sudo dnf clean all

# Clean other caches
sudo rm -R -f /var/tmp/dnf-* /var/cache/dnf/*
1 Like

What affect will that have on the system? Could packagekit and Software app then be reinstalled with dnf install?

I have neither PackageKit nor GNOME Software installed and manage packages exclusively with DNF.
You can reinstall them later if required.

1 Like

I think that I will remove them and clean the cache like you suggested. I also only use dnf to manage software except for an occasional look to see what new applications may be available. I may even try to re-install them just to see if that fixes the problem. I certainly don’t want automatic updates to occur, since I prefer to see what is going to be updated before I apply the updates.

Thanks for the patience and help provided. I was only attempting to stop the error that only occurs on reboot.

2 Likes

Well I removed both PackageKit and Software and that did stop the error after ever reboot. I then thought maybe a fresh install of Packagekit and Software would fix the problem but it didn’t. Next I upgraded to Fedora 32 but still have the same error on every restart. As a side note I have installed dnfdragora and dnfdragora-updater neither of which work now. dnfdragora was working in Fedora 31 and I could see packages installed and packages available to install but that no longer works. It now not possible to see any Fedora packages other than from command line.

Do these applications work for anyone??