Bug#1002732: needrestart stalled in background when performing update with KDE Discover
Perhaps I spoke too hastily earlier, or perhaps the issue only manifests for certain update sets. I have seen the issue again a couple times in the past week or so. When I performed a manual `apt install` to install a random package after, I received a notice that a newer kernel is available. Perhaps that's it? Also note that I have never actually received a desktop notification from debconf-kde-helper, if that was supposed to be the intended behaviour, so perhaps this bug should just be reassigned to that package? Ryan On Sunday, January 2, 2022 8:22:19 A.M. EST Ryan Armstrong wrote: > So, I actually just installed my regular updates today with Discover and > noticed a few library changes. The update completed properly. If I run > needrestart after (or do an apt install), it confirms it wants to restart > some libraries. I can continue to install other packages with Discover as > well. So it looks like that package was all I needed. > > Thanks, > Ryan > > On Saturday, January 1, 2022 8:42:26 A.M. EST Thomas Liske wrote: > > Hi, > > > > could you check running needrestart as root on cli if you have any > > pending restarts? > > > > You might try to reinstall a lib to trigger needrestart (i.e. via apt- > > get install --reinstall libnss3 - this *should* not break anything) to > > force to get a pending restarts. > > > > Please check if needrestart and debconf-kde-helper are working when > > using KDE Discover afterwards. > > > > > > Regards, > > Thomas > > > > On Fri, 2021-12-31 at 10:10 -0500, Ryan Armstrong wrote: > > > I did not, but your message prompted me to go looking a bit. I found > > > I had > > > not installed debconf-kde-helper. I would have expected a package > > > like this to > > > get pulled in when I installed KDE, so I expect it is missing as a > > > dependency > > > (for plasma-discover perhaps?) > > > > > > In my setup, KDE was installed onto an existing setup by running `apt > > > install > > > kde-plasma-desktop` > > > > > > I did one update after installing the helper, but didn't notice > > > anything (it > > > didn't stall, though). As long as that fixes the problem, I guess > > > this bug > > > should be redirected as a dependency issue? > > > > > > Ryan > > > > > > On Friday, December 31, 2021 9:54:02 A.M. EST you wrote: > > > > Hi Ryan, > > > > > > > > needrestart should not block if it is run non-interactive. On > > > > Debian it > > > > uses the debconf frontend which also has graphical frontends. Do > > > > you > > > > get debconf dialogs in KDE Discover when installing/updating > > > > packages > > > > at all? (Sorry I do not have an KDE environment for testing.) > > > > > > > > > > > > Regards, > > > > Thomas > > > > > > > > On Tue, 2021-12-28 at 08:33 -0500, Ryan Armstrong wrote: > > > > > Package: needrestart > > > > > Version: 3.5-5 > > > > > Severity: normal > > > > > > > > > > Dear Maintainer, > > > > > > > > > > When I performed an update with KDE Discover, I noticed it > > > > > stalled at > > > > > 99% complete status and would not finish. When I checked the > > > > > process > > > > > tree with htop, I noticed the following lines from packagekitd > > > > > and > > > > > > > > > > needrestart: > > > > >2629 root 20 0 492M 124M 79624 S 0.0 0.8 0:29.20 > > > > > > > > > > ├─ > > > > > /usr/libexec/packagekitd > > > > > > > > > >2632 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.00 > > > > > > > > > > │ > > > > > ├─ /usr/libexec/packagekitd > > > > > > > > > >2634 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.05 > > > > > > > > > > │ > > > > > ├─ /usr/libexec/packagekitd > > > > > > > > > > 14075 root 20 0 492M 124M 79624 S 0.0 0.8 0:05.78 > > > > > > > > > > │ > > > > > ├─ /usr/libexec/packagekitd > > > > > > > > > > 14090 root 20 0 494M 99648 50800 S 0.0 0.6 0:00.24 > > > > > > > > > > │ > > > > > └─ /usr/libexec/packagekitd > > > > > > > > > > 25864 root 20 0 494M 51924 2336 S 0.0 0.3 0:00.00 > > > > > > > > > > │ └─ /usr/libexec/packagekitd > > > > > > > > > > 25872 root 20 0 2472 704 616 S 0.0 0.0 0:00.00 > > > > > > > > > > │└─ sh -c test -x /usr/lib/needrestart/apt-pinvoke && > > > > > /usr/lib/needrestart/apt-pinvoke || true > > > > > > > > > > 25873 root 20 0 35864 27816 6140 S 0.0 0.2 0:00.64 > > > > > > > > > > │ └─ /usr/bin/perl /usr/sbin/needrestart > > > > > > > > > > It appears that packagekit is still running needrestart to ask if > > > > > I > > > > > want to restart systemd services. However, this prompt is > > > > > obviously > > > > > not > > > > > visible to me through KDE Discover, so it's stuck waiting > > > > > forever. > > > > > > > > > > If I use kill on needrestart, the Discover session completes. > > > > > > > > > > Since, this is an interaction between Discover, packagekit, apt > > > > > and > > > > > needrestart (possibly others?), I'm not 100% sure this is
Bug#1002732: needrestart stalled in background when performing update with KDE Discover
More info from today, where again the update is stalled due to the next
update
# xargs -0n 1 -a /proc/401446/environ echo
DPKG_FRONTEND_LOCKED=true
APT_LISTCHANGES_FRONTEND=none
LANGUAGE=de_DE.UTF-8
PACKAGEKIT_CALLER_UID=2260
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=de_DE.UTF-8
DEBIAN_FRONTEND=noninteractive
PWD=/tmp
APT_LISTBUGS_FRONTEND=none
The message is from
# dpkg -L needrestart | xargs grep -sn --color Return
/usr/share/perl5/NeedRestart/UI/stdio.pm:42:$self->wprint(\*STDOUT, '', '',
__x("Pending kernel upgrade!\n\nRunning kernel version:\n {kversion}\n\nDiagnostics:\n
{message}\n\nRestarting the system to load the new kernel will not be handled
automatically, so you should consider rebooting. [Return]\n",
which is the only available UI package:
env -i DPKG_FRONTEND_LOCKED=true APT_LISTCHANGES_FRONTEND=none LANGUAGE=C.UTF-8
PACKAGEKIT_CALLER_UID=2260
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=de_DE.UTF-8 DEBIAN_FRONTEND=noninteractive PWD=/tmp
APT_LISTBUGS_FRONTEND=none /usr/sbin/needrestart -u \?
Available UI packages:
NeedRestart::UI::stdio
Looking further into /usr/share/perl5/NeedRestart/UI/stdio.pm:
sub _announce {
...
if (-t *STDIN && -t *STDOUT);
}
Combine that with
# lsof -p 401446 -a -d 0-2
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
needresta 401446 root0u CHR 136,3 0t06 /dev/pts/3
needresta 401446 root1u CHR 136,3 0t06 /dev/pts/3
needresta 401446 root2u CHR 136,3 0t06 /dev/pts/3
STDIN and STDOUT are both '/dev/pts/3' which is a pseudo TTY, so the
test evaluates to true and the code tries to read from that PTY; as the
message is not displayed anywhere visible and there is no way to
interact with needrestart from Discover the process hangs.
Philipp
Bug#1002732: needrestart stalled in background when performing update with KDE Discover
So, I actually just installed my regular updates today with Discover and noticed a few library changes. The update completed properly. If I run needrestart after (or do an apt install), it confirms it wants to restart some libraries. I can continue to install other packages with Discover as well. So it looks like that package was all I needed. Thanks, Ryan On Saturday, January 1, 2022 8:42:26 A.M. EST Thomas Liske wrote: > Hi, > > could you check running needrestart as root on cli if you have any > pending restarts? > > You might try to reinstall a lib to trigger needrestart (i.e. via apt- > get install --reinstall libnss3 - this *should* not break anything) to > force to get a pending restarts. > > Please check if needrestart and debconf-kde-helper are working when > using KDE Discover afterwards. > > > Regards, > Thomas > > On Fri, 2021-12-31 at 10:10 -0500, Ryan Armstrong wrote: > > I did not, but your message prompted me to go looking a bit. I found > > I had > > not installed debconf-kde-helper. I would have expected a package > > like this to > > get pulled in when I installed KDE, so I expect it is missing as a > > dependency > > (for plasma-discover perhaps?) > > > > In my setup, KDE was installed onto an existing setup by running `apt > > install > > kde-plasma-desktop` > > > > I did one update after installing the helper, but didn't notice > > anything (it > > didn't stall, though). As long as that fixes the problem, I guess > > this bug > > should be redirected as a dependency issue? > > > > Ryan > > > > On Friday, December 31, 2021 9:54:02 A.M. EST you wrote: > > > Hi Ryan, > > > > > > needrestart should not block if it is run non-interactive. On > > > Debian it > > > uses the debconf frontend which also has graphical frontends. Do > > > you > > > get debconf dialogs in KDE Discover when installing/updating > > > packages > > > at all? (Sorry I do not have an KDE environment for testing.) > > > > > > > > > Regards, > > > Thomas > > > > > > On Tue, 2021-12-28 at 08:33 -0500, Ryan Armstrong wrote: > > > > Package: needrestart > > > > Version: 3.5-5 > > > > Severity: normal > > > > > > > > Dear Maintainer, > > > > > > > > When I performed an update with KDE Discover, I noticed it > > > > stalled at > > > > 99% complete status and would not finish. When I checked the > > > > process > > > > tree with htop, I noticed the following lines from packagekitd > > > > and > > > > needrestart: > > > > > > > >2629 root 20 0 492M 124M 79624 S 0.0 0.8 0:29.20 > > > > ├─ > > > > /usr/libexec/packagekitd > > > >2632 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.00 > > > > │ > > > > ├─ /usr/libexec/packagekitd > > > >2634 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.05 > > > > │ > > > > ├─ /usr/libexec/packagekitd > > > > 14075 root 20 0 492M 124M 79624 S 0.0 0.8 0:05.78 > > > > │ > > > > ├─ /usr/libexec/packagekitd > > > > 14090 root 20 0 494M 99648 50800 S 0.0 0.6 0:00.24 > > > > │ > > > > └─ /usr/libexec/packagekitd > > > > 25864 root 20 0 494M 51924 2336 S 0.0 0.3 0:00.00 > > > > │ └─ /usr/libexec/packagekitd > > > > 25872 root 20 0 2472 704 616 S 0.0 0.0 0:00.00 > > > > │└─ sh -c test -x /usr/lib/needrestart/apt-pinvoke && > > > > /usr/lib/needrestart/apt-pinvoke || true > > > > 25873 root 20 0 35864 27816 6140 S 0.0 0.2 0:00.64 > > > > │ └─ /usr/bin/perl /usr/sbin/needrestart > > > > > > > > It appears that packagekit is still running needrestart to ask if > > > > I > > > > want to restart systemd services. However, this prompt is > > > > obviously > > > > not > > > > visible to me through KDE Discover, so it's stuck waiting > > > > forever. > > > > > > > > If I use kill on needrestart, the Discover session completes. > > > > > > > > Since, this is an interaction between Discover, packagekit, apt > > > > and > > > > needrestart (possibly others?), I'm not 100% sure this is the > > > > right > > > > place for it. Feel free to reassign if I got it wrong. > > > > > > > > Ryan > > > > > > > > -- Package-specific info: > > > > needrestart output: > > > > Your outdated processes: > > > > akonadi_archive[3076], akonadi_mailfil[3102], > > > > akonadi_sendlat[3116], > > > > akonadi_unified[3117], blueman-applet[2663], Discord[2921, 2924, > > > > 2967, 2922, 2958, 2917, 3276, 3044], DiscoverNotifie[2571], > > > > evolution-addre[2767], evolution-alarm[2660], evolution- > > > > calen[2742], > > > > evolution-sourc[2698], goa-daemon[2704], kmail[2936], > > > > kwin_x11[2488], > > > > nextcloud[2656], plasmashell[2554], QtWebEngineProc[6196, 6215, > > > > 6194, > > > > 6193], tracker-miner-f[2674], xdg-desktop-por[2375], xdg- > > > > document- > > > > po[2392], xdg-permission-[2397] > > > > > > > > > > > > > > > > -- System Information: > > > > Debian Release: bookworm/sid > > > > APT prefers testing > > > > APT policy: (900, 'testing'), (300,
Bug#1002732: needrestart stalled in background when performing update with KDE Discover
Hi, could you check running needrestart as root on cli if you have any pending restarts? You might try to reinstall a lib to trigger needrestart (i.e. via apt- get install --reinstall libnss3 - this *should* not break anything) to force to get a pending restarts. Please check if needrestart and debconf-kde-helper are working when using KDE Discover afterwards. Regards, Thomas On Fri, 2021-12-31 at 10:10 -0500, Ryan Armstrong wrote: > I did not, but your message prompted me to go looking a bit. I found > I had > not installed debconf-kde-helper. I would have expected a package > like this to > get pulled in when I installed KDE, so I expect it is missing as a > dependency > (for plasma-discover perhaps?) > > In my setup, KDE was installed onto an existing setup by running `apt > install > kde-plasma-desktop` > > I did one update after installing the helper, but didn't notice > anything (it > didn't stall, though). As long as that fixes the problem, I guess > this bug > should be redirected as a dependency issue? > > Ryan > > On Friday, December 31, 2021 9:54:02 A.M. EST you wrote: > > Hi Ryan, > > > > needrestart should not block if it is run non-interactive. On > > Debian it > > uses the debconf frontend which also has graphical frontends. Do > > you > > get debconf dialogs in KDE Discover when installing/updating > > packages > > at all? (Sorry I do not have an KDE environment for testing.) > > > > > > Regards, > > Thomas > > > > On Tue, 2021-12-28 at 08:33 -0500, Ryan Armstrong wrote: > > > Package: needrestart > > > Version: 3.5-5 > > > Severity: normal > > > > > > Dear Maintainer, > > > > > > When I performed an update with KDE Discover, I noticed it > > > stalled at > > > 99% complete status and would not finish. When I checked the > > > process > > > tree with htop, I noticed the following lines from packagekitd > > > and > > > needrestart: > > > > > > 2629 root 20 0 492M 124M 79624 S 0.0 0.8 0:29.20 > > > ├─ > > > /usr/libexec/packagekitd > > > 2632 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.00 > > > │ > > > ├─ /usr/libexec/packagekitd > > > 2634 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.05 > > > │ > > > ├─ /usr/libexec/packagekitd > > > 14075 root 20 0 492M 124M 79624 S 0.0 0.8 0:05.78 > > > │ > > > ├─ /usr/libexec/packagekitd > > > 14090 root 20 0 494M 99648 50800 S 0.0 0.6 0:00.24 > > > │ > > > └─ /usr/libexec/packagekitd > > > 25864 root 20 0 494M 51924 2336 S 0.0 0.3 0:00.00 > > > │ └─ /usr/libexec/packagekitd > > > 25872 root 20 0 2472 704 616 S 0.0 0.0 0:00.00 > > > │ └─ sh -c test -x /usr/lib/needrestart/apt-pinvoke && > > > /usr/lib/needrestart/apt-pinvoke || true > > > 25873 root 20 0 35864 27816 6140 S 0.0 0.2 0:00.64 > > > │ └─ /usr/bin/perl /usr/sbin/needrestart > > > > > > It appears that packagekit is still running needrestart to ask if > > > I > > > want to restart systemd services. However, this prompt is > > > obviously > > > not > > > visible to me through KDE Discover, so it's stuck waiting > > > forever. > > > > > > If I use kill on needrestart, the Discover session completes. > > > > > > Since, this is an interaction between Discover, packagekit, apt > > > and > > > needrestart (possibly others?), I'm not 100% sure this is the > > > right > > > place for it. Feel free to reassign if I got it wrong. > > > > > > Ryan > > > > > > -- Package-specific info: > > > needrestart output: > > > Your outdated processes: > > > akonadi_archive[3076], akonadi_mailfil[3102], > > > akonadi_sendlat[3116], > > > akonadi_unified[3117], blueman-applet[2663], Discord[2921, 2924, > > > 2967, 2922, 2958, 2917, 3276, 3044], DiscoverNotifie[2571], > > > evolution-addre[2767], evolution-alarm[2660], evolution- > > > calen[2742], > > > evolution-sourc[2698], goa-daemon[2704], kmail[2936], > > > kwin_x11[2488], > > > nextcloud[2656], plasmashell[2554], QtWebEngineProc[6196, 6215, > > > 6194, > > > 6193], tracker-miner-f[2674], xdg-desktop-por[2375], xdg- > > > document- > > > po[2392], xdg-permission-[2397] > > > > > > > > > > > > -- System Information: > > > Debian Release: bookworm/sid > > > APT prefers testing > > > APT policy: (900, 'testing'), (300, 'unstable') > > > Architecture: amd64 (x86_64) > > > Foreign Architectures: i386 > > > > > > Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) > > > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), > > > LANGUAGE=en_GB:en_US > > > Shell: /bin/sh linked to /bin/dash > > > Init: systemd (via /run/systemd/system) > > > LSM: AppArmor: enabled > > > > > > Versions of packages needrestart depends on: > > > ii binutils 2.37-7 > > > ii dpkg 1.21.1 > > > ii gettext-base 0.21-4 > > > ii libintl-perl 1.26-3 > > > ii libmodule-find-perl 0.15-1 > > > ii libmodule-scandeps-perl 1.31-1 > > >
Bug#1002732: needrestart stalled in background when performing update with KDE Discover
Hi Ryan, needrestart should not block if it is run non-interactive. On Debian it uses the debconf frontend which also has graphical frontends. Do you get debconf dialogs in KDE Discover when installing/updating packages at all? (Sorry I do not have an KDE environment for testing.) Regards, Thomas On Tue, 2021-12-28 at 08:33 -0500, Ryan Armstrong wrote: > Package: needrestart > Version: 3.5-5 > Severity: normal > > Dear Maintainer, > > When I performed an update with KDE Discover, I noticed it stalled at > 99% complete status and would not finish. When I checked the process > tree with htop, I noticed the following lines from packagekitd and > needrestart: > > 2629 root 20 0 492M 124M 79624 S 0.0 0.8 0:29.20 ├─ > /usr/libexec/packagekitd > 2632 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.00 │ > ├─ /usr/libexec/packagekitd > 2634 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.05 │ > ├─ /usr/libexec/packagekitd > 14075 root 20 0 492M 124M 79624 S 0.0 0.8 0:05.78 │ > ├─ /usr/libexec/packagekitd > 14090 root 20 0 494M 99648 50800 S 0.0 0.6 0:00.24 │ > └─ /usr/libexec/packagekitd > 25864 root 20 0 494M 51924 2336 S 0.0 0.3 0:00.00 > │ └─ /usr/libexec/packagekitd > 25872 root 20 0 2472 704 616 S 0.0 0.0 0:00.00 > │ └─ sh -c test -x /usr/lib/needrestart/apt-pinvoke && > /usr/lib/needrestart/apt-pinvoke || true > 25873 root 20 0 35864 27816 6140 S 0.0 0.2 0:00.64 > │ └─ /usr/bin/perl /usr/sbin/needrestart > > It appears that packagekit is still running needrestart to ask if I > want to restart systemd services. However, this prompt is obviously > not > visible to me through KDE Discover, so it's stuck waiting forever. > > If I use kill on needrestart, the Discover session completes. > > Since, this is an interaction between Discover, packagekit, apt and > needrestart (possibly others?), I'm not 100% sure this is the right > place for it. Feel free to reassign if I got it wrong. > > Ryan > > -- Package-specific info: > needrestart output: > Your outdated processes: > akonadi_archive[3076], akonadi_mailfil[3102], akonadi_sendlat[3116], > akonadi_unified[3117], blueman-applet[2663], Discord[2921, 2924, > 2967, 2922, 2958, 2917, 3276, 3044], DiscoverNotifie[2571], > evolution-addre[2767], evolution-alarm[2660], evolution-calen[2742], > evolution-sourc[2698], goa-daemon[2704], kmail[2936], kwin_x11[2488], > nextcloud[2656], plasmashell[2554], QtWebEngineProc[6196, 6215, 6194, > 6193], tracker-miner-f[2674], xdg-desktop-por[2375], xdg-document- > po[2392], xdg-permission-[2397] > > > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (900, 'testing'), (300, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB:en_US > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages needrestart depends on: > ii binutils 2.37-7 > ii dpkg 1.21.1 > ii gettext-base 0.21-4 > ii libintl-perl 1.26-3 > ii libmodule-find-perl 0.15-1 > ii libmodule-scandeps-perl 1.31-1 > ii libproc-processtable-perl 0.634-1 > ii libsort-naturally-perl 1.03-2 > ii libterm-readkey-perl 2.38-1+b2 > ii perl 5.32.1-6 > ii xz-utils 5.2.5-2 > > Versions of packages needrestart recommends: > ii libpam-systemd 249.7-1 > > Versions of packages needrestart suggests: > ii iucode-tool 2.3.1-1 > ii libnotify-bin 0.7.9-3 > > -- no debconf information
Bug#1002732: needrestart stalled in background when performing update with KDE Discover
Package: needrestart Version: 3.5-5 Severity: normal Dear Maintainer, When I performed an update with KDE Discover, I noticed it stalled at 99% complete status and would not finish. When I checked the process tree with htop, I noticed the following lines from packagekitd and needrestart: 2629 root 20 0 492M 124M 79624 S 0.0 0.8 0:29.20 ├─ /usr/libexec/packagekitd 2632 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.00 │ ├─ /usr/libexec/packagekitd 2634 root 20 0 492M 124M 79624 S 0.0 0.8 0:00.05 │ ├─ /usr/libexec/packagekitd 14075 root 20 0 492M 124M 79624 S 0.0 0.8 0:05.78 │ ├─ /usr/libexec/packagekitd 14090 root 20 0 494M 99648 50800 S 0.0 0.6 0:00.24 │ └─ /usr/libexec/packagekitd 25864 root 20 0 494M 51924 2336 S 0.0 0.3 0:00.00 │ └─ /usr/libexec/packagekitd 25872 root 20 0 2472 704 616 S 0.0 0.0 0:00.00 │└─ sh -c test -x /usr/lib/needrestart/apt-pinvoke && /usr/lib/needrestart/apt-pinvoke || true 25873 root 20 0 35864 27816 6140 S 0.0 0.2 0:00.64 │ └─ /usr/bin/perl /usr/sbin/needrestart It appears that packagekit is still running needrestart to ask if I want to restart systemd services. However, this prompt is obviously not visible to me through KDE Discover, so it's stuck waiting forever. If I use kill on needrestart, the Discover session completes. Since, this is an interaction between Discover, packagekit, apt and needrestart (possibly others?), I'm not 100% sure this is the right place for it. Feel free to reassign if I got it wrong. Ryan -- Package-specific info: needrestart output: Your outdated processes: akonadi_archive[3076], akonadi_mailfil[3102], akonadi_sendlat[3116], akonadi_unified[3117], blueman-applet[2663], Discord[2921, 2924, 2967, 2922, 2958, 2917, 3276, 3044], DiscoverNotifie[2571], evolution-addre[2767], evolution-alarm[2660], evolution-calen[2742], evolution-sourc[2698], goa-daemon[2704], kmail[2936], kwin_x11[2488], nextcloud[2656], plasmashell[2554], QtWebEngineProc[6196, 6215, 6194, 6193], tracker-miner-f[2674], xdg-desktop-por[2375], xdg-document-po[2392], xdg-permission-[2397] -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages needrestart depends on: ii binutils 2.37-7 ii dpkg 1.21.1 ii gettext-base 0.21-4 ii libintl-perl 1.26-3 ii libmodule-find-perl0.15-1 ii libmodule-scandeps-perl1.31-1 ii libproc-processtable-perl 0.634-1 ii libsort-naturally-perl 1.03-2 ii libterm-readkey-perl 2.38-1+b2 ii perl 5.32.1-6 ii xz-utils 5.2.5-2 Versions of packages needrestart recommends: ii libpam-systemd 249.7-1 Versions of packages needrestart suggests: ii iucode-tool2.3.1-1 ii libnotify-bin 0.7.9-3 -- no debconf information
