Bug 1820931
Summary: | PackageKit get-updates being called every second | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Andrew Munn <andrew> |
Component: | PackageKit | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | CentOS Stream | CC: | bstinson, carl, jwboyer, klember |
Target Milestone: | rc | Flags: | andrew:
needinfo-
|
Target Release: | 8.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-10-04 07:26:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew Munn
2020-04-04 21:41:08 UTC
> killing gnome-software does not effect it
PackageKit does not schedule it's own transactions. Something must be calling into PackageKit in a loop. Are you running stock GNOME from Centos? Is this a clean install?
This was a clean install of Centos 8.1 with default gnome. Some updates may have been applied after the install. I only noticed this because it was installed on a noisy old hard drive that I could hear writing every second. Maybe updates since April have fixed it or maybe it's still happening because I see this one one of my CentOS VMs now: # uname -a Linux prod 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul 26 03:54:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # systemctl status packagekit ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: inactive (dead) Sep 20 19:11:32 prod PackageKit[1417254]: get-updates transaction /1034072_deecbada from uid 1000 finished with success after 36ms Sep 20 19:11:33 prod PackageKit[1417254]: get-updates transaction /1034073_aabceeed from uid 1000 finished with success after 37ms Sep 20 19:11:33 prod PackageKit[1417254]: get-updates transaction /1034074_ecdbeeed from uid 1000 finished with success after 29ms Sep 20 19:11:34 prod PackageKit[1417254]: get-updates transaction /1034075_cbdebeaa from uid 1000 finished with success after 30ms Sep 20 19:11:34 prod PackageKit[1417254]: get-updates transaction /1034076_bbcdbcda from uid 1000 finished with success after 37ms Sep 20 19:11:35 prod PackageKit[1417254]: get-updates transaction /1034077_ebbbcaca from uid 1000 finished with success after 37ms Sep 20 19:11:35 prod PackageKit[1417254]: get-updates transaction /1034078_ccdedcae from uid 1000 finished with success after 33ms Sep 20 19:11:36 prod PackageKit[1417254]: get-updates transaction /1034079_dddcdbcd from uid 1000 finished with success after 34ms Sep 20 19:11:36 prod PackageKit[1417254]: get-updates transaction /1034080_cedebccb from uid 1000 finished with success after 26ms Sep 20 19:16:38 prod PackageKit[1417254]: daemon quit Should it be running twice a second like that? You need to find the process that's calling PackageKit. Maybe top or ps would help? After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |