Bug#984789: needrestart: Microcode warnings without using Systemd

Control: tags -1 + upstream fixed-upstream Hi Patrik, On Mo, 2021-03-08 at 13:25 +0100, Patrik Schindler wrote: > libimvirt-perl would provide a convenient way to not depend on > systemd at all. I did not want it as a hard dependency. > Here, it's installed automatically, because I use apt-da

Bug#826044: Hangs in apt hook with a zombie - problem still exists in debian10

Hi, you are using some ansible deployment? Could you share your ansible role? This is a long-standing bug and it feels like that affected users are using aptitude. I wonder if this is related - could you give it a try (force_apt_get task parameter)? Regards, Thomas On Tue, 2022-05-10 at 18:00

Bug#1002591: misdetects socket activated ssh

Hi Marc, On Sat, 2022-01-01 at 20:55 +0100, Marc Haber wrote: > Sure: > 1 [1/4996]mh@torres:~ $ pgrep ssh > 315675 > 315738 > [2/4997]mh@torres:~ $ sudo cat /proc/315675/cgroup > [sudo] password for mh on torres: > 0::/user.slice/user-1001.slice/session-296.scope > [3/4998]mh@torres:~ $ sudo cat

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

Bug#1002591: misdetects socket activated ssh

Hi Marc, could you please provide the content of /proc/$PID/cgroup for an socket activated sshd instance? As a workaround you might blacklist sshd in needrestart but I think a generic approach handling socket activation services in needrestart would be better. Therefore needrestart need a way to

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, Thoma

Bug#995274: needrestart: false positive: rabbitmq-server

