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

[David Mohr]

On 2015-07-10 10:46, Michael Biebl wrote:
> Am 10.07.2015 um 18:38 schrieb Josh Triplett:
>> On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
>>>>   * 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?

apt used this order on my system:

2015-07-09 12:05:33 status installed systemd:amd64 222-1
[...]
2015-07-09 12:05:46 status installed gdm3:amd64 3.14.2-1