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 <[email protected]>:
> 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
>
>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
