At times my systems gets slow and unresponsive. Apparently on those cases PackageKit is the culprit, for example: top - 15:46:56 up 5:40, 2 users, load average: 1.74, 2.04, 2.63 Tasks: 385 total, 1 running, 384 sleeping, 0 stopped, 0 zombie %Cpu(s): 31.5 us, 1.8 sy, 0.0 ni, 65.7 id, 0.8 wa, 0.2 hi, 0.1 si, 0.0 st MiB Mem : 15677.2 total, 1172.9 free, 9506.5 used, 5496.7 buff/cache MiB Swap: 16384.0 total, 12173.7 free, 4210.2 used. 6170.7 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3873 root 20 0 8339668 4.8g 21548 S 79.4 31.3 290:25.73 packagekitd In general I just kill it to get back my resources. In the example above it's using "only" 4.8GB from my 16GB RAM, but if I leave it running longer it'll take more. Reproducible: Sometimes Steps to Reproduce: 1. Start system 2. Do stuff with the system 3. Note an unresponsive system after some time (hours?). Actual Results: Lot of memory consumption by PackageKit Expected Results: A well behaving Packagekit.
This is in the journal: Feb 24 15:53:02 desktop-pc PackageKit[3873]: update-packages transaction /4580803_dbdccbee from uid 10011 finished with need-untrusted after 254ms Feb 24 15:53:02 desktop-pc PackageKit[3873]: new update-packages transaction /4580804_eddbadab scheduled from uid 10011 Feb 24 15:53:03 desktop-pc PackageKit[3873]: update-packages transaction /4580804_eddbadab from uid 10011 finished with need-untrusted after 238ms Feb 24 15:53:03 desktop-pc PackageKit[3873]: new update-packages transaction /4580805_cceaabbc scheduled from uid 10011 Feb 24 15:53:03 desktop-pc PackageKit[3873]: update-packages transaction /4580805_cceaabbc from uid 10011 finished with need-untrusted after 244ms Feb 24 15:53:03 desktop-pc PackageKit[3873]: new update-packages transaction /4580806_aceebced scheduled from uid 10011 Feb 24 15:53:03 desktop-pc PackageKit[3873]: update-packages transaction /4580806_aceebced from uid 10011 finished with need-untrusted after 243ms Feb 24 15:53:03 desktop-pc PackageKit[3873]: new update-packages transaction /4580807_eecdadea scheduled from uid 10011 Feb 24 15:53:04 desktop-pc PackageKit[3873]: update-packages transaction /4580807_eecdadea from uid 10011 finished with need-untrusted after 243ms Feb 24 15:53:04 desktop-pc PackageKit[3873]: new update-packages transaction /4580808_ddaacbec scheduled from uid 10011 Feb 24 15:53:04 desktop-pc PackageKit[3873]: update-packages transaction /4580808_ddaacbec from uid 10011 finished with need-untrusted after 241ms Feb 24 15:53:04 desktop-pc PackageKit[3873]: new update-packages transaction /4580809_bcbbdacb scheduled from uid 10011 Feb 24 15:53:04 desktop-pc PackageKit[3873]: update-packages transaction /4580809_bcbbdacb from uid 10011 finished with need-untrusted after 246ms Feb 24 15:53:04 desktop-pc PackageKit[3873]: new update-packages transaction /4580810_ccbcbaca scheduled from uid 10011 Feb 24 15:53:04 desktop-pc PackageKit[3873]: update-packages transaction /4580810_ccbcbaca from uid 10011 finished with need-untrusted after 247ms Feb 24 15:53:05 desktop-pc PackageKit[3873]: new update-packages transaction /4580811_ebeaacab scheduled from uid 10011 Feb 24 15:53:05 desktop-pc PackageKit[3873]: update-packages transaction /4580811_ebeaacab from uid 10011 finished with need-untrusted after 240ms Feb 24 15:53:05 desktop-pc PackageKit[3873]: new update-packages transaction /4580812_daedcdce scheduled from uid 10011 Feb 24 15:53:05 desktop-pc PackageKit[3873]: update-packages transaction /4580812_daedcdce from uid 10011 finished with need-untrusted after 243ms Feb 24 15:53:05 desktop-pc PackageKit[3873]: new update-packages transaction /4580813_ebceccec scheduled from uid 10011 This goes on and on and on and on....
I have the same problem in Fedora 39. RSS of packagekitd just grew to about 1G right after booting the system. After restarting packagekit via systemctl the memory usage was low for a while. I could cause packagekitd to grow to 500MB (RSS) quite easily with "pkcon get-packages" and "pkgcon get-updates". If any additional information would be helpful, please let me know.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.