Devuan bug report logs - #209
ASCII: Default config in ~/.bash_logout crashes X server

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Mark Hindley <mark@hindley.org.uk>
Subject: bug#209: marked as done (ASCII: Default config in ~/.bash_logout
 crashes X server)
Message-ID: <handler.209.D209.167415111921517.ackdone@bugs.devuan.org>
References: <Y8mEl8fSHAC93oa0@hindley.org.uk>
 <fce8085e-c24a-2280-50ef-16b098cf6b64@malbolge.net>
X-Devuan-PR-Message: closed 209
X-Devuan-PR-Package: bash
X-Devuan-PR-Keywords: debian
Reply-To: 209@bugs.devuan.org
Date: Thu, 19 Jan 2023 18:00:01 +0000
Content-Type: multipart/mixed; boundary="----------=_1674151201-21553-0"

[Message part 1 (text/plain, inline)]

Your message dated Thu, 19 Jan 2023 17:57:43 +0000
with message-id <Y8mEl8fSHAC93oa0@hindley.org.uk>
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 owner@bugs.devuan.org
immediately.)


-- 
209: https://bugs.devuan.org/cgi/bugreport.cgi?bug=209
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Michael Siegel <msi@malbolge.net>

To: submit@bugs.devuan.org

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

Date: Sun, 13 May 2018 23:42:09 +0200

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 part 3 (message/rfc822, inline)]

From: Mark Hindley <mark@hindley.org.uk>

To: 209-done@bugs.devuan.org

Subject: Fixed in Debian #810660

Date: Thu, 19 Jan 2023 17:57:43 +0000

Version: 5.0-3

Send a report that this bug log contains spam.