Devuan logs - #209, boring messages


Message sent to [email protected], [email protected]:


X-Loop: [email protected]
Subject: bug#209: ASCII: Default config in ~/.bash_logout crashes X server
Reply-To: Michael Siegel <[email protected]>, [email protected]
Resent-From: Michael Siegel <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Sun, 13 May 2018 22:03:01 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: report 209
X-Devuan-PR-Package: bash
X-Devuan-PR-Keywords: 
Received: via spool by [email protected] id=B.15262482061967
          (code B ref -1); Sun, 13 May 2018 22:03:01 UTC
Received: (at submit) by bugs.devuan.org; 13 May 2018 21:50:06 +0000
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Sun, 13 May 2018 23:50:06 +0200 (CEST)
Received: from poseidon.malbolge.net (poseidon.malbolge.net [5.45.108.48])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id F19F3F608B1
	for <[email protected]>; Sun, 13 May 2018 23:44:03 +0200 (CEST)
Received: from hermes.malbolge.net (hermes.malbolge.net [192.168.123.201])
	by poseidon.malbolge.net (OpenSMTPD) with ESMTPSA id f5de56dc (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO)
	for <[email protected]>;
	Sun, 13 May 2018 23:42:17 +0200 (CEST)
Received: from kerberos.malbolge.net ([192.168.123.128] helo=127.0.0.1)
	by hermes.malbolge.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.89)
	(envelope-from <[email protected]>)
	id 1fHykx-0003DF-QG
	for [email protected]; Sun, 13 May 2018 23:42:16 +0200
To: [email protected]
From: Michael Siegel <[email protected]>
Message-ID: <[email protected]>
Date: Sun, 13 May 2018 23:42:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD,SPF_PASS
	autolearn=disabled version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tupac3.dyne.org

Package: bash
Version: 4.4-5

When running X on VT1 and another user session (CLI) on VT2, logging out
on VT2, will either

  * crash the X server running on VT1, leaving you with a functional CLI
or
  * leave you with a blank screen and an apparently frozen-up system
    once you switch back to VT1

Running X with setuid root does not make any difference here. But if the
user on VT2 is root, X on VT1 will not crash when logging out on VT2.

In a discussion on Debian's IRC channel, I've been informed that this
problem is caused by the default configuration in ~/.bash_logout, which
looks like this:

  # ~/.bash_logout: executed by bash(1) when login shell exits.

  # when leaving the console clear the screen to increase privacy

  if [ "$SHLVL" = 1 ]; then
      [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
  fi

Commenting out the if statement (or just deleting the file) will cure
the problem.

The culprit here is clear_console. Running /usr/bin/clear_console from
VT2 in the scenario described above will result in the same problems you
get when logging out.

fsmithred has also found that this problem does not occur on D-Bus-free
installations (with the above config in place).


msi


Message sent:


X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: Michael Siegel <[email protected]>
Subject: bug#209: Acknowledgement (ASCII: Default config in ~/.bash_logout crashes X server)
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
Precedence: bulk
X-Devuan-PR-Message: ack 209
X-Devuan-PR-Package: bash
X-Devuan-PR-Keywords: 
Reply-To: [email protected]

Thank you for the problem report you have sent regarding Devuan.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers mailing list for
their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 [email protected]

If you wish to submit further information on your problem, please send
it to [email protected] (and *not* to
[email protected]).

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Devuan Bugs Owner
(administrator, Devuan bugs database)


Message sent to [email protected], [email protected]:


X-Loop: [email protected]
Subject: bug#209: Debian changelog for Bash in Stretch
Reply-To: Michael Siegel <[email protected]>, [email protected]
Resent-From: Michael Siegel <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Mon, 14 May 2018 15:18:01 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: report 209
X-Devuan-PR-Package: bash
X-Devuan-PR-Keywords: 
Received: via spool by [email protected] id=B209.15263106027081
          (code B ref 209); Mon, 14 May 2018 15:18:01 UTC
Received: (at 209) by bugs.devuan.org; 14 May 2018 15:10:02 +0000
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Mon, 14 May 2018 17:10:02 +0200 (CEST)
Received: from poseidon.malbolge.net (poseidon.malbolge.net [5.45.108.48])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id AEF40F60A2B
	for <[email protected]>; Mon, 14 May 2018 17:05:17 +0200 (CEST)
Received: from hermes.malbolge.net (hermes.malbolge.net [192.168.123.201])
	by poseidon.malbolge.net (OpenSMTPD) with ESMTPSA id 07bd29e6 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO)
	for <[email protected]>;
	Mon, 14 May 2018 17:03:30 +0200 (CEST)
Received: from kerberos.malbolge.net ([192.168.123.128] helo=127.0.0.1)
	by hermes.malbolge.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.89)
	(envelope-from <[email protected]>)
	id 1fIF0b-0003QF-Ux
	for [email protected]; Mon, 14 May 2018 17:03:30 +0200
To: [email protected]
From: Michael Siegel <[email protected]>
Message-ID: <[email protected]>
Date: Mon, 14 May 2018 17:03:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD,SPF_PASS
	autolearn=disabled version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tupac3.dyne.org

The Debian changelog for the package of Bash in Stretch includes:

  bash (4.4-3) unstable; urgency=medium

    * Apply upstream patches 006 - 007.
    * clear_console: Securely erase the current console. Closes:
      #845177.
    * Mark locales and time build dependencies with <!nocheck>.
      Closes: #838201.
    * Don't configure with --with-curses. Closes: #794588.

   -- Matthias Klose <[email protected]>  Fri, 20 Jan 2017 11:52:59 +0100


msi


Message sent:


X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: Michael Siegel <[email protected]>
Subject: bug#209: Info received (was Debian changelog for Bash in Stretch)
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
Precedence: bulk
X-Devuan-PR-Message: ack-info 209
X-Devuan-PR-Package: bash
X-Devuan-PR-Keywords: 
Disabled-Doogie-Reply-To: [email protected]

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developer(s) and
to the developers mailing list to accompany the original report.

Your message has been sent to the package maintainer(s):
 [email protected]

If you wish to continue to submit further information on your problem,
please send it to [email protected], as before.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Devuan Bugs Owner
(administrator, Devuan bugs database)


Message received at [email protected]:


Received: (at control) by bugs.devuan.org; 19 Jan 2023 17:42:08 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Thu, 19 Jan 2023 17:42:08 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id fVUMH9KAyWMOBwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Thu, 19 Jan 2023 17:41:38 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 756001222; Thu, 19 Jan 2023 17:41:38 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 2C1BEB69
	for <[email protected]>; Thu, 19 Jan 2023 17:41:37 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pIYuu-0000mC-Mx
	for [email protected]; Thu, 19 Jan 2023 17:41:36 +0000
Received: (nullmailer pid 3181 invoked by uid 1000);
	Thu, 19 Jan 2023 17:41:36 -0000
Date: Thu, 19 Jan 2023 17:41:36 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: bug 209 is forwarded to https://bugs.debian.org/810660
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: devscripts bts/2.22.2
X-Debbugs-No-Ack: No Thanks

tags 209 debian
forwarded 209 https://bugs.debian.org/810660
thanks


Message received at [email protected]:


Received: (at control) by bugs.devuan.org; 19 Jan 2023 17:42:08 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Thu, 19 Jan 2023 17:42:08 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id fVUMH9KAyWMOBwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Thu, 19 Jan 2023 17:41:38 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 756001222; Thu, 19 Jan 2023 17:41:38 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 2C1BEB69
	for <[email protected]>; Thu, 19 Jan 2023 17:41:37 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pIYuu-0000mC-Mx
	for [email protected]; Thu, 19 Jan 2023 17:41:36 +0000
Received: (nullmailer pid 3181 invoked by uid 1000);
	Thu, 19 Jan 2023 17:41:36 -0000
Date: Thu, 19 Jan 2023 17:41:36 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: bug 209 is forwarded to https://bugs.debian.org/810660
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: devscripts bts/2.22.2
X-Debbugs-No-Ack: No Thanks

