needrestart icon indicating copy to clipboard operation
needrestart copied to clipboard

Restart daemons after library updates.

Results 77 needrestart issues
Sort by recently updated
recently updated
newest added

With new enough kernel/plasmashell/KDE/Qt needrestart reports false-positives on memfd files used by Qt applications: ``` # needrestart Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Running kernel seems...

After updating or installing other packages with `apt-get install package` or `apt-get upgrade` needsrestart displays e.g.: ``` Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Running kernel seems...

bug
moreinfo

Arch Linux gives users the choice to install multiple kernels to their systems. E.g. I have currently `linux-mainline` and `linux-next` installed. However, if I update `linux-next`, `needrestart` warns me that...

wishlist

Whenever I run needrestart (version 3.6) on my machine with an AMD processor, I get the message `Failed to check for processor microcode upgrades.` `sudo needrestart -v -w` output: ```...

bug

I'm using needrestart in batch mode in a script which runs in user space. It returns an indication that a restart is needed, but when run as root, it does...

moreinfo

needrestart always ignores updated libraries in LXC/LXD instances. It seems that it is regression of #233. ## Environment * Ubuntu 22.04 LTS * needrestart 3.5 (package version 3.5-5ubuntu2.1, backported many...

bug

Without modifying needrestart's notify configuration, needrestart is really annoying. I installed needrestart because when I update / install packages manually, it then asks me in the terminal which services would...

wishlist

Unattended-upgrades service does very little that can be affected by a library update, and it's main purpose is delaying shutdown to ensure that package upgrades are not interrupted in the...

moreinfo
wishlist

After upgraded the `libgcc` package, using `fuser` showed that `systemd` (PID 1) wasn't using the new shared library, and `fuser` only changed to showing it using the new library after...

bug
moreinfo