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.
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
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
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
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,
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:
6 matches
Mail list logo
