Package: packagekit
Version: 1.1.5-2
Severity: normal
Dear Maintainer,
Problem: On 3 new installs of Stretch (KDE), I noticed that PackageKit was
updating frequently (about every 5 minutes - continuously). There is no
good reason for the updates. This doesn't happen on a similarly
configured Gnome system.
Bypass: The only way I found to stop the updates is to uninstall
"packagekit".
I'm not sure what the side-effects of that may be, but I'm sure
packagekit
is installed on the default system for a reason.
Discussion: In trying to diagnose what was happening on my real hardware,
I've installed several copies of Stretch on VMware. I installed
them with
the same installer configuration parameters as my real systems.
Then I started
to add software. As soon as I added Chromium, the problem started
showing
up in "syslog". Notice the times, around every 5 minutes
Nov 14 16:02:24 vm921 systemd[1]: Started Run anacron jobs.
Nov 14 16:02:24 vm921 anacron[54523]: Anacron 2.3 started on 2017-11-14
Nov 14 16:02:24 vm921 anacron[54523]: Normal exit (0 jobs run)
Nov 14 16:02:24 vm921 systemd[1]: anacron.timer: Adding 1min
18.530212s random time.
Nov 14 16:04:58 vm921 PackageKit: refresh-cache transaction
/1630_dadbdddd from uid 1000 finished with success after 948ms
Nov 14 16:04:58 vm921 PackageKit: get-updates transaction
/1631_cedaadac from uid 1000 finished with success after 734ms
Nov 14 16:04:59 vm921 PackageKit: get-updates transaction
/1632_ceaaccaa from uid 1000 finished with success after 244ms
Nov 14 16:05:00 vm921 PackageKit: get-updates transaction
/1634_aeeebeaa from uid 1000 finished with success after 249ms
Nov 14 16:05:00 vm921 PackageKit: get-updates transaction
/1635_ddcbbaaa from uid 1000 finished with success after 240ms
Nov 14 16:10:57 vm921 PackageKit: refresh-cache transaction
/1637_aeadadba from uid 1000 finished with success after 857ms
Nov 14 16:10:58 vm921 PackageKit: get-updates transaction
/1638_bcbabdbb from uid 1000 finished with success after 833ms
Nov 14 16:10:59 vm921 PackageKit: get-updates transaction
/1639_abaecbee from uid 1000 finished with success after 228ms
Nov 14 16:11:00 vm921 PackageKit: get-updates transaction
/1641_dcccabdc from uid 1000 finished with success after 224ms
Nov 14 16:11:00 vm921 PackageKit: get-updates transaction
/1642_ccadcceb from uid 1000 finished with success after 214ms
Nov 14 16:16:57 vm921 PackageKit: refresh-cache transaction
/1644_bbaddbbe from uid 1000 finished with success after 835ms
Nov 14 16:16:58 vm921 PackageKit: get-updates transaction
/1645_cccdedca from uid 1000 finished with success after 767ms
Nov 14 16:16:59 vm921 PackageKit: get-updates transaction
/1646_abcaaeec from uid 1000 finished with success after 243ms
Nov 14 16:17:00 vm921 PackageKit: get-updates transaction
/1648_cbdededb from uid 1000 finished with success after 247ms
Nov 14 16:17:00 vm921 PackageKit: get-updates transaction
/1649_bdacdeaa from uid 1000 finished with success after 238ms
Nov 14 16:17:01 vm921 CRON[55165]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
Nov 14 16:22:57 vm921 PackageKit: refresh-cache transaction
/1651_adbccadb from uid 1000 finished with success after 828ms
Nov 14 16:22:58 vm921 PackageKit: get-updates transaction
/1652_abbddcbb from uid 1000 finished with success after 693ms
Nov 14 16:22:58 vm921 PackageKit: get-updates transaction
/1653_babbeddd from uid 1000 finished with success after 217ms
Nov 14 16:23:00 vm921 PackageKit: get-updates transaction
/1655_ccabdeae from uid 1000 finished with success after 229ms
Nov 14 16:23:00 vm921 PackageKit: get-updates transaction
/1656_bbeadecb from uid 1000 finished with success after 220ms
On my real hardware systems the refresh-cache transaction can last
up to 300-400 seconds
## syslog entry from a "real" system that was up for a while
Nov 14 14:59:48 sake PackageKit: refresh-cache transaction
/80459_bbcaceec from uid 1000 finished with success after 374505ms
You can also see how many transactions that sytem is up to 80459!
I also installed a Gnome GUI installation on a VM. Other than that,
everything was the same. This setup installed and runs FINE.
No packagekit issues.
This seems like an installation parameter configuration problem, but
I can't
figure out what to change/fix. Since it is absolutely reproducable,
what
can I try next on my other systems other than un-installing packagekit?
Since I have several VM copies, I can experiment is someone has some
suggestions...
Thanks...gmc
-- System Information:
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages packagekit depends on:
ii libapt-inst2.0 1.4.8
ii libapt-pkg5.0 1.4.8
ii libc6 2.24-11+deb9u1
ii libgcc1 1:6.3.0-18
ii libglib2.0-0 2.50.3-2
ii libglib2.0-bin 2.50.3-2
ii libgstreamer1.0-0 1.10.4-1
ii libpackagekit-glib2-18 1.1.5-2
ii libpolkit-gobject-1-0 0.105-18
ii libsqlite3-0 3.16.2-5
ii libstdc++6 6.3.0-18
ii libsystemd0 232-25+deb9u1
ii policykit-1 0.105-18
Versions of packages packagekit recommends:
ii packagekit-tools 1.1.5-2
Versions of packages packagekit suggests:
pn appstream <none>
-- no debconf information