tags 209 debian
forwarded 209 https://bugs.debian.org/810660
thanks


Message sent:


MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Mark Hindley <[email protected]>
Subject: bug#209: marked as done (ASCII: Default config in ~/.bash_logout
 crashes X server)
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
X-Devuan-PR-Message: closed 209
X-Devuan-PR-Package: bash
X-Devuan-PR-Keywords: debian
Reply-To: [email protected]
Date: Thu, 19 Jan 2023 18:00:01 +0000
Content-Type: multipart/mixed; boundary="----------=_1674151201-21553-0"

This is a multi-part message in MIME format...

------------=_1674151201-21553-0
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Your message dated Thu, 19 Jan 2023 17:57:43 +0000
with message-id <[email protected]>
and subject line Fixed in Debian #810660
has caused the Devuan bug report #209,
regarding ASCII: Default config in ~/.bash_logout crashes X server
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


--=20
209: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D209
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1674151201-21553-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 13 May 2018 21:50:06 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Sun, 13 May 2018 23:50:06 +0200 (CEST)
Received: from poseidon.malbolge.net (poseidon.malbolge.net [5.45.108.48])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id F19F3F608B1
	for <[email protected]>; Sun, 13 May 2018 23:44:03 +0200 (CEST)
Received: from hermes.malbolge.net (hermes.malbolge.net [192.168.123.201])
	by poseidon.malbolge.net (OpenSMTPD) with ESMTPSA id f5de56dc (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO)
	for <[email protected]>;
	Sun, 13 May 2018 23:42:17 +0200 (CEST)
Received: from kerberos.malbolge.net ([192.168.123.128] helo=127.0.0.1)
	by hermes.malbolge.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.89)
	(envelope-from <[email protected]>)
	id 1fHykx-0003DF-QG
	for [email protected]; Sun, 13 May 2018 23:42:16 +0200
To: [email protected]
From: Michael Siegel <[email protected]>
Subject: ASCII: Default config in ~/.bash_logout crashes X server
Message-ID: <[email protected]>
Date: Sun, 13 May 2018 23:42:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD,SPF_PASS
	autolearn=disabled version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tupac3.dyne.org

Package: bash
Version: 4.4-5

When running X on VT1 and another user session (CLI) on VT2, logging out
on VT2, will either

  * crash the X server running on VT1, leaving you with a functional CLI
or
  * leave you with a blank screen and an apparently frozen-up system
    once you switch back to VT1

Running X with setuid root does not make any difference here. But if the
user on VT2 is root, X on VT1 will not crash when logging out on VT2.

In a discussion on Debian's IRC channel, I've been informed that this
problem is caused by the default configuration in ~/.bash_logout, which
looks like this:

  # ~/.bash_logout: executed by bash(1) when login shell exits.

  # when leaving the console clear the screen to increase privacy

  if [ "$SHLVL" = 1 ]; then
      [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
  fi

Commenting out the if statement (or just deleting the file) will cure
the problem.

The culprit here is clear_console. Running /usr/bin/clear_console from
VT2 in the scenario described above will result in the same problems you
get when logging out.

fsmithred has also found that this problem does not occur on D-Bus-free
installations (with the above config in place).


msi

------------=_1674151201-21553-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 209-done) by bugs.devuan.org; 19 Jan 2023 17:58:39 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Thu, 19 Jan 2023 17:58:39 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Fu7NAJmEyWPrBwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Thu, 19 Jan 2023 17:57:45 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id EC8B4121D; Thu, 19 Jan 2023 17:57:44 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AD875226
	for <[email protected]>; Thu, 19 Jan 2023 17:57:44 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pIZAV-0000ri-RB
	for [email protected]; Thu, 19 Jan 2023 17:57:43 +0000
Received: (nullmailer pid 8321 invoked by uid 1000);
	Thu, 19 Jan 2023 17:57:43 -0000
Date: Thu, 19 Jan 2023 17:57:43 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: Fixed in Debian #810660
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debbugs-No-Ack: No Thanks

Version: 5.0-3
------------=_1674151201-21553-0--

