Hello, Matthias! Thank you for your quick reply. This pair of messages appears all through '.xsession-errors':
(gnome-settings-daemon:4690): PackageKit-WARNING **: couldn't parse execption 'GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_5ftransaction_5ferror.Code4: GetDistroUpgrades not supported by backend', please report (gnome-settings-daemon:4690): updates-plugin-WARNING **: failed to get upgrades: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_5ftransaction_5ferror.Code4: GetDistroUpgrades not supported by backend As mentioned previously, contrary to the documentation, '/var/log/PackageKit' does not exist. Perhaps the cause of the log file not existing is that transactions don't actually complete? Regarding the low cost of the service starting, I am aware that it costs next to nothing in terms of resources, but the starting without knowing which component is doing so, and not knowing the intent of the autostart (i.e. what is _supposed_ to be happening, and how often is it supposed to happen?) muddies the waters of understanding and makes it more difficult to configure and/or debug other package management services and helpers (i.e. update-notifier). In the googling I did in order to research this problem I found I was not alone in wondering about this spordadic starting and the attending syslog spam, One person said they used to receive the messages every hour, but that now it is down to 6 or 7 minutes. I will try and get a bustle log and report back. Thank you again for your attention in this matter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
