-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packagekitd eats up CPU on Debian+Gnome-shell #740
Comments
When
|
Hi, Thanks! Gnome-software is already set to manual updates. Finally i had time : From top (it will hit 100% soon) :
Pkmon :
journalctl -xb /usr/libexec/packagekitd is full of this :
After running pkcon update, packagekitd CPU consuming tasks ended, and pkmon remains silent. So this will be a gnome-software related issue? |
I'm not sure if this is related to the issues you are seeing but perhaps this will help: I have also noticed excessive CPU usage and battery drain recently and tracked it down to the packagekit daemon. I also discovered that Debian is in the process of updating several packages to use 64-bit time data structures but has not finished the transition and as a result, some packages, like Thunderbird, Firefox and a few others, have dependencies on versions of packages that are still in transition to 64-bit time structures and therefore they cannot be updated. But packagekit keeps trying endlessly to update those packages. By using apt or aptitude to put a hold on the packages with unsatisfied dependencies, packagekit stops trying to update them and CPU usage has gone back to something reasonable. |
Yes, this is GNOME Software hammering the daemon with requests, and PackageKit just fulfills those. There have been multiple changes on the GNOME Software side already, and one tweak just got merged into PK today - so with the next releases of both GNOME and PackageKit, this situation will hopefully improve. This issue happens less on Fedora, apparently, so it was only noticed once the latest GNOME Software was uploaded to Debian unstable. |
@horvathcsabalaszlo: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2462 is the issue mentioned above by |
@hknox: What is the version of Debian ? |
Trixie - testingSent from an iPhone....On Apr 16, 2024, at 22:15, sidt4 ***@***.***> wrote:
@hknox: What is the version of Debian ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Okay. Then it's #740 (comment). |
Thanks for this. Updates to many packages are waiting for the 64-bit time_t transition including gnome packages. I’ll practice patience. HankSent from an iPhone....On Apr 16, 2024, at 22:30, sidt4 ***@***.***> wrote:
Trixie - testing
Okay. Then it's #740 (comment).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thanks for the information (and to all who commented to this. ) |
I have
I wonder that -beta-1 is older than 46.0 :D |
Here is the GNOME version lifecyle for a package: 46.alpha -> 46.beta -> 46.rc -> 46.0 -> 46.1 ... etc |
Thanks :) |
I am experiencing the same thing, thanks for the replies @sidt4! |
Hi,
I have some Debian Testing machines, and all of them has the issue with Packagekitd. The typical situation 👍
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1016570 root 20 0 449040 38576 19084 S 64,5 0,2 2:53.20 packagekitd
But it goes up to 100% CPU usage.
The version is packagekit/testing,testing,now 1.2.8-2 amd64 (the other components are matching)
I have enabled the ShutdownTimeout=300 option, but does not help.
So i need to disable packagekitd if i don't want to get high CPU usage. But the packagekitd is needed for the apt-get upgrade process to work correctly, so i better want to avoid the disabling of packagekitd.
Is this a common problem? Can you please check? I'll be thankful :)
The text was updated successfully, but these errors were encountered: