Package: location Version: 0.9.16-2.1 Severity: normal I've found that restarting location-update (as needrestart prompts me to do after upgrading Python or a shared library it uses) can take ages, to the point where I generally give up and kill the systemctl process, letting the start job continue in the background. Curiously, the service starts fine on boot.
Could you please take a look? Please let me know if I can provide any further information that would be helpful. Thanks! -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'oldstable-security'), (500, 'testing'), (300, 'unstable-debug'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages location depends on: ii python3 3.11.4-5+b1 ii python3-location 0.9.16-2.1 location recommends no packages. location suggests no packages. -- debconf-show failed