Message sent:


MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Michael Siegel <[email protected]>
Subject: bug#209 closed by Mark Hindley <[email protected]> (Fixed in
 Debian #810660)
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
X-Devuan-PR-Message: they-closed 209
X-Devuan-PR-Package: bash
X-Devuan-PR-Keywords: debian
Reply-To: [email protected]
Date: Thu, 19 Jan 2023 18:00:03 +0000
Content-Type: multipart/mixed; boundary="----------=_1674151203-21553-1"

This is a multi-part message in MIME format...

------------=_1674151203-21553-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

This is an automatic notification regarding your bug report
which was filed against the bash package:

#209: ASCII: Default config in ~/.bash_logout crashes X server

It has been closed by Mark Hindley <[email protected]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hin=
dley.org.uk> by
replying to this email.


--=20
209: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D209
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1674151203-21553-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 209-done) by bugs.devuan.org; 19 Jan 2023 17:58:39 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Thu, 19 Jan 2023 17:58:39 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Fu7NAJmEyWPrBwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Thu, 19 Jan 2023 17:57:45 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id EC8B4121D; Thu, 19 Jan 2023 17:57:44 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AD875226
	for <[email protected]>; Thu, 19 Jan 2023 17:57:44 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pIZAV-0000ri-RB
	for [email protected]; Thu, 19 Jan 2023 17:57:43 +0000
Received: (nullmailer pid 8321 invoked by uid 1000);
	Thu, 19 Jan 2023 17:57:43 -0000
Date: Thu, 19 Jan 2023 17:57:43 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: Fixed in Debian #810660
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debbugs-No-Ack: No Thanks

Version: 5.0-3
------------=_1674151203-21553-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 13 May 2018 21:50:06 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Sun, 13 May 2018 23:50:06 +0200 (CEST)
Received: from poseidon.malbolge.net (poseidon.malbolge.net [5.45.108.48])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id F19F3F608B1
	for <[email protected]>; Sun, 13 May 2018 23:44:03 +0200 (CEST)
Received: from hermes.malbolge.net (hermes.malbolge.net [192.168.123.201])
	by poseidon.malbolge.net (OpenSMTPD) with ESMTPSA id f5de56dc (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO)
	for <[email protected]>;
	Sun, 13 May 2018 23:42:17 +0200 (CEST)
Received: from kerberos.malbolge.net ([192.168.123.128] helo=127.0.0.1)
	by hermes.malbolge.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.89)
	(envelope-from <[email protected]>)
	id 1fHykx-0003DF-QG
	for [email protected]; Sun, 13 May 2018 23:42:16 +0200
To: [email protected]
From: Michael Siegel <[email protected]>
Subject: ASCII: Default config in ~/.bash_logout crashes X server
Message-ID: <[email protected]>
Date: Sun, 13 May 2018 23:42:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD,SPF_PASS
	autolearn=disabled version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tupac3.dyne.org

Package: bash
Version: 4.4-5

When running X on VT1 and another user session (CLI) on VT2, logging out
on VT2, will either

  * crash the X server running on VT1, leaving you with a functional CLI
or
  * leave you with a blank screen and an apparently frozen-up system
    once you switch back to VT1

Running X with setuid root does not make any difference here. But if the
user on VT2 is root, X on VT1 will not crash when logging out on VT2.

In a discussion on Debian's IRC channel, I've been informed that this
problem is caused by the default configuration in ~/.bash_logout, which
looks like this:

  # ~/.bash_logout: executed by bash(1) when login shell exits.

  # when leaving the console clear the screen to increase privacy

  if [ "$SHLVL" = 1 ]; then
      [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
  fi

Commenting out the if statement (or just deleting the file) will cure
the problem.

The culprit here is clear_console. Running /usr/bin/clear_console from
VT2 in the scenario described above will result in the same problems you
get when logging out.

fsmithred has also found that this problem does not occur on D-Bus-free
installations (with the above config in place).


msi

------------=_1674151203-21553-1--

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <[email protected]>.
Last modified: Wed, 29 Jan 2025 20:39:01 UTC