tags 995274 upstream fixed-upstream thanks Hi, thanks for the verbose output. This is due to anonymous file mapping /memfd (see also #988461). Has been already fixed upstream in needrestart 3.6+ [1]. [1] https://github.com/liske/needrestart/commit/6c87772bdc38091e9efbf4c59217fa502365dcf2#diff-5

Bug#986507: use grep -a instead of strings(1) (fix check-support-status)

tags 986507 upstream fixed-upstream thanks Hi, thanks for the hint. I've applied a slitly modified patch upstream to replace binutils's strings by grep in needrestart 3.6+. Replacing the bintuils dependency by GNU grep lowers the total installation size by an order of magnitude. Regards, Thom

Bug#994407: Binaries with same name

Hi, @Patrick this looks like a regression of #752114, doesn't it? Regards, Thomas On Wed, 2021-09-15 at 18:22 +0200, ThePPK wrote: > Package: needrestart > Version: 3.5-4 > > Needrestart while run once of scripts on > /etc/needrestart/hook.d/30-pacman, execute pacman binary (which is > Arch

Bug#988461: needrestart: False positive for sddm

tags 988461 upstream fixed-upstream thanks Hi, thanks for reporting. I've updated the default configuration upstream to ignore the all memfd mappings. The bugfix will be part of needrestart 3.6+. Regards, Thomas On Thu, 2021-05-13 at 14:44 +0200, Michail Bachmann wrote: > Package: needrestar

Bug#995274: needrestart: false positive: rabbitmq-server

Hi, could you please provide the output of `needrestart -lv`? TIA, Thomas On Tue, 2021-09-28 at 20:34 -0300, Antonio Terceiro wrote: > Package: needrestart > Version: 3.5-4 > Severity: normal > > Dear Maintainer, > > Recently every time I install something, needrestart seems to think > that

Bug#973050: needrestart: Use of uninitialized value in hex at /usr/share/perl5/NeedRestart/uCode/AMD.pm line 169

Hi, could you please provide the output of `needrestart -vw`? TIA & Regards, Thomas On 27.10.20 10:44, Martin-Éric Racine wrote: > Package: needrestart > Version: 3.5-1 > Severity: normal > Scanning processes... Use of uninitialized value in hex at /usr/share/perl5/NeedRestart/uCode/AMD.pm

Bug#972685: needrestart: Please add support for runit

Hi Lorenzo, thanks for the updated patch. I've applied it upstream and will be part of needrestart 3.6+. Regards, Thomas On 23.10.20 12:12, Lorenzo Puliti wrote: Package: needrestart Version: 3.5-1 Followup-For: Bug #972685 On 10/22/20 8:16 PM, Thomas Liske wrote: Hi, thanks fo

Bug#972685: needrestart: Please add support for runit

Hi, thanks for the patch. Would it possible that you provide a updated patch compatible with upstream's git HEAD? Regards, Thomas (Upstream) On 22.10.20 16:55, Lorenzo Puliti wrote: Package: needrestart Version: 3.5-1 Severity: normal Tags: patch Dear maintainer, Please consider the att

Bug#907372: needrestart: complains about microcode updates on systems with microcode for multiple CPUs in initramfs

HTH, Thomas Paul Wise writes: > On Sun, 2018-10-28 at 19:57 +0100, Thomas Liske wrote: > >> ... please provide the output of the following commands: >> >> cat /sys/devices/system/cpu/cpu0/microcode/version >> sh -x /usr/lib/needrestart/iucode-scan-versions > >

Bug#907372: needrestart: complains about microcode updates on systems with microcode for multiple CPUs in initramfs

tags 907372 upstream thanks Hi Paul, Paul Wise writes: > Package: needrestart > Version: 3.3-1 > Severity: normal > File: /usr/lib/needrestart/iucode-scan-versions > > I have a system that changes between two different CPUs occasionally. > I have a system that boots a different computer at a

Bug#903119: needrestart lists both gdm and gdm3

tags 903119 upstream moreinfo thanks Hi Laurent, Laurent Bigonville writes: > Package: needrestart > Version: 3.3-1 > Severity: normal > > Hi, > > needrestart lists both gdm and gdm3 when proposing the services to > restart > > gdm3.service is a symlink to gdm.service to mask the gdm3 initsc

Bug#906958: needrestart: Complains when the microcode is newer than what Debian has

tags 906958 upstream fixed-upstream thanks Hi Maik, Maik Zumstrull writes: > Package: needrestart > Version: 3.3-1 > > On this box, needrestart gives this message: > > The currently running processor microcode revision is 0x20 which is > not the expected microcode revision 0x1f. > > Unless

Bug#893152: needrestart: leaks a file descriptor into restarted services

tags 893152 upstream fixed-upstream thanks Hi Stephen, I've added a workaround to close the orphan FD to Debconf.pm. The fix will be part of needrestart 3.2. HTH, Thomas -- :: WWW:https://fiasko-nw.net/~thomas/ :: ::: Jabber: xmpp:tho...@

Bug#893152: needrestart: leaks a file descriptor into restarted services

Hi Stephen, Stephen Rothwell writes: > Services restarted by needrestart have a unexpected file descriptor > open (on /usr/share/perl5/NeedRestart/UI/Debconf.pm). Manually > restarting the service gets rid of it. > > For example: lvcreate when used from a cron job after cron has been > restar

Bug#900298: needrestart: Needrestart false positive detect need to reboot due to microcode update

tags 900298 fixed-upstream thanks Hi, Francois Mescam writes: > Le Wed, May 30, 2018 à 05:37:15PM +0800, Thomas Liske a écrit >> >> >> Could you give upstream's most recent iucode-scan-versions[2] >> scripts a try? It should report a single ucode revis

Bug#900298: needrestart: Needrestart false positive detect need to reboot due to microcode update

tags 900298 upstream thanks Hi, this might be related to issue #112[1]. While scanning for ucode updates using the iucode_tool for the running system it does report updates which are *not* applicable. This might be a bug or a inaccuracy description of the --scan--system option of iucode_tool.

Bug#894444: needrestart doesn't restart services anymore

Hi, Jean-Michel Vourgère writes: > Package: needrestart > Version: 2.11-3+deb9u1 > Severity: normal > > Dear Maintainer, > > Here, needrestart recently stopped working automatically in stable. This is triggered by the bugfix for Debian Bug#876459 and is intentional (upstream's point of view).

Bug#892113: needrestart: Bug in GTK3-frontend

Hi Andreas, Andreas Schmidt writes: > Package: needrestart > Version: 3.0-1 > Severity: normal > > Dear Maintainer, > > the new GTK-3 frontend to needrestart has two buttons: and > . needrestart does not have a graphical frontend at all ;-). I think you are using the debconf frontend which m

Bug#891923: needrestart: Use of uninitialized value $ucode_vars

tag 891923 upstream fixed-upstream thanks Hi Bob, thanks for the report. The bug has been fixed upstream. HTH, Thomas Bob Proulx writes: > Package: needrestart > Version: 3.0-1 > Severity: normal > > On some systems I see the following: > > root@clash:~# needrestart -b > NEEDRESTART-V

Bug#859387: Info received (Upload 2.12 to stretch-backports?)

