GNU logs - #35509, boring messages

Message sent to bug-guix@HIDDEN:

Subject: bug#35509: Stopping gdm-service results in an unresponsive system
Resent-From: Mark H Weaver <mhw@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Tue, 30 Apr 2019 20:45:02 +0000
Resent-Message-ID: <handler.35509.B.155665704614170 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 35509 <at> debbugs.gnu.org
From: Mark H Weaver <mhw@HIDDEN>
Date: Tue, 30 Apr 2019 16:42:12 -0400
Message-ID: <877ebbmdhc.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

On my x86_64-linux system running the Guix system, when I include
gdm-service in my system services, 'herd stop xorg-server' results in a
state where I seemingly cannot recover except by rebooting.  I'm left in
what appears to be an empty Linux text console with a cursor in the top
left corner, but the keyboard is unresponsive, and I'm not able to
switch VTs.  Perhaps there is some SysRq key combination that could be
used to recover, but I haven't yet tried.

Since I prefer to use Wayland, and would rather not have a separate Xorg
session running that I never use, this means that currently I must avoid
using 'gdm-service' entirely.

Note that this is on a system running fairly recent 'master', but before
'staging' was merged.  I'll try again and report back after I've
finished rebuilding my post-staging-merge system.

     Regards,
       Mark

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Mark H Weaver <mhw@HIDDEN>
Subject: bug#35509: Acknowledgement (Stopping gdm-service results in an
 unresponsive system)
Message-ID: <handler.35509.B.155665704614170.ack <at> debbugs.gnu.org>
References: <877ebbmdhc.fsf@HIDDEN>
X-Gnu-PR-Message: ack 35509
X-Gnu-PR-Package: guix
Reply-To: 35509 <at> debbugs.gnu.org
Date: Tue, 30 Apr 2019 20:45:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guix@HIDDEN

If you wish to submit further information on this problem, please
send it to 35509 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
35509: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D35509
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guix@HIDDEN:

