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
Flooding of "get-updates" every second #322
Comments
if you do "killall gnome-software" do the events stop? Can you find the name of ":1.3112" in d-feet? |
":1.3112" in this case is "org.freedesktop.PackageKit". It is sending the results (asynchronously) as property changes to transactions. |
I guess this means it's something in your user account, rather than something running as root. Maybe check what's running at startup compared to the other computers? |
Good catch with the uid, this really helped me discover the issue. :) So, it ended up being Byobu. Specifically, its default configuration (at least on Fedora) uses this line in updates_available for its status notification, which indeed keeps getting updated every second. When I exited Byobu the log flooding stopped. But, now I have a question: Is Byobu doing the right thing here with PackageKit? Is it reasonable to do |
No, it's a really dumb way to do it :) The smart way is do GetUpdates on coldplug and then watch for the |
Thank you! I will open a bug on Byobu and direct them here. |
I'm at my wits end with this issue! Basically every second something is calling PackageKit with a "get-updates".
It's on a newly installed Fedora 30 system with PackageKit 1.1.12, though I also had the same issue with Fedora 29 (which is one reason that I upgraded). I do not have it with other Fedora 29 and 30 systems (I have about 10!) so there must be something special about this box.
I know it's not GNOME Software causing this -- I already set it to not update. But I don't know how to figure out who is calling. Is there something in DBus I can use to trace it, perhaps? Here's what I have:
journalctl
shows this:Using
pkmon
:Using
dbus-monitor --system
:The text was updated successfully, but these errors were encountered: