Package: unattended-upgrades Version: 1.9 Severity: important Dear Maintainer,
* What led up to the situation? On my laptop the fan started running unexpectedly. Starting KDE's systemmonitor it showed unattended-upgrades using 25% of CPU. The laptop was offline at ths time. * What outcome did you expect instead? In my opinion, unattended-ugrades should use minimal system resources as a background process. I have also doubts that it can do anything useful on an offline system. Best wishes, Gábor -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8), LANGUAGE=hu:en_US:de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unattended-upgrades depends on: ii debconf [debconf-2.0] 1.5.69 ii lsb-base 10.2018112800 ii lsb-release 10.2018112800 ii python3 3.7.1-2 ii python3-apt 1.7.0 ii python3-dbus 1.2.8-2+b2 ii python3-distro-info 0.20 ii ucf 3.0038 ii xz-utils 5.2.2-1.3 Versions of packages unattended-upgrades recommends: ii anacron 2.3-27 ii cron [cron-daemon] 3.0pl1-130 ii systemd-sysv 239-15 Versions of packages unattended-upgrades suggests: ii bsd-mailx 8.1.2-0.20180807cvs-1 ii dma [mail-transport-agent] 0.11-1+b1 ii needrestart 3.3-2 ii powermgmt-base 1.33 ii python3-gi 3.30.4-1 -- debconf information: unattended-upgrades/enable_auto_updates: true unattended-upgrades/origins_pattern: "origin=Debian,codename=${distro_codename},label=Debian-Security";