Debian Bug report logs - #665477
packagekit: dbus reports 'Activating service ...PackageKit' at random intervals throughout the day

version graph

Package: packagekit; Maintainer for packagekit is Matthias Klumpp <mak@debian.org>; Source for packagekit is src:packagekit (PTS, buildd, popcon).

Reported by: Dominique Brazziel <dbrazziel@snet.net>

Date: Sat, 24 Mar 2012 15:15:01 UTC

Severity: minor

Found in version packagekit/0.7.3-2

Done: Matthias Klumpp <matthias@tenstral.net>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Information forwarded to debian-bugs-dist@lists.debian.org, Matthias Klumpp <matthias@tenstral.net>:
Bug#665477; Package packagekit. (Sat, 24 Mar 2012 15:15:04 GMT) (full text, mbox, link).

Acknowledgement sent to Dominique Brazziel <dbrazziel@snet.net>:
Extra info received and forwarded to list. Copy sent to Matthias Klumpp <matthias@tenstral.net>. (Sat, 24 Mar 2012 15:15:10 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Dominique Brazziel <dbrazziel@snet.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: packagekit: dbus reports 'Activating service ...PackageKit' at random intervals throughout the day
Date: Sat, 24 Mar 2012 11:12:34 -0400
Package: packagekit
Version: 0.7.3-2
Severity: normal

Dear Maintainer,

    Why is packagekit starting up throughout the day?  There is no
indication in the messages which component is sending the message to
start packagekit, just a dbus message indicating that the service
was started:

dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'

This pair of messages appears throughout the day, but the intervals are not fixed:

Mar 24 07:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 07:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 07:28:04 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 07:28:04 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 08:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 08:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 08:27:07 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 08:27:07 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 08:42:07 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 08:42:07 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 09:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 09:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 09:20:00 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 09:20:00 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 09:58:13 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 09:58:14 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 24 10:20:25 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 24 10:20:25 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'

The doc (src/packagekit/packagekit-0.7.2/docs/api/html/config-main.html#config-main-logging)
says transaction logging will go to '/var/log/PackageKit', but it does not.
Setting 'Check for updates' to 'never' and 'Automatically install' to 'nothing' 
via gpk-prefs has no effect on these messages or PackageKit waking up.  

I get updates (including security) from a daily cron job ('/etc/cron.daily/apt')
 and update-notifier tells me about them.  I don't need packagekit checking for 
 updates and don't want the service activated from any source that I don't know about

1.  What is waking up packagekit (sending the message to 'org.freedesktop.PackageKit')?
2.  Is there a method to control how often the service is awakened or, better yet,
    disable it without hitting it with a hammer (i.e. removing the service or setting it
    to '/bin/true').



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.4-interatom (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages packagekit depends on:
ii  libarchive12              3.0.3-6
ii  libc6                     2.13-27
ii  libglib2.0-0              2.30.2-6
ii  libglib2.0-bin            2.30.2-6
ii  libpackagekit-glib2-14    0.7.3-2
ii  libpolkit-backend-1-0     0.104-2
ii  libpolkit-gobject-1-0     0.104-2
ii  libsqlite3-0              3.7.10-1
ii  packagekit-backend-aptcc  0.7.3-2

packagekit recommends no packages.

Versions of packages packagekit suggests:
pn  packagekit-backend-smart  <none>

-- Configuration Files:
/etc/PackageKit/PackageKit.conf changed:
[Daemon]
TransactionLogging=true
UseNetworkManager=false
UseNetworkConnman=false
UseNetworkHeuristic=true
UseRemainingTimeEstimation=true
ShutdownTimeout=300
BackendShutdownTimeout=5
BackendSpawnNiceValue=0
BackendSpawnNiceValueBackground=10
BackendSpawnIdleIO=true
BackendSpawnIdleIOBackground=true
BackendSpawnAllowSIGKILL=true
DefaultBackend=aptcc
UseSyslog=false
ScanDesktopFiles=true
UpdatePackageList=true
UpdateCheckProcesses=true
CheckSharedLibrariesInUse=true
CheckTestingRepos=true
UseUpdateCache=false
DeveloperMode=false
StateChangedTimeoutPriority=30
StateChangedTimeoutNormal=600
SimultaneousTransactionsForUid=500
MaximumItemsToResolve=3200
MaximumPackagesToProcess=4000
TransactionCreateCommitTimeout=300
TransactionKeepFinishedTimeout=5
UseIdleBandwidth=true
NoUpdateProcessList=/usr/lib/*/firefox;/usr/lib/*/iceweasel
UseThreadsInBackend=true
UseRoot=/
CancelBackgroundTransactions=true


-- no debconf information

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#665477; Package packagekit. (Sat, 24 Mar 2012 15:58:20 GMT) (full text, mbox, link).

Acknowledgement sent to Matthias Klumpp <matthias@tenstral.net>:
Extra info received and forwarded to list. (Sat, 24 Mar 2012 15:58:25 GMT) (full text, mbox, link).

Message #10 received at 665477@bugs.debian.org (full text, mbox, reply):

From: Matthias Klumpp <matthias@tenstral.net>
To: Dominique Brazziel <dbrazziel@snet.net>, 665477@bugs.debian.org
Cc: control@bugs.debian.org
Subject: Re: Bug#665477: packagekit: dbus reports 'Activating service ...PackageKit' at random intervals throughout the day
Date: Sat, 24 Mar 2012 16:54:39 +0100
severity 665477 minor
thankyou

Hi!
Hmm, usually PK should not be activated that often. I think maybe
GNOME-Settings-Daemon does that...
The log file /var/log/PackageKit will help so we know which action is requested.
Or even better, install "bustle" and run "bustle-dbus-monitor --system
> bustle.out.log" and send me the resulting log file via mail. (you
don't need to attach it to this bug report)
This would help for the start.
But btw, packagekitd starting is not really a big deal, it doesn't
take much resources and should not lock your package db too. (But of
course it's weird that PK is run that often)
Regards,
    Matthias Klumpp

2012/3/24 Dominique Brazziel <dbrazziel@snet.net>:
> Package: packagekit
> Version: 0.7.3-2
> Severity: normal
>
> Dear Maintainer,
>
>    Why is packagekit starting up throughout the day?  There is no
> indication in the messages which component is sending the message to
> start packagekit, just a dbus message indicating that the service
> was started:
>
> dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>
> This pair of messages appears throughout the day, but the intervals are not fixed:
>
> Mar 24 07:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 07:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 07:28:04 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 07:28:04 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 08:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 08:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 08:27:07 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 08:27:07 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 08:42:07 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 08:42:07 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 09:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 09:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 09:20:00 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 09:20:00 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 09:58:13 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 09:58:14 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
> Mar 24 10:20:25 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
> Mar 24 10:20:25 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>
> The doc (src/packagekit/packagekit-0.7.2/docs/api/html/config-main.html#config-main-logging)
> says transaction logging will go to '/var/log/PackageKit', but it does not.
> Setting 'Check for updates' to 'never' and 'Automatically install' to 'nothing'
> via gpk-prefs has no effect on these messages or PackageKit waking up.
>
> I get updates (including security) from a daily cron job ('/etc/cron.daily/apt')
>  and update-notifier tells me about them.  I don't need packagekit checking for
>  updates and don't want the service activated from any source that I don't know about
>
> 1.  What is waking up packagekit (sending the message to 'org.freedesktop.PackageKit')?
> 2.  Is there a method to control how often the service is awakened or, better yet,
>    disable it without hitting it with a hammer (i.e. removing the service or setting it
>    to '/bin/true').
>
>
>
> -- System Information:
> Debian Release: wheezy/sid
>  APT prefers testing
>  APT policy: (990, 'testing'), (500, 'unstable')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.2.4-interatom (SMP w/2 CPU cores; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages packagekit depends on:
> ii  libarchive12              3.0.3-6
> ii  libc6                     2.13-27
> ii  libglib2.0-0              2.30.2-6
> ii  libglib2.0-bin            2.30.2-6
> ii  libpackagekit-glib2-14    0.7.3-2
> ii  libpolkit-backend-1-0     0.104-2
> ii  libpolkit-gobject-1-0     0.104-2
> ii  libsqlite3-0              3.7.10-1
> ii  packagekit-backend-aptcc  0.7.3-2
>
> packagekit recommends no packages.
>
> Versions of packages packagekit suggests:
> pn  packagekit-backend-smart  <none>
>
> -- Configuration Files:
> /etc/PackageKit/PackageKit.conf changed:
> [Daemon]
> TransactionLogging=true
> UseNetworkManager=false
> UseNetworkConnman=false
> UseNetworkHeuristic=true
> UseRemainingTimeEstimation=true
> ShutdownTimeout=300
> BackendShutdownTimeout=5
> BackendSpawnNiceValue=0
> BackendSpawnNiceValueBackground=10
> BackendSpawnIdleIO=true
> BackendSpawnIdleIOBackground=true
> BackendSpawnAllowSIGKILL=true
> DefaultBackend=aptcc
> UseSyslog=false
> ScanDesktopFiles=true
> UpdatePackageList=true
> UpdateCheckProcesses=true
> CheckSharedLibrariesInUse=true
> CheckTestingRepos=true
> UseUpdateCache=false
> DeveloperMode=false
> StateChangedTimeoutPriority=30
> StateChangedTimeoutNormal=600
> SimultaneousTransactionsForUid=500
> MaximumItemsToResolve=3200
> MaximumPackagesToProcess=4000
> TransactionCreateCommitTimeout=300
> TransactionKeepFinishedTimeout=5
> UseIdleBandwidth=true
> NoUpdateProcessList=/usr/lib/*/firefox;/usr/lib/*/iceweasel
> UseThreadsInBackend=true
> UseRoot=/
> CancelBackgroundTransactions=true
>
>
> -- no debconf information
>
>

Severity set to 'minor' from 'normal' Request was from Matthias Klumpp <matthias@tenstral.net> to control@bugs.debian.org. (Sat, 24 Mar 2012 15:58:30 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Matthias Klumpp <matthias@tenstral.net>:
Bug#665477; Package packagekit. (Sun, 25 Mar 2012 19:15:06 GMT) (full text, mbox, link).

Acknowledgement sent to Dominique Brazziel <dbrazziel@snet.net>:
Extra info received and forwarded to list. Copy sent to Matthias Klumpp <matthias@tenstral.net>. (Sun, 25 Mar 2012 19:15:06 GMT) (full text, mbox, link).

Message #17 received at 665477@bugs.debian.org (full text, mbox, reply):

From: Dominique Brazziel <dbrazziel@snet.net>
To: 665477@bugs.debian.org
Subject: gnome-settings-daemon probably is the culprit
Date: Sun, 25 Mar 2012 15:12:02 -0400
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.

Information forwarded to debian-bugs-dist@lists.debian.org, Matthias Klumpp <matthias@tenstral.net>:
Bug#665477; Package packagekit. (Tue, 27 Mar 2012 16:18:03 GMT) (full text, mbox, link).

Acknowledgement sent to Dominique Brazziel <dbrazziel@snet.net>:
Extra info received and forwarded to list. Copy sent to Matthias Klumpp <matthias@tenstral.net>. (Tue, 27 Mar 2012 16:18:03 GMT) (full text, mbox, link).

Message #22 received at 665477@bugs.debian.org (full text, mbox, reply):

From: Dominique Brazziel <dbrazziel@snet.net>
To: 665477@bugs.debian.org
Subject: bustle output
Date: Tue, 27 Mar 2012 12:15:42 -0400
	I ran bustle-dbus-monitor for a couple of hours this morning on a
lightly loaded system (a VNC session actually) and mailed you the
output.  I saw a few PackageKit signals in there, hope it is of some
use.

Information forwarded to debian-bugs-dist@lists.debian.org, Matthias Klumpp <matthias@tenstral.net>:
Bug#665477; Package packagekit. (Sun, 01 Apr 2012 13:51:06 GMT) (full text, mbox, link).

Acknowledgement sent to Dominique Brazziel <dbrazziel@snet.net>:
Extra info received and forwarded to list. Copy sent to Matthias Klumpp <matthias@tenstral.net>. (Sun, 01 Apr 2012 13:51:08 GMT) (full text, mbox, link).

Message #27 received at 665477@bugs.debian.org (full text, mbox, reply):

From: Dominique Brazziel <dbrazziel@snet.net>
To: 665477@bugs.debian.org
Subject: Correction: one hour interval is in effect
Date: Sun, 01 Apr 2012 09:47:50 -0400
	It seems that the gnome-settings-daemon 'updates' plugin
is responsible for many of the packagekit updates, as
'gsd-updates-refresh' indicates:

#define PERIODIC_CHECK_TIME     60*60   /* poke PackageKit every hour */

I run rsyslog which receives messages from another machine which runs 2
desktop sessions (one native, one VNC) and do the updates faithfully in
addition to some ad-hoc command line apt(itude) work, so didn't notice
the one hour interval when I initially perused the logs.  Upon initial
viewing without knowing about the g-s-d updates plugin it just seemed
like a storm of activations with no discernible source.   

	If the one hour trigger from each of the g-s-d processes is sifted out
of the messages, what is left might be attributed to dpkg and apt-get
update post-invoke calls from '/etc/apt/apt.conf.d/20packagekit'.  

	OK to close this, and thank you for the hint about g-s-d and for your
fine work with Debian.

Reply sent to Matthias Klumpp <matthias@tenstral.net>:
You have taken responsibility. (Wed, 18 Apr 2012 22:18:11 GMT) (full text, mbox, link).

Notification sent to Dominique Brazziel <dbrazziel@snet.net>:
Bug acknowledged by developer. (Wed, 18 Apr 2012 22:18:13 GMT) (full text, mbox, link).

Message #32 received at 665477-close@bugs.debian.org (full text, mbox, reply):

From: Matthias Klumpp <matthias@tenstral.net>
To: Dominique Brazziel <dbrazziel@snet.net>, 665477-close@bugs.debian.org
Subject: Re: Bug#665477: packagekit: dbus reports 'Activating service ...PackageKit' at random intervals throughout the day
Date: Thu, 19 Apr 2012 00:15:19 +0200
Hi!
Well, maybe this function in GSD needs a setting somewhere... Thanks
for looking into it! :) In the end, it could've been only GSD causing
this behavior
If you find anything else which looks weird, please notify me!
Regads,
    Matthias

2012/3/24 Matthias Klumpp <matthias@tenstral.net>:
> severity 665477 minor
> thankyou
>
> Hi!
> Hmm, usually PK should not be activated that often. I think maybe
> GNOME-Settings-Daemon does that...
> The log file /var/log/PackageKit will help so we know which action is requested.
> Or even better, install "bustle" and run "bustle-dbus-monitor --system
>> bustle.out.log" and send me the resulting log file via mail. (you
> don't need to attach it to this bug report)
> This would help for the start.
> But btw, packagekitd starting is not really a big deal, it doesn't
> take much resources and should not lock your package db too. (But of
> course it's weird that PK is run that often)
> Regards,
>    Matthias Klumpp
>
> 2012/3/24 Dominique Brazziel <dbrazziel@snet.net>:
>> Package: packagekit
>> Version: 0.7.3-2
>> Severity: normal
>>
>> Dear Maintainer,
>>
>>    Why is packagekit starting up throughout the day?  There is no
>> indication in the messages which component is sending the message to
>> start packagekit, just a dbus message indicating that the service
>> was started:
>>
>> dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>>
>> This pair of messages appears throughout the day, but the intervals are not fixed:
>>
>> Mar 24 07:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 07:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 07:28:04 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 07:28:04 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 08:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 08:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 08:27:07 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 08:27:07 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 08:42:07 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 08:42:07 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 09:03:16 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 09:03:16 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 09:20:00 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 09:20:00 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 09:58:13 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 09:58:14 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>> Mar 24 10:20:25 asusb202 dbus[2560]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
>> Mar 24 10:20:25 asusb202 dbus[2560]: [system] Successfully activated service 'org.freedesktop.PackageKit'
>>
>> The doc (src/packagekit/packagekit-0.7.2/docs/api/html/config-main.html#config-main-logging)
>> says transaction logging will go to '/var/log/PackageKit', but it does not.
>> Setting 'Check for updates' to 'never' and 'Automatically install' to 'nothing'
>> via gpk-prefs has no effect on these messages or PackageKit waking up.
>>
>> I get updates (including security) from a daily cron job ('/etc/cron.daily/apt')
>>  and update-notifier tells me about them.  I don't need packagekit checking for
>>  updates and don't want the service activated from any source that I don't know about
>>
>> 1.  What is waking up packagekit (sending the message to 'org.freedesktop.PackageKit')?
>> 2.  Is there a method to control how often the service is awakened or, better yet,
>>    disable it without hitting it with a hammer (i.e. removing the service or setting it
>>    to '/bin/true').
>>
>>
>>
>> -- System Information:
>> Debian Release: wheezy/sid
>>  APT prefers testing
>>  APT policy: (990, 'testing'), (500, 'unstable')
>> Architecture: i386 (i686)
>>
>> Kernel: Linux 3.2.4-interatom (SMP w/2 CPU cores; PREEMPT)
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>>
>> Versions of packages packagekit depends on:
>> ii  libarchive12              3.0.3-6
>> ii  libc6                     2.13-27
>> ii  libglib2.0-0              2.30.2-6
>> ii  libglib2.0-bin            2.30.2-6
>> ii  libpackagekit-glib2-14    0.7.3-2
>> ii  libpolkit-backend-1-0     0.104-2
>> ii  libpolkit-gobject-1-0     0.104-2
>> ii  libsqlite3-0              3.7.10-1
>> ii  packagekit-backend-aptcc  0.7.3-2
>>
>> packagekit recommends no packages.
>>
>> Versions of packages packagekit suggests:
>> pn  packagekit-backend-smart  <none>
>>
>> -- Configuration Files:
>> /etc/PackageKit/PackageKit.conf changed:
>> [Daemon]
>> TransactionLogging=true
>> UseNetworkManager=false
>> UseNetworkConnman=false
>> UseNetworkHeuristic=true
>> UseRemainingTimeEstimation=true
>> ShutdownTimeout=300
>> BackendShutdownTimeout=5
>> BackendSpawnNiceValue=0
>> BackendSpawnNiceValueBackground=10
>> BackendSpawnIdleIO=true
>> BackendSpawnIdleIOBackground=true
>> BackendSpawnAllowSIGKILL=true
>> DefaultBackend=aptcc
>> UseSyslog=false
>> ScanDesktopFiles=true
>> UpdatePackageList=true
>> UpdateCheckProcesses=true
>> CheckSharedLibrariesInUse=true
>> CheckTestingRepos=true
>> UseUpdateCache=false
>> DeveloperMode=false
>> StateChangedTimeoutPriority=30
>> StateChangedTimeoutNormal=600
>> SimultaneousTransactionsForUid=500
>> MaximumItemsToResolve=3200
>> MaximumPackagesToProcess=4000
>> TransactionCreateCommitTimeout=300
>> TransactionKeepFinishedTimeout=5
>> UseIdleBandwidth=true
>> NoUpdateProcessList=/usr/lib/*/firefox;/usr/lib/*/iceweasel
>> UseThreadsInBackend=true
>> UseRoot=/
>> CancelBackgroundTransactions=true
>>
>>
>> -- no debconf information
>>
>>

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Thu, 17 May 2012 07:41:30 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sat Jan 13 06:07:26 2018; Machine Name: beach

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.