Description of problem: Byobu when started, causes flooding in logs from packagekitd. Thanks to Alessio help, on ask Fedora we were able to understand the problem, but it wasn't easy. While waiting for the upstream bug to be resolved, I was suggested, again in the help post, to report it on the Fedora side Version-Release number of selected component (if applicable): Fedora 34 byobu.noarch: 5.133-3.fc34 bug upstream: https://bugs.launchpad.net/byobu/+bug/1828115 For more details: https://ask.fedoraproject.org/t/packagekitd-keeps-writing-to-logs-uses-disk-ram-and-cpu/15363
I have a similar problem. packagekitd starts flooding the logs Okt 01 10:21:59 c3274 PackageKit[3872554]: update-packages transaction /91461_deaaacaa from uid 1235242675 finished with need-untrusted after 95ms Okt 01 10:21:59 c3274 PackageKit[3872554]: new update-packages transaction /91462_cedabecb scheduled from uid 1235242675 Okt 01 10:21:59 c3274 PackageKit[3872554]: update-packages transaction /91462_cedabecb from uid 1235242675 finished with need-untrusted after 85ms Okt 01 10:22:00 c3274 PackageKit[3872554]: new update-packages transaction /91463_cddabdea scheduled from uid 1235242675 Okt 01 10:22:00 c3274 PackageKit[3872554]: update-packages transaction /91463_cddabdea from uid 1235242675 finished with need-untrusted after 85ms Okt 01 10:22:00 c3274 PackageKit[3872554]: new update-packages transaction /91464_aadddacc scheduled from uid 1235242675 Okt 01 10:22:00 c3274 PackageKit[3872554]: update-packages transaction /91464_aadddacc from uid 1235242675 finished with need-untrusted after 108ms But i don't use byobu. I use gnome-software and I think packagekitd starts flooding after waking up from hibernate / suspend. This cause high memory usage (my notebook with 32 GB RAM and 16 GB swap) run out of memory. Stopping packagekit "sudo systemctl stop packagekit.service" release 20 GB RAM and half of swap. So I think, the toolings that use packagekit as backend, aren't causing the problem. System: Kernel: 5.14.8-250.vanilla.1.fc34.x86_64 x86_64 bits: 64 compiler: gcc v: 2.35.2-5.fc34 Desktop: Cinnamon 5.0.5 Distro: Fedora release 34 (Thirty Four) Machine: Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: <filter> Mobo: Dell model: 018W12 v: A06 serial: <filter> UEFI: Dell v: 1.11.0 date: 05/31/2021
I do not think this is a byobu problem. It is a packagekit-d problem. The solution is as follows: ### Shutting Down PackageKitD ``` bash dconf write /org/gnome/software/download-updates false sudo systemctl stop packagekit.service sudo systemctl disable packagekit.service ``` This should stop packagekitd which is an unnecessary resource hog. ### References - https://unix.stackexchange.com/questions/280015/what-does-the-process-usr-libexec-packagekitd-do - https://ask.fedoraproject.org/t/packagekitd-keeps-writing-to-logs-uses-disk-ram-and-cpu/15363
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.