Subject: bug#35509: Stopping gdm-service results in an unresponsive system
Resent-From: Timothy Sample <samplet@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Wed, 01 May 2019 12:37:02 +0000
Resent-Message-ID: <handler.35509.B35509.15567142165556 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Mark H Weaver <mhw@HIDDEN>
Cc: 35509 <at> debbugs.gnu.org
From: Timothy Sample <samplet@HIDDEN>
References: <877ebbmdhc.fsf@HIDDEN>
Date: Wed, 01 May 2019 08:36:46 -0400
In-Reply-To: <877ebbmdhc.fsf@HIDDEN> (Mark H. Weaver's message of "Tue, 30
 Apr 2019 16:42:12 -0400")
Message-ID: <87imuupd0h.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi Mark,

Mark H Weaver <mhw@HIDDEN> writes:

> On my x86_64-linux system running the Guix system, when I include
> gdm-service in my system services, 'herd stop xorg-server' results in a
> state where I seemingly cannot recover except by rebooting.  I'm left in
> what appears to be an empty Linux text console with a cursor in the top
> left corner, but the keyboard is unresponsive, and I'm not able to
> switch VTs.  Perhaps there is some SysRq key combination that could be
> used to recover, but I haven't yet tried.

This has been an issue with GDM since I started working on it.  IIRC,
it=E2=80=99s not entirely deterministic (but it fails most of the time).  I
don=E2=80=99t have any leads on this yet.

> Since I prefer to use Wayland, and would rather not have a separate Xorg
> session running that I never use, this means that currently I must avoid
> using 'gdm-service' entirely.

Yes.  The service does not currently support Wayland.  I believe that
Wayland support will require a few modifications to GDM itself.  At
least, we ended up modifying the X session startup a little bit, and I
would guess that the Wayland session startup would need similar changes.

> Note that this is on a system running fairly recent 'master', but before
> 'staging' was merged.  I'll try again and report back after I've
> finished rebuilding my post-staging-merge system.

Unfortunately, I wouldn=E2=80=99t expect the changes from staging to help h=
ere.

-- Tim

Message sent to bug-guix@HIDDEN:

Subject: bug#35509: Stopping gdm-service results in an unresponsive system
Resent-From: Timothy Sample <samplet@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Thu, 02 May 2019 19:46:02 +0000
Resent-Message-ID: <handler.35509.B35509.155682633625487 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Mark H Weaver <mhw@HIDDEN>
Cc: 35509 <at> debbugs.gnu.org
From: Timothy Sample <samplet@HIDDEN>
References: <877ebbmdhc.fsf@HIDDEN> <87imuupd0h.fsf@HIDDEN>
Date: Thu, 02 May 2019 15:45:25 -0400
In-Reply-To: <87imuupd0h.fsf@HIDDEN> (Timothy Sample's message of "Wed, 01
 May 2019 08:36:46 -0400")
Message-ID: <87ef5gprmy.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi again,

Timothy Sample <samplet@HIDDEN> writes:

> Mark H Weaver <mhw@HIDDEN> writes:
>
>> On my x86_64-linux system running the Guix system, when I include
>> gdm-service in my system services, 'herd stop xorg-server' results in a
>> state where I seemingly cannot recover except by rebooting.  I'm left in
>> what appears to be an empty Linux text console with a cursor in the top
>> left corner, but the keyboard is unresponsive, and I'm not able to
>> switch VTs.  Perhaps there is some SysRq key combination that could be
>> used to recover, but I haven't yet tried.
>
> This has been an issue with GDM since I started working on it.  IIRC,
> it=E2=80=99s not entirely deterministic (but it fails most of the time). =
 I
> don=E2=80=99t have any leads on this yet.

I have a lead now!  At least, I have a way to stop GDM and return to a
working TTY.  Assuming that you are working on a TTY with elogind
session =E2=80=9Cc1=E2=80=9D, you can run

    herd stop xorg-server & (sleep 5; loginctl activate c1)

When GDM exits, it leaves the display in a non-working state.  It turns
out elogind knows how to fix this.  I=E2=80=99m guessing it does some magic=
 with
the VT_* set of ioctl requests (see =E2=80=9Csrc/basic/terminal-util.c=E2=
=80=9D from
elogind).  I=E2=80=99m not sure how to get GDM to clean up after itself, th=
ough.
It might be expecting things of elogind that it doesn=E2=80=99t provide (si=
nce
it is not exactly like the original logind from systemd).


-- Tim

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#35509: Stopping gdm-service results in an unresponsive system
Resent-From: Mark H Weaver <mhw@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Thu, 02 May 2019 21:49:01 +0000
Resent-Message-ID: <handler.35509.B35509.15568337074249 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 35509
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Timothy Sample <samplet@HIDDEN>
Cc: 35509 <at> debbugs.gnu.org
Received: via spool by 35509-submit <at> debbugs.gnu.org id=B35509.15568337074249
          (code B ref 35509); Thu, 02 May 2019 21:49:01 +0000
Received: (at 35509) by debbugs.gnu.org; 2 May 2019 21:48:27 +0000
Received: from localhost ([127.0.0.1]:47192 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1hMJZ3-00016S-CX
	for submit <at> debbugs.gnu.org; Thu, 02 May 2019 17:48:27 -0400
Received: from world.peace.net ([64.112.178.59]:48670)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <mhw@HIDDEN>) id 1hMJZ1-00016F-6X
 for 35509 <at> debbugs.gnu.org; Thu, 02 May 2019 17:48:23 -0400
Received: from mhw by world.peace.net with esmtpsa
 (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89)
 (envelope-from <mhw@HIDDEN>)
 id 1hMJYu-0002Iz-QI; Thu, 02 May 2019 17:48:16 -0400
From: Mark H Weaver <mhw@HIDDEN>
References: <877ebbmdhc.fsf@HIDDEN> <87imuupd0h.fsf@HIDDEN>
 <87ef5gprmy.fsf@HIDDEN>
Date: Thu, 02 May 2019 17:46:31 -0400
In-Reply-To: <87ef5gprmy.fsf@HIDDEN> (Timothy Sample's message of "Thu, 02
 May 2019 15:45:25 -0400")
Message-ID: <877eb8o7fx.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Hi Timothy,

Timothy Sample <samplet@HIDDEN> writes:

> I have a lead now!  At least, I have a way to stop GDM and return to a
> working TTY.  Assuming that you are working on a TTY with elogind
> session =E2=80=9Cc1=E2=80=9D, you can run
>
>     herd stop xorg-server & (sleep 5; loginctl activate c1)
>
> When GDM exits, it leaves the display in a non-working state.  It turns
> out elogind knows how to fix this.  I=E2=80=99m guessing it does some mag=
ic with
> the VT_* set of ioctl requests (see =E2=80=9Csrc/basic/terminal-util.c=E2=
=80=9D from
> elogind).  I=E2=80=99m not sure how to get GDM to clean up after itself, =
though.
> It might be expecting things of elogind that it doesn=E2=80=99t provide (=
since
> it is not exactly like the original logind from systemd).

Thanks for investigating!

My first guess is that when GDM is killed, it's leaving the keyboard
in RAW mode.  Running "kbd_mode -a" might be another way to recover.
"Alt + SysRq + r" might be another way.  I'll try again after I finish
building my post-staging-merge system.

  https://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO-9.html

I notice that in Debian's start script for gdm3, it runs activate_logind
just before launching GDM, where activate_logind is the following Bash
function:

  activate_logind() {
    # Try to dbus activate logind to avoid a race conditions if we are not
    # running systemd as PID1 and we have systemd << 204 package installed =
(see:
    # #747292)
    if [ ! -d /run/systemd/system ] && [ -x /lib/systemd/systemd-logind-lau=
nch ]; then
      dbus-send --system --print-reply --dest=3Dorg.freedesktop.DBus /org/f=
reedesktop/DBus \
        org.freedesktop.DBus.StartServiceByName string:org.freedesktop.logi=
n1 uint32:0 2>&1 > /dev/null
    fi
  }

The Debian start script is debian/gdm3.init in
<http://deb.debian.org/debian/pool/main/g/gdm3/gdm3_3.22.3-3+deb9u2.debian.=
tar.xz>.

The Debian bug referenced above is <https://bugs.debian.org/747292>.

Might be worth a try, but admittedly I'm grasping at straws here :)

       Mark

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#35509: Stopping gdm-service results in an unresponsive system
Resent-From: Timothy Sample <samplet@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Fri, 03 May 2019 02:16:01 +0000
Resent-Message-ID: <handler.35509.B35509.155684972528424 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 35509
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Mark H Weaver <mhw@HIDDEN>
Cc: 35509 <at> debbugs.gnu.org
Received: via spool by 35509-submit <at> debbugs.gnu.org id=B35509.155684972528424
          (code B ref 35509); Fri, 03 May 2019 02:16:01 +0000
Received: (at 35509) by debbugs.gnu.org; 3 May 2019 02:15:25 +0000
Received: from localhost ([127.0.0.1]:47445 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1hMNjO-0007OJ-8p
	for submit <at> debbugs.gnu.org; Thu, 02 May 2019 22:15:25 -0400
Received: from out3-smtp.messagingengine.com ([66.111.4.27]:42391)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <samplet@HIDDEN>) id 1hMNjM-0007O6-0h
 for 35509 <at> debbugs.gnu.org; Thu, 02 May 2019 22:15:20 -0400
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailout.nyi.internal (Postfix) with ESMTP id 6BCE322EFE;
 Thu,  2 May 2019 22:15:14 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
 by compute4.internal (MEProxy); Thu, 02 May 2019 22:15:14 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm2; bh=fppIB0WmOsDePP4iFkFh7gdgNt7tbN02fOXQeBfTD
 p4=; b=JKyUwk+6+mEmyP+mop08juVSO1VgRg+iq1f9AqcWTwcwju8xqPCvi4Fk0
 fojTcWmxV4eRSGYfLtUEFGFmiocyV3teol3cI+v7Kw/2NB9HTnFgruM/6Of7A+pA
 OQYgSbsV+Ly3+Lt3R0oLQR6siuHYUX7g11BlwHKbQTxaXw3zozdTJTZal1KJrKGu
 XbQIBnN7Aag9PKf96FKgT+d5Z5IHXTpZrRnFvLKrEscGrLF4KeJWsfYu9tcQjqek
 MKcyN3w2Xn6c12BqLP2YUQEs46TYrKoPioHZEOccIF8xNXCBGNqsm7IdFLt1UC1j
 SwvqOS1OQAfRmoj+GSSi4JImGJBgQ==
X-ME-Sender: <xms:MaTLXKsoRbkgwyNQKdj8HNeltdEGX5miLvGD5W2zPhbCXXho3fFDIA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrjedtgdehiecutefuodetggdotefrodftvf
 curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
 uegrihhlohhuthemuceftddtnecunecujfgurhephffvufhfffgjkfgfgggtgfesthhqre
 dttderjeenucfhrhhomhepvfhimhhothhhhicuufgrmhhplhgvuceoshgrmhhplhgvthes
 nhhghihrohdrtghomheqnecuffhomhgrihhnpeguvggsihgrnhdrohhrghdpthhlughprd
 horhhgnecukfhppeejgedrudduiedrudekiedrgeegnecurfgrrhgrmhepmhgrihhlfhhr
 ohhmpehsrghmphhlvghtsehnghihrhhordgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:MaTLXA8PZ44X317ZOLkpViy4Dn8JCO4zT70jkOKST8i2iC7shpZkxg>
 <xmx:MaTLXOZxVdJ99YgUKJ403ubF1HAjln9aItmBO4SCEkRuCygCZqa6dw>
 <xmx:MaTLXHM1FwxJBc5y3sAP832s1amzXaKeda5EXEsH-hwGekcPpyusAA>
 <xmx:MqTLXP0yNbxCh03g1pcgvoENH0GwgxeBdX6ZowjEjKJE4RFG0X6Ujg>
Received: from mrblack (74-116-186-44.qc.dsl.ebox.net [74.116.186.44])
 by mail.messagingengine.com (Postfix) with ESMTPA id 4AD7610369;
 Thu,  2 May 2019 22:15:13 -0400 (EDT)
From: Timothy Sample <samplet@HIDDEN>
References: <877ebbmdhc.fsf@HIDDEN> <87imuupd0h.fsf@HIDDEN>
 <87ef5gprmy.fsf@HIDDEN> <877eb8o7fx.fsf@HIDDEN>
Date: Thu, 02 May 2019 22:15:12 -0400
In-Reply-To: <877eb8o7fx.fsf@HIDDEN> (Mark H. Weaver's message of "Thu, 02
 May 2019 17:46:31 -0400")
Message-ID: <87bm0kz3kf.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.7 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

Hi Mark,

Mark H Weaver <mhw@HIDDEN> writes:

> Timothy Sample <samplet@HIDDEN> writes:
>
>> I have a lead now!  At least, I have a way to stop GDM and return to a
>> working TTY.  Assuming that you are working on a TTY with elogind
>> session =E2=80=9Cc1=E2=80=9D, you can run
>>
>>     herd stop xorg-server & (sleep 5; loginctl activate c1)
>>
>> When GDM exits, it leaves the display in a non-working state.  It turns
>> out elogind knows how to fix this.  I=E2=80=99m guessing it does some ma=
gic with
>> the VT_* set of ioctl requests (see =E2=80=9Csrc/basic/terminal-util.c=
=E2=80=9D from
>> elogind).  I=E2=80=99m not sure how to get GDM to clean up after itself,=
 though.
>> It might be expecting things of elogind that it doesn=E2=80=99t provide =
(since
>> it is not exactly like the original logind from systemd).
>
> Thanks for investigating!
>
> My first guess is that when GDM is killed, it's leaving the keyboard
> in RAW mode.  Running "kbd_mode -a" might be another way to recover.
> "Alt + SysRq + r" might be another way.  I'll try again after I finish
> building my post-staging-merge system.
>
>   https://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO-9.html

Indeed.  I saw this earlier today.  I looked at the source for elogind,
and all it does is =E2=80=9CVT_ACTIVATE=E2=80=9D =E2=80=93 no magic there. =
 The loginctl command
can be replaced with =E2=80=9Cchvt 1=E2=80=9D.  The =E2=80=9CSysRq + r=E2=
=80=9D trick works too.  In
fact, I saw this in the X.org logs:

--------------------------------
(II) UnloadModule: "libinput"
(II) systemd-logind: releasing fd for 13:67
(EE) systemd-logind: failed to release device: Unknown object '/org/freedes=
ktop/login1/session/c4'.
(II) UnloadModule: "libinput"
(II) systemd-logind: releasing fd for 13:68
(EE) systemd-logind: failed to release device: Unknown object '/org/freedes=
ktop/login1/session/c4'.
(II) UnloadModule: "libinput"
(II) systemd-logind: releasing fd for 13:65
(EE) systemd-logind: failed to release device: Unknown object '/org/freedes=
ktop/login1/session/c4'.
(II) UnloadModule: "libinput"
(II) systemd-logind: releasing fd for 13:64
(EE) systemd-logind: failed to release device: Unknown object '/org/freedes=
ktop/login1/session/c4'.
(EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedeskto=
p/login1/session/c4'.
(II) Server terminated successfully (0). Closing log file.
--------------------------------

I wonder if GDM is destroying the session before X can call its
=E2=80=9CReleaseControl=E2=80=9D method.  Maybe this keeps X from restoring=
 the terminal
properly.

> I notice that in Debian's start script for gdm3, it runs activate_logind
> just before launching GDM, where activate_logind is the following Bash
> function:
>
>   activate_logind() {
>     # Try to dbus activate logind to avoid a race conditions if we are not
>     # running systemd as PID1 and we have systemd << 204 package installe=
d (see:
>     # #747292)
>     if [ ! -d /run/systemd/system ] && [ -x /lib/systemd/systemd-logind-l=
aunch ]; then
>       dbus-send --system --print-reply --dest=3Dorg.freedesktop.DBus /org=
/freedesktop/DBus \
>         org.freedesktop.DBus.StartServiceByName string:org.freedesktop.lo=
gin1 uint32:0 2>&1 > /dev/null
>     fi
>   }
>
> The Debian start script is debian/gdm3.init in
> <http://deb.debian.org/debian/pool/main/g/gdm3/gdm3_3.22.3-3+deb9u2.debia=
n.tar.xz>.
>
> The Debian bug referenced above is <https://bugs.debian.org/747292>.
>
> Might be worth a try, but admittedly I'm grasping at straws here :)

I gave this a try and... it didn=E2=80=99t help.  :(

Looking a little closer at the systemd source, I found out that they
have logic to reset terminal settings when a service becomes =E2=80=9Cdead=
=E2=80=9D (see
=E2=80=9Cexec_context_revert_tty=E2=80=9D as called from =E2=80=9Cservice_e=
nter_dead=E2=80=9D in the
file =E2=80=9Csrc/core/service.c=E2=80=9D).  I wonder if GDM relies on that.


-- Tim

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.