From unknown Thu Mar 28 22:06:52 2024 Received: (at submit) by bugs.devuan.org; 13 May 2018 21:50:06 +0000 Return-Path: Delivered-To: devuanbugs@dyne.org Received: from tupac3.dyne.org [195.169.149.119] by fulcanelli with IMAP (fetchmail-6.3.26) for (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 ; 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 ; 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 ) id 1fHykx-0003DF-QG for submit@bugs.devuan.org; Sun, 13 May 2018 23:42:16 +0200 To: submit@bugs.devuan.org From: Michael Siegel Subject: ASCII: Default config in ~/.bash_logout crashes X server Message-ID: 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