Bug#823987: systemd: after upgrading some libs, login takes much longer until systemd-logind is restarted

[Christoph Anton Mitterer]

Control: forcemerge 770135 823987

On Wed, 2016-05-11 at 11:59 +0200, Michael Biebl wrote:
> My guess is, that it's the D-Bus restart and only indirectly related
> to
> the library upgrade.
mhh and the dbus restart is "suggested" because of the libgcc update...
I see..


> needrestart has a blacklist of services which should not be restarted
> and dbus should be on that list. Please check that.
I think it even is, I just didn't know that the dbus restart indirectly
"breaks" systemd (respectively the pam module).

Don't you think that it would be better if this could be solved
independently of needrestart (or similar tools)?
Cause one could also just manually restart dbus, and then the same
would probably happen, wouldn't it?

Perhaps something like dbus triggering a restart of systemd-logind?

Is that something we should carry upstream?


> Fwiw, you already filed
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770135 which seems
> to
> be exactly the same issue.
> Any reason you filed a new bug report or should we merge them?
No, I just totally forgot about it,... my apologies.


Thanks,
Chris.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5930 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160511/8eabd49b/attachment-0002.bin>