Bug#791964: gdm3: upgrade causes X session to be terminated

[Michael Biebl]

Am 10.07.2015 um 18:38 schrieb Josh Triplett:
> On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
>> Control: severity -1 serious
>>
>> Am 09.07.2015 um 20:14 schrieb David Mohr:
>>> Package: gdm3
>>> Version: 3.14.2-1
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> the changelog reads:
>>>   * Systemd has been fixed in v222 to no longer kill services on reload
>>>     if BusName is set, so drop that part from 92_systemd_unit.patch.
>>> but that is EXACTLY what happened to me right now, in the middle of
>>
>> Right. Subsequent reloads of gdm3.service should no longer kill
>> gdm3.service though. So this was indeed fixed in v222 but there seems to
>> be a specific issue for the upgrade path.
>> Once gdm3 has been restarted, a reload no longer causes it to be killed.
> 
> Note, though, that it doesn't help for systemd to be upgraded first.
> Even if running the new systemd 222, upgrading gdm3 kills the active
> session.

Well, that's exactly what I said, right?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150710/8d2976a9/attachment-0002.sig>