Hi, Francis M writes: > s/2.12/2.11+git20180213-1/ it has been released[1] upstream as needrestart 3.0. [1] https://github.com/liske/needrestart/releases/tag/v3.0 > Apologies for the noise, I made the mistake of typing my previous > e-mail before my morning coffee. :-) > I've tested the

Bug#887828: needrestart: Possible false positive on postifx and wazuh-agent running in LXC container

Hi, Chris writes: > Yes, it seems most processes of postfix are chrooted by default in > Debian Stretch (plain install of Postfix via apt-get install postfix): I did install a vanilla Debian Stretch VM, setup an LXC container inside (using Stretch again) and installed postfix inside the conta

Bug#887828: needrestart: Possible false positive on postifx and wazuh-agent running in LXC container

Hi, Chris writes: > [main] #338 uses non-existing /var/ossec/bin/ossec-agentd > [main] #338 is not a child this is by design of the wazuh-agent and might trigger a false positive in needrestart - putting binaries into /var looks something special. > [main] #25460 uses non-existing /usr/lib/p

Bug#856260: needrestart: always says newer kfreebsd kernel available

Hi Bill, this report is about kfreebsd kernel - you are using a linux kernel. Needrestart's warning on pending kernel updates seems to be correct: - running kernel is 4.9.0-4-686-pae build on 2017-09-28 - installed kernel is 4.9.0-4-686-pae build on 2017-12-03 HTH, Thomas Bill Brelsford wri

Bug#886402: needrestart: Shows perl errors (uninitialized value)

tags 886402 upstream fixed-upstream thanks Hi, the perl warnings have been already fixed upstream[1]. [1] https://github.com/liske/needrestart/commit/7ab8834b154f7813b0528424d149e0a0aa3f5b88 HTH, Thomas cre writes: > Package: needrestart > Version: 2.11-4 > Severity: normal > > Dear Mai

Bug#887828: needrestart: Possible false positive on postifx and wazuh-agent running in LXC container

tags 887828 upstream thanks Hi, you are running needrestart outside of the container? For some reason needrestart seems to not detect that the services are belonging to a LXC container. And the postfix service name looks suspicious. Could you please provide the content of /proc/$PID/cgroup of t

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

Henrique de Moraes Holschuh writes: > On Sat, 13 Jan 2018, Thomas Liske wrote: >> # iucode_tool -Sl /lib/firmware/intel-ucode/ > > It would have to be: > > iucode_tool -Sl /lib/firmware/intel-ucode /usr/share/misc/intel-microcode* > > and that could still miss some

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

Hi, Paul Wise writes: > On Sat, 2018-01-13 at 14:20 +0100, Thomas Liske wrote: > >> during adding the feature in needrestart I've looked more closely at the >> uicode-tool stuff. I don't think we need to examine the initrd since >> the following comman

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

mpare the current running microcode signature with the latest available one. This would also handle outdated initrd images gracefuly. Regards, Thomas Thomas Liske writes: > tags 886445 upstream > thanks > > > Hi Paul, > > thanks for summarising your findings. I'm

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

stem/cpu/cpu1/microcode/version <== > 0x5 > > ==> /sys/devices/system/cpu/cpu2/microcode/version <== > 0x5 > > ==> /sys/devices/system/cpu/cpu3/microcode/version <== > 0x5 > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise --

Bug#886611: needrestart: detect need to reboot due to AMD microcode updates

