Bug#791964: gdm3: upgrade causes X session to be terminated
Control: severity -1 important Am 24.07.2015 um 14:22 schrieb Michael Biebl: > On Fri, 10 Jul 2015 09:38:56 -0700 Josh Triplett > wrote: > >> For a short-term fix, how about quickly re-introducing the gdm3 >> workaround? Then, we can experiment with possible ways to drop it and >> (more) carefully test the upgrade paths with packages that haven't been >> uploaded yet, and subsequently with experimental. > > I did that now in 3.14.2-2. Would be great if someone can help track > this down. I kept this bug open since I want to re-purpose it for tracking the process of re-adding BusName again. But I'm lowering the severity, so the package migrate to testing now. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#791964: gdm3: upgrade causes X session to be terminated
On Fri, 10 Jul 2015 09:38:56 -0700 Josh Triplett wrote: > For a short-term fix, how about quickly re-introducing the gdm3 > workaround? Then, we can experiment with possible ways to drop it and > (more) carefully test the upgrade paths with packages that haven't been > uploaded yet, and subsequently with experimental. I did that now in 3.14.2-2. Would be great if someone can help track this down. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#791964: gdm3: upgrade causes X session to be terminated
Am 10.07.2015 um 18:38 schrieb Josh Triplett: > On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: >> I'm not yet quite sure, if this is a gdm or systemd bug and whether the >> best course of action is to simply re-introduce the workaround patch and >> drop that in stretch+1 or if we drop the reload from gdm3.postinst or if >> this indeed another corner case which is not handled properly in systemd. > > For a short-term fix, how about quickly re-introducing the gdm3 > workaround? Then, we can experiment with possible ways to drop it and > (more) carefully test the upgrade paths with packages that haven't been > uploaded yet, and subsequently with experimental. I won't be around till monday. If someone fills like this needs immediate action, please use your best judgement and proceed. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#791964: gdm3: upgrade causes X session to be terminated
Am 10.07.2015 um 19:11 schrieb 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: >>> 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. Ah, ok, I meant the gdm upgrade indeed. Yeah, probably a bit misleading when you get this email out-of-context. This was filed against gdm3 after all, specifically for gdm being upgraded. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#791964: gdm3: upgrade causes X session to be terminated
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
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? signature.asc Description: OpenPGP digital signature
Bug#791964: gdm3: upgrade causes X session to be terminated
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. > I'm not yet quite sure, if this is a gdm or systemd bug and whether the > best course of action is to simply re-introduce the workaround patch and > drop that in stretch+1 or if we drop the reload from gdm3.postinst or if > this indeed another corner case which is not handled properly in systemd. For a short-term fix, how about quickly re-introducing the gdm3 workaround? Then, we can experiment with possible ways to drop it and (more) carefully test the upgrade paths with packages that haven't been uploaded yet, and subsequently with experimental. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
[keeping pkg-systemd into the loop here] Am 10.07.2015 um 14:37 schrieb Michael Biebl: > I suggest we follow up on this bug report. > > I'm not yet quite sure, if this is a gdm or systemd bug and whether the > best course of action is to simply re-introduce the workaround patch and > drop that in stretch+1 or if we drop the reload from gdm3.postinst or if > this indeed another corner case which is not handled properly in systemd. Joss, bigon: looking at gdm3.postinst, I wonder why we do run "invoke-rc.d gdm3 reload". Isn't that potentially dangerous, say we have a major new gdm3 upgrade with incompatible configuration and we tell the old, running gdm3 to reload this new configuration? Wouldn't we rather want a full-restart once all user sessions are closed? I'm not sure if gdm3 (still) supports that. As for the systemd specific part, I made an interesting observation, which might be related to the problem. Say you have gdm-3.14-7 runnig which has BusName *not* set. "systemctl show gdm3.service -p BusName -p Type" will return Type=simple (as expected). Merely changing the gdm3.service file on disk, and running "systemctl daemon-reload" *without* actually restarting gdm3, will now yield Type=dbus BusName=org.gnome.DisplayManager I find this behaviour unexpected and strange, i.e. changing the Type of a running job. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#791964: gdm3: upgrade causes X session to be terminated
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. > doing some work. That's highly unacceptable IMHO. Indeed. I didn't run into this while testing. Sorry for that. Bumping severity to RC, so other users are notified and the package doesn't migrate to testing. > I ran an apt-get upgrade, and suddenly my X session closed and I was > brought back to the gdm login screen. > > Pretty busy right now, but do let me know what could help to pinpoint > this issue and I'll try to provide more details. The issue seems to be reproducible and multiple users already reported the same issue: http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2015-July/008066.html (CCed) I suggest we follow up on this bug report. I'm not yet quite sure, if this is a gdm or systemd bug and whether the best course of action is to simply re-introduce the workaround patch and drop that in stretch+1 or if we drop the reload from gdm3.postinst or if this indeed another corner case which is not handled properly in systemd. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#791964: gdm3: upgrade causes X session to be terminated
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 doing some work. That's highly unacceptable IMHO. I ran an apt-get upgrade, and suddenly my X session closed and I was brought back to the gdm login screen. Pretty busy right now, but do let me know what could help to pinpoint this issue and I'll try to provide more details. ~David -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.40-2 ii adduser 3.113+nmu3 ii awesome [x-window-manager]3.5.6-1 ii dconf-cli 0.24.0-2 ii dconf-gsettings-backend 0.24.0-2 ii debconf [debconf-2.0] 1.5.56 ii gir1.2-gdm3 3.14.2-1 ii gnome-session-bin 3.16.0-1 ii gnome-settings-daemon 3.16.2-3 ii gnome-shell 3.16.3-1 ii gsettings-desktop-schemas 3.16.1-1 ii libaccountsservice0 0.6.40-2 ii libaudit1 1:2.4.2-1 ii libc6 2.19-18 ii libcanberra-gtk3-00.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-02.31.4-2 ii libgdm1 3.14.2-1 it libglib2.0-0 2.44.1-1.1 ii libglib2.0-bin2.44.1-1.1 iu libgtk-3-03.16.5-1 ii libpam-modules1.1.8-3.1 ii libpam-runtime1.1.8-3.1 ii libpam-systemd222-1 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.9-2 ii libselinux1 2.3-2+b1 ii libsystemd0 222-1 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.3-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxrandr22:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 iu metacity [x-window-manager] 1:3.17.2-4 ii mutter [x-window-manager] 3.16.3-1 ii policykit-1 0.105-10 ii rxvt [x-terminal-emulator]1:2.7.10-6 ii ucf 3.0030 ii x11-common1:7.7+9 ii x11-xserver-utils 7.7+4 ii xfce4-session [x-session-manager] 4.12.1-3 ii xfce4-terminal [x-terminal-emulator] 0.6.3-1+b2 ii xfwm4 [x-window-manager] 4.12.3-1 ii xterm [x-terminal-emulator] 318-2 Versions of packages gdm3 recommends: ii at-spi2-core 2.16.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+2 ii xserver-xephyr 2:1.17.2-1 ii xserver-xorg 1:7.7+9 ii zenity 3.16.3-1 Versions of packages gdm3 suggests: pn gnome-orca ii libpam-gnome-keyring 3.16.0-4 -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
