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

[Josh Triplett]

On Fri, Jul 10, 2015 at 06:46:18PM +0200, 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:
> >> 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?

You said "seems to be a specific issue for the upgrade path", and I
didn't know whether you meant the upgrade path for gdm3, systemd, or
both.  Just wanted to make sure.

- Josh Triplett