Bug#902031: needrestart: Restarts login manager

2018-06-23 Thread Axel Beckert
Another thing which might restart (IIRC any) login manager:

It also tries to restart dbus.service by default which IIRC was
blacklisted in the past, too.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#902031: needrestart: Restarts login manager

2018-06-22 Thread Daniel Bayer
Control: retitle -1 needrestart: ignores configuration file

Hi!

On Thu, Jun 21, 2018 at 08:22:26PM +0200, Axel Beckert wrote:
> But for some reason "qr(^wdm)" doesn't seem to match wdm.service
> (anymore?) and it did by default restart wdm.service.
> 
> I don't think, the change from "q(^wdm)" to "qr(^wdm)" could have
> caused this, but I haven't found any other recent change.

I just had the same probem (with sddm). The reason is that the
configuration file is not correctly parsed anymore.

The bug is in commit dd7f10172a7f6163b906b23297898ac1ac164210. The
problem is that the last command in the block changed. So the return
value of <$fh> is ignored and hence the entire configuration, too.


Daniel



Bug#902031: needrestart: Restarts login manager

2018-06-21 Thread Axel Beckert
Control: retitle -1 needrestart: Restarts wdm by default since recently

Hi,

Axel Beckert wrote:
> since the recent needrestart update, needrestart started again to
> restart my X session by restarting the login manager (wdm in my case).
> 
> I suspect that this is related to the fact that it wanted to restart
> systemd-logind.service. (I haven't checked it yet, but will do after
> having written and sent this bug report.)

No, wasn't systemd-logind.service.

But for some reason "qr(^wdm)" doesn't seem to match wdm.service
(anymore?) and it did by default restart wdm.service.

I don't think, the change from "q(^wdm)" to "qr(^wdm)" could have
caused this, but I haven't found any other recent change.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#902031: needrestart: Restarts login manager

2018-06-21 Thread Axel Beckert
Package: needrestart
Version: 3.2-1
Severity: important

Hi,

since the recent needrestart update, needrestart started again to
restart my X session by restarting the login manager (wdm in my case).

I suspect that this is related to the fact that it wanted to restart
systemd-logind.service. (I haven't checked it yet, but will do after
having written and sent this bug report.)

-- Package-specific info:
needrestart output:
Your outdated processes:
chromium[24922], journalctl[5337], monkeysphere-va[4002], systemd[3927], 
telegram-deskto[31181]

checkrestart output:


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
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.30-21
ii  dpkg   1.19.0.5+b1
ii  gettext-base   0.19.8.1-6+b1
ii  libintl-perl   1.26-2
ii  libmodule-find-perl0.13-1
ii  libmodule-scandeps-perl1.24-1
ii  libproc-processtable-perl  0.55-1
ii  libsort-naturally-perl 1.03-2
ii  libterm-readkey-perl   2.37-1+b2
ii  perl   5.26.2-6
ii  xz-utils   5.2.2-1.3

Versions of packages needrestart recommends:
ii  libpam-systemd  238-5

Versions of packages needrestart suggests:
ii  iucode-tool  2.3.1-1
ii  libnotify-bin0.7.7-3
ii  needrestart-session  0.3-5

-- no debconf information