Bug#729576: duplicate of bug #726763

[Andreas Cadhalpun]

reassign 736880 libpam-systemd 204-5
reassign 726763 libpam-systemd 204-5
reassign 731426 libpam-systemd 204-5
reassign 731602 libpam-systemd 204-5
reassign 735591 libpam-systemd 204-5
reassign 735593 libpam-systemd 204-5
reassign 735628 libpam-systemd 204-5
forcemerge 729576 736880 726763 731426 731602 735591 735593 735628
thanks

Hi,

On 05.05.2014 14:31, Vincent Lefevre wrote:
> On 2013-12-22 17:38:53 +0100, Vincent Lefevre wrote:
>> But perhaps #726763 is assigned to the wrong package...
>>
>> If #726763 occurs with GNOME and without lightdm, and is the same
>> problem as #729576, then this could confirm that it is a systemd
>> bug.
>
> Now I don't know the current status of #726763, but #729576 seems
> to have been fixed with systemd-shim automatic installation. So,
> retroactively, I suppose that this could have be regarded as a
> bug in libpam-systemd, fixed by the new dependency on
> systemd-sysv | systemd-shim (in libpam-systemd 204-9).

Indeed that fixes #726763 and all the other bugs due to missing 
systemd-sysv or systemd-shim, because gnome-settings-daemon depends on 
systemd and systemd recommends libpam-systemd.

> So, I'm reassigning the bug to libpam-systemd (204-5 was its version
> when I reported the bug). I'll close it in a second time, once the
> reassign has been done.

I'm now merging the other bugs with Bug #729576.

Best regards,
Andreas