tags 886611 upstream thanks Hi Paul, checking if initramfs is newer than uptime might be a good idea in general. A reboot may be also required due to updates of 3rd party kernel modules (like DKMS) if they are part of the initramfs. I would avoid to parse the initramfs in needrestart (would nee

Bug#885448: needrestart manual: typo: (a)dvaned -> (a)dvanced

tags 885448 upstream fixed-upstream thanks Hi Paul, I've patched the typo upstream. Thanks, Thomas Paul Wise writes: > Package: needrestart > Version: 2.11-4 > Severity: minor > File: /usr/share/man/man1/needrestart.1.gz > > There is a typo in the manual page, this line: > > a

Bug#866105: needrestart: please have a mechanism to invoke needrestart from apt with -r a

tags 866105 upstream fixed-upstream thanks Re, Marc Haber writes: > On Fri, Nov 03, 2017 at 11:14:53AM +0100, Thomas Liske wrote: >> Marc Haber writes: >> >> > I didn't find any possibility in needrestart.conf to set the equivalent >> > of the -r opti

Bug#866105: needrestart: please have a mechanism to invoke needrestart from apt with -r a

Re, Marc Haber writes: > I didn't find any possibility in needrestart.conf to set the equivalent > of the -r option. Maybe that's a documentation issue? indeed there is the $nrconf{restart} config option. It might be confusing since the word 'mode' is *not* used the configuration comment. >

Bug#866105: needrestart: please have a mechanism to invoke needrestart from apt with -r a

Hi Marc, Marc Haber writes: > Package: needrestart > Version: 2.11-3 > Severity: wishlist > > Dear Maintainer, > > during automated processes, such as puppet runs or automated upgrades, > it is sometimes acceptable to restart daemons without asking. In this > case, I would like to have my syst

Bug#842512: explain how this integrates with various unattended-upgrade solutions

tags 842512 upstream fixed-upstream thanks Hi Antoine, Antoine Beaupré writes: > It is unclear to me whether installing this package alongside a > properly configured "unattended-upgrade" package will do the right > thing (that is, automatically restart services). it depends, I do not think

Bug#864347: needrestart: Multiple "Use of uninitialized value" error messages

tags 864347 upstream fixed-upstream thanks Hi Vincas, Vincas Dargis writes: > I've noticed that running needrestart produces these "uninitialized > value" messages: [snip] > I am not sure how (if) serious is this, I do get list of applications > that need to be restarted occasionaly after

Bug#878700: needrestart: False positive with AppImage

tags 878700 fixed-upstream - moreinfo thanks Hi Richard, thanks for the detailed update. The problem was a bug in needrestart due to the inspection of a non-existing mapping in /tmp (so you also got that many "Use of uninitialized value" warnings). The patch for the original github issue #58[1

Bug#857730: Need to support DPKG_ROOT

tags 857730 upstream severity 857730 wishlist thanks Hi Bastien, Bastien ROUCARIES writes: >>> severity: important >> >> Using severity important for anything DPKG_ROOT related sounds dubious >> to me, because the feature is not finalized in dpkg, but a technology >> preview. Please do not

Bug#876459: needrestart: Non-interactive mode not being detected properly

tags 876459 fixed-upstream notfixed 803249 needrestart/2.6-1 thanks Hi Piotr, the fix of Debian Bug#803249 was broken. I've applied your patch upstream, this fixes #803249 and #876459. Thanks! Regards, Thomas Piotr Pańczyk writes: > Package: needrestart > Version: 2.11-3 > Severity: impor

Bug#859387: NeedRestart::UI assumes STDOUT is a terminal

Re, Guillaume writes: > Would the fix make it into the upcoming 2.12 release ? > > I just want to know which version to watch for, no hurry. yes, it will be part of 2.12 as any other fixes and changes being merged before releasing it. There are still a few issues left for fixing before I'm goin

Bug#878700: needrestart: False positive with AppImage

tags 878700 upstream moreinfo thanks Hi Richard, Richard Hector writes: > It appears that AppImage packages mount their filesystem under /tmp/, > and needrestart may find that there are open binaries or libraries there > but be unable to find them. Sorry, I'm not sure how to word this ... yes,

Bug#859387: NeedRestart::UI assumes STDOUT is a terminal

tags 859387 upstream fixed-upstream forwarded 859387 https://github.com/liske/needrestart/issues/86 thanks Hi, I've adopted the PR and GetTerminalSize() should be no more called on a non-TTY STDOUT. Thanks for the report and the PR. Regards, Thomas Guillaume writes: > Hi, > > This also a

Bug#876452: needrestart: Unnamed block devices (like for OpenVZ's simfs) not being detected properly

tags 876452 fixed-upstream thanks Hi Piotr, I've applied your patch upstream. The fix will be part of needrestart 2.12. Thanks & regards, Thomas Piotr Pańczyk writes: > Package: needrestart > Version: 2.11-3 > Severity: important > Tags: patch upstream > > Dear Maintainer, > needrestart do

Bug#856260: needrestart: always says newer kfreebsd kernel available

tags 856260 upstream moreinfo thanks Hi Michael, Michael Gilbert writes: > Needrestart's apt hook on kfreebsd always says that a newer kernel is > available even though the kfreebsd kernel package has not changed. could you please provide the output of `needrestart -k -v`? Thanks, Thomas

Bug#879091: needrestart: false positive with recent evolution/gnome-shell: /tmp/#8929645

tag 879091 upstream fixed-upstream thanks Hi Paul, Paul Wise writes: > There seems to be a false positive with evolution 3.26.1-1 and > gnome-shell 3.22.3-3 and temporary files like /tmp/#8929645: it seems to be related to github issue #84 (although this was related to plasmashell). You migh

Bug#855788: 855788 severity

Hi Paul, could you please verify if there is a user named "needrestart-dbus"? The package seems no creating the required user. Maybe this report is a duplicate of #857077. TIA, Thomas Paul Wise writes: > On Sun, 2017-03-05 at 23:24 +0100, Thomas Liske wrote: > >&

Bug#857077: needrestart-session: Unknown username "needrestart-dbus" in message bus configuration file

severity 857077 important thanks Hi Laurent, you are right, there seems to be no configure script with-in the .deb to add the needrestart-dbus user if it does not exist. @Patrick: It seems that no user 'needrestart-dbus' was or is created by the package's configure script. This breaks any Xse

Bug#855788: 855788 severity

tags 855788 more-info upstream thanks Hi pabs, Paul Wise writes: > On Thu, 2017-03-02 at 23:30 +0100, Yann Dirson wrote: > >> FWIW, no such problem here. Is that high severity really warranted ? > > The package is not working for me at all. I assumed that the reason the package's core funct

Bug#851866: wants to restart systemd-manager.service

Hi, Sven Hartge writes: > Instead of doing "systemctl daemon-restart" needrestart tries to restart > systemd-manager.service, which is of course unknown: there was a change in needrestart 2.11 putting the special treatment required to restart certain daemons into external scripts. Sadly the Ma

Bug#838360: needrestart: Wants to restart services, even if these were restarted already

Re, "ge...@riseup.net" writes: > (I'm subscribed to the bug, not need to mail me directly.) > > Hi Patrick, > > Thanks for your response: > > On 17-01-14 23:31:13, Thomas Liske wrote: >> the repeating restart of ssh.service might be triggered by one or

Bug#850108: needrestart: support python3

close 850108 thanks Re, Paul Wise writes: > On Fri, 2017-01-13 at 22:38 +0100, Thomas Liske wrote: > >> this regex does match on /usr/bin/python3 since there is no >> end of string metacharacter ($). So it should not require any change in >> needrestart, should

Bug#850948: needrestart: Hangs in apt hook with a zombie

Re, Jonas Smedegaard writes: >> I think the severity of this bug should be lowered to important since >> there is no policy violation of needrestart at all. > > I think it is quite worrisome if simply installing (not actively using) > needrestart inside a chroot spawns daemons - and that is n

Bug#838360: needrestart: Wants to restart services, even if these were restarted already

tags 838360 upstream fixed-upstream thanks Hi Georg, "ge...@riseup.net" writes: > Hi Patrick, > > On 16-09-20 12:12:50, ge...@riseup.net wrote: >> needrestart wants to restart {ganeti,ssh}.service, even if these were >> restarted already: the repeating restart of ssh.service might be triggere

Bug#850948: needrestart: Hangs in apt hook with a zombie

Re, I've replied to #850948 where I think you wan't to discuss the piuparts-needrestart-* issue. Jonas Smedegaard writes: >> Maybe it is just a debconf frontend issue? In cases needrestart does >> seems to hang it trackes down to: >> >> - daemons hangig while restarting them (init scripts)

Bug#826044: needrestart: Hangs in apt hook with a zombie

unblock 850948 with 826044 unmerge 826044 severity 826044 important thanks Hi, Jonas Smedegaard writes: > Hi, > > It seems I have another instance of this issue: piuparts hangs (as I piuparts does not use consolation, doesn't it? Please stop abusing this issue focusing on needrestart vs. con

Bug#850108: needrestart: support python3

Hi Paul, Paul Wise writes: > Package: needrestart > Version: 2.10-1 > Severity: important > > The Python interpreter support doesn't appear to check python3 processes: > > /usr/share/perl5/NeedRestart/Interp/Python.pm:return 1 if($bin =~ > m@/usr/(local/)?bin/python@); this regex does ma

Bug#843832: needrestart: detect need for a systemctl daemon-reload

tags 843832 wontfix thanks Hi Paul, needrestart tries to detect which daemons (read: processes in the broadest sense) should be restarted due to upgraded libraries (read: code to be somehow *executed*). Configuration files etc. are beyond the scope of needrestart (maybe there should be a mechan

Bug#845996: needrestart: Restarts lxdm by default

tags 845996 upstream fixed-upstream severity 845996 minor thanks Hi Rodrigo, Rodrigo Campos writes: > I'm using lxdm display manager and needrestart tries to restart it by default, > instead of being disabled by default as it is with others DM. I've added an override to the default configurat

Bug#844283: needrestart: uses wrong quote function for regexps in default configuration file

severity 844283 normal tags 844283 upstream fixed-upstream thanks Hi Paul, thanks for the hint. Interestingly it seems that q() is somehow working - at least if there is no EOL marker '$' in use (see also the attachment). So the broken default config was there since the beginning but it was no

Bug#827339: Please revert patch for cmd, and fix default pattern

Hi, this is a negative lookbehind assertion - quoting from perlre(1): "(? writes: > Am 30.10.2016 um 12:31 schrieb Stephan Sürken: >> Hi Evgeni, Patrick, >> >> fwiw (probably this is already worked on), i have fixed up my system by >> >> * reverting 01-grep-syntax-error.diff >> >> Th

Bug#838622: needrestart: systemctl combine, stdio, list mode: do not wrap systemctl restart commands

ckages. > > Versions of packages needrestart suggests: > ii  libnotify-bin0.7.6-2 > ii  needrestart-session  0.3-2 > > -- no debconf information > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise -- supp...@ibh.de T

Bug#838355: needrestart: Automatic restart mode doesn't work

her, please > let me know. > > Thanks in advance and for your work! > All the best, > Georg -- supp...@ibh.de Tel. +49 351 477 77 30 www.ibh.de Fax +49 351 477 77 39 -

Bug#837147: needrestart batchmode shows different result than interactive mode

Hi Andreas, sadly, the documentation in ADP 0.7 does not expose the meaning of NEEDRESTART-KSTA values. Since ADP was developed for apt-dater the meaning of NEEDRESTART-STA can be lookuped in apt-dater's sources[1]: #define ADP_STATUS_NRK_UNKNOWN 0 #define ADP_STATUS_NRK_NOUPGR

Bug#827023: needrestart - please ignore services in override_rc in nagios plugin mode

Bastian Blank writes: tags 827023 upstream,wontfix,fixed-upstream thanks Hi Bastian, > Currently needrestart returns CRITICAL if any service needs restart, > even if they are included in override_rc. The following example just > have the already listed dbus. > Please reduce the severity to W

Bug#826044: needrestart: Hangs in apt hook with a zombie

tags 826044 unreproducible thanks Hi Axel, Axel Beckert writes: > So it's actually debconf which fails to end needrestart cleanly as it > did in my initial bug report. > > stracing debconf/frontend shows that it seems to wait for input on > file descriptor 9: > > # strace -p 26405 > strace: P

Bug#826247: needrestart: Improve performance when checking interpreters by not running multiple times for the same script

tags 826247 upstream,fixed-upstream thanks Hi Wolfang, Wolfgang Karall-Ahlborn writes: > on a system with a perl-based daemon spawned by postfix many many times, > needrestart was very slow. > > That's because it re-scans all the perl module source files over and > over again, for each PID onc

Bug#827162: needrestart: reports unchanged backport kernel as changed

tags 827162 upstream,fixed-upstream found 827162 needrestart/2.8-1 thanks Re, Martin Steigerwald writes: >> Could you please provide the output of `needrestart -v -r l`? It would >> be sufficient to provide the kernel related lines ('^[Kernel]' until >> the kernel status message). > > Includin

Bug#826527: needrestart: override_rc option does not work

tags 826527 upstream,fixed-upstream merge 826526 826527 thanks Hi Paul, this issue is related to #826527 and is triggered only running in list mode (due to the wrong usage of perl's 'local' function). So it should be fixed in [master d82fff9], too. HTH, Thomas Paul Wise writes: > [ Unknow

Bug#826526: needrestart: systemctl_combine option does not work

tags 826526 upstream,fixed-upstream thanks Hi Paul, Paul Wise writes: > [ Unknown signature status ] > Package: needrestart > Version: 2.8-1 > Severity: normal > > The systemctl_combine option does not appear to work: > > root@chianamo ~ # grep -r systemctl_combine /etc/needrestart/ > /etc/nee

Bug#813079: chromium.desktop: StartupWMClass does not match actual WM_CLASS

found 813079 52.0.2743.116-2 affects 813079 docky thanks Hi, it seems that the StartWMClass option has been already changed: $ dpkg-query -W chromium chromium52.0.2743.116-2 $ grep WMClass /usr/share/applications/chromium.desktop StartupWMClass=chromium-browser Sadly, the WM_C

Bug#833111: otrs2: use init system for starting otrs.Daemon.pl / needrestart

Hi, On Fri, Aug 12, 2016 at 04:23:08PM +0200, Patrick Matthäi wrote: > > Am 01.08.2016 um 02:48 schrieb Sven Strickroth: > > Package: otrs2 > > Version: 5.0.10-1~bpo8+1 > > Severity: minor > > > > Dear Maintainer, > > > > right now the OTRS daemon (otrs.Daemon.pl) is started using cron. This lead

Bug#828103: needrestart: false positive: pulseaudio: orcexec files in /run

tags 828103 upstream fixed-upstream thanks Hi Paul, On Sat, Jun 25, 2016 at 07:36:22AM +0200, Paul Wise wrote: > There is a false positive with pulseaudio and files in /run: > > needrestart output: > # needrestart -v > ... > [main] #1976 uses deleted /run/user/1000/orcexec.nXwDNz although ther

Bug#826220: needrestart: Allow usage of different config file when run from APT

tags 826220 upstream fixed-upstream thanks Hi Wolfgang, On Fri, Jun 03, 2016 at 02:12:17PM +0200, Wolfgang Karall-Ahlborn wrote: > It would be nice to be able to set a different config for APT, so the > interactive call of needrestart is could be plain 'needrestart' again. I've changed call of n

Bug#832166: please don't restart lxcfs by default

tags 832166 fixed-upstream thanks Hi, On Sat, Jul 23, 2016 at 08:33:36AM +0200, Evgeni Golov wrote: > needrestart currently will try to restart lxcfs if that got upgraded, however > restarting it would result in all containers using it hanging, so please > don't :) I've added an override for

Bug#831840: needrestart: false positive: restart due to grsec Linux kernel variant installed

severity 831840 minor tags 831840 wontfix upstream thanks Hi Paul, On Wed, Jul 20, 2016 at 12:52:16PM +0800, Paul Wise wrote: > I have linux-image-4.6.0-1-amd64 and linux-image-4.6.0-1-grsec-amd64 > installed and am running linux-image-4.6.0-1-amd64 because various > services fail under linux-ima

Bug#827162: needrestart: reports unchanged backport kernel as changed

Hi, On Mon, Jun 13, 2016 at 09:43:26AM +0200, Martin Steigerwald wrote: > Means it thinks the kernel has changed, while it has not. I know for sure > I booted exactly this kernel. It seems to be confused detecting the end of > the version number in the second case as it appears that it uses the wh

Bug#811417: apt-dater reports an error for servers with multi-line issue.net

severity 811417 normal tags 811417 wontfix thanks Re, On Sun, Jun 12, 2016 at 11:13:38PM +0200, Alexander Schier wrote: > Am 12.06.2016 um 21:30 schrieb Thomas Liske: > > > Does your issue.net contain the words 'error', 'warning' or 'failed' > >

Bug#811417: apt-dater reports an error for servers with multi-line issue.net

ssue.net" clearly triggers / removes the problem here. I'm unable to reproduce it. I think the false positive is triggered by the content of your issue.net. HTH, Thomas -- supp...@ibh.de Tel. +49 351 477 77 30 www.ibh.de

Bug#827107: uses obsolete tmux option "status-utf8"

r/hosts.xml [Errno 13] Permission denied: > u'/etc/apt-dater/hosts.xml' > > -- no debconf information > -- supp...@ibh.de Tel. +49 351 477 77 30 www.ibh.de Fax +49 351 477 77 39 --

Bug#812871: apt-dater: Some configured hosts are not displayed until any host is refreshed

> -- Configuration Files: > /etc/apt-dater/apt-dater.xml [Errno 13] Permission denied: > u'/etc/apt-dater/apt-dater.xml' > /etc/apt-dater/hosts.xml [Errno 13] Permission denied: > u'/etc/apt-dater/hosts.xml' > > -- no debconf information > -

Bug#811417: apt-dater reports an error for servers with multi-line issue.net

tags 811417 moreinfo upstream thanks Hi, On Mon, Jan 18, 2016 at 07:47:59PM +0100, Alexander Schier wrote: > Package: apt-dater > Version: apt-dater reports an error for servers with multi-line > issue.net which version of apt-dater did you use? > Severity: important > > Dear Maintainer, > ap

Bug#813103: apt-dater: Typo in the german translation

Init: sysvinit (via /sbin/init) > -- supp...@ibh.de Tel. +49 351 477 77 30 www.ibh.de Fax +49 351 477 77 39 --- Dipl.-Ing. Thomas Liske Teamleiter DataCenter Services IBH IT-Service

Bug#826044: needrestart: Hangs in apt hook with a zombie

Hi Axel, could you please provide your needrestart config (if changed from defaults)? Is the problem reproducable? Could you attach strace to needrestart while it hangs? TIA & HTH, Thomas On Wed, Jun 01, 2016 at 10:20:58PM +0200, Axel Beckert wrote: > Package: needrestart > Version: 2.8-1 > Sev

Bug#795787: needrestart-session doesn't work when installing a package via dpkg

tags 795787 upstream wontfix severity 795787 wishlist reassign 795787 needrestart thanks Hi, On Sun, Aug 16, 2015 at 10:14:50PM +0200, Christoph Anton Mitterer wrote: > On Mon, 2015-08-17 at 01:24 +0530, shirish शिरीष wrote: > > When a package is installed via dpkg, needrestart-session stays > >

Bug#787292: needrestart-session: running needrestart-session with arguments makes it "silent"

tags 787292 upstream severity 787292 minor thanks Hi Chris, On Sun, May 31, 2015 at 06:52:35AM +0200, Christoph Anton Mitterer wrote: > When needrestart-session is run (as user) with an argument, e.g. > $ needrestart-session foo > it doesn't seem to do anything (not even the "nothing found" popup

Bug#824564: libterm-readkey-perl: supply a filehandle parameter on GetTerminalSize don't work work

Package: libterm-readkey-perl Version: 2.32-1+b1 Severity: normal Tags: patch, upstream Hi, there seems to be a bug in GetTerminalSize using the optional filehandle parameter. The man page reads: GetTerminalSize [Filehandle] But the implementation ignores the first parameter and expects the

Bug#819824: easy mode for needrestart

tags 819824 fixed-upstream thanks Hi, the easy mode is now using debconf for user notification and is part of the needrestart 2.8 release. HTH, Thomas On Sun, May 08, 2016 at 12:34:08PM +0200, Thomas Liske wrote: > Hi Patrick, > > I've added a first implementation

Bug#824184: needrestart: bashism in /etc/needrestart/notify.d/600-mail prevents disabling of sending mails

severity 824184 minor tags 824184 upstream fixed-upstream merge 824184 818001 thanks Hi Axel, On Fri, May 13, 2016 at 03:21:11PM +0200, Axel Beckert wrote: > there is a bashism in /etc/needrestart/notify.d/600-mail (which has a > "#!/bin/sh" shebang line): upstream has been already fixed but a

Bug#819824: easy mode for needrestart

iske/needrestart/master/needrestart). HTH & TIA, Thomas On Sun, Apr 24, 2016 at 02:08:51PM +0200, Thomas Liske wrote: > tags 819824 upstream > thanks > > > Hi Patrick, > > On Sat, Apr 02, 2016 at 07:18:39PM +, Patrick Schleizer wrote: > > we are wondering if n

Bug#818853: needrestart: systemd restart output

tags 818853 upstream fixed-upstream thanks Hi, On Mon, Mar 21, 2016 at 10:31:38AM +0800, Paul Wise wrote: > Package: needrestart > Version: 2.7-1 > Severity: wishlist > > The needrestart output used to put systemctl restart commands all on > one line, it would be nice to have that back and on s

Bug#819824: easy mode for needrestart

tags 819824 upstream thanks Hi Patrick, On Sat, Apr 02, 2016 at 07:18:39PM +, Patrick Schleizer wrote: > we are wondering if needrestart should be installed by default in Whonix. > > When needrestart is automatically run during apt-get dist-upgrade, > I am concerned, that its output by defa

Bug#817927: needrestart emits a lot of "Unknown option:" warnings (python buildbot)

tags 817927 fixed-upstream thanks Hi Francois, needrestart uses the default Getopt::Std implementation shipped by perl-modules - but python implements a custom getopts parser and handles '-c' in the special way you've already described. I dislike reimplementing the python approach again, but ot

Bug#817807: needrestart: shouldn't restart xendomains by default

severity 817807 minor tags 817807 + upstream fixed-upstream thanks Hi, On Thu, Mar 10, 2016 at 03:42:20PM +0100, Samuel Thibault wrote: > Sometimes needrestart proposes to restart the xendomains service, and > that choice is enabled by default. This is not a good idea, since > restarting the xen

Bug#818001: More bashisms

severity 818001 minor tags 818001 + upstream fixed-upstream thanks Hi, this issue has been fixed upstream. HTH & thanks, Thomas -- :: WWW:https://fiasko-nw.net/~thomas/ :: ::: Jabber: xmpp:tho...@jabber.fiasko-nw.net ::: :: flickr:

  1   2   3   4   >