From owner-freebsd-questions@freebsd.org Sun Apr 21 02:47:01 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01E4C157E0B3 for ; Sun, 21 Apr 2019 02:47:01 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FA2886867 for ; Sun, 21 Apr 2019 02:47:00 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.126.133]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPA (Nemesis) id 1M1YtP-1hF0Ux0h5f-0031du; Sun, 21 Apr 2019 04:46:52 +0200 Date: Sun, 21 Apr 2019 04:46:51 +0200 From: Polytropon To: Victor Sudakov Cc: freebsd-questions@freebsd.org Subject: Re: AIGLX: Suspending AIGLX clients for VT switch Message-Id: <20190421044651.2332f5a1.freebsd@edvax.de> In-Reply-To: <20190420130228.GA31721@admin.sibptus.ru> References: <20190420130228.GA31721@admin.sibptus.ru> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:QbNiCGg46yHwGpCJVbkZzVEHI9gKbKEk+bJMsWlAImQxF+YmbqX o42EcCovsjoduDqzGkl/eLOeU3FrdnHyQIW2xaO55gtGuSxFYhC2fEXw3BI+a5kZgPEkJ+o OVIAQM5AIyUSFnM6Wog0Zc++3sFX0Hjm08SNc3aLWzxc8IQ3Qi/H9M/cvaXPOwdKXa0nje8 Fm2TVqdv9vNSqymh8oEEA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:mwjRgRaTdRQ=:0OHdV5TpfOjF52cjXzKhnd PYbrqj/Wu5SnNgsnw4QEuIMzbzTjWykP3CwzGZW4RguKY88Cwkny72yrqrQpu/4TH9kVTHXvD t3PCtE9q26KRwRrbSmMKZP0Pn2fpOMlxQ73YvVSbhJBlMOpFEZMDCPIfc9YKXwxg8avNfuOP2 SldmBJ272a2lo503WMLt7VdtJyU1S/fvBjQoMIC74tLKWeyra+y2C8A8czBKA1LEjIUFCkosh dNOeksibptIqOA+Pqhk755xBIB4WQKhGu+Uy9LZS03Je1VKluKAVYlk4DuCZqy7yI71exAVtK ertmPtui5R8FCBPV6XXXTMdZS2HxxG+fMEN1Aq81ecsPeF5PLDdxzJrpuvnv9Mq8RyGCjd25m Vs51gL9ZjPaq1f3Rwek7WWDzdt6+8XRiw1SiXGY+P0oJK10LByOSgNLSUWXXrmMdu0Y1okG0z CbwzpKtfH6r0R47v5mnx+dGL390Fr3tdWgR28loj+BUxEXDnrH9yLEUBMJ57gMmJQhTrr+ujl 5YZF/hVCfSF0HZwKDq4UzzsxNO93GutAYq6TfbnGrCfn90HY/VwbrpfPeM1GhUU+kqe8xLv9q kJIa2ZLE1TaKeJ+0lj0B1DvCP/Tw0W8prtjPE+8+tLOdJRUmOVFln8uMro42ewtJSHGk/hyNp JspXhWSGoPb5HRo1mZ04cGXVVj2DWPKfZp2Tjk+WQ4DXy58yLz+EPVFjerysh7i8WHmXTGRnO pFjgQNm7a7FQerHrzcs4vHTeUx4tASfXqUxQpx36Yjak1Nl4cC77M6guUAo= X-Rspamd-Queue-Id: 5FA2886867 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.982,0] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 02:47:01 -0000 On Sat, 20 Apr 2019 20:02:28 +0700, Victor Sudakov wrote: > Sometimes after I kill the xinit processes I see the following message: > > (II) AIGLX: Suspending AIGLX clients for VT switch > > I presume that something is preventing the vt switching from happening. THat's probably the same thing that makes vt an inappropriate replacement for sc. ;-) Have you tried disabling AIGLX? In a partial configuration file in X's configuration directory, /usr/local/etc/X11/xorg.conf.d/, you could try this: Section "ServerFlags" Option "DontVTSwitch" "false" Option "AIGLX" "false" EndSection Check for any missing functionality within X. > If vt switching crashes some X client, I'm > fine with it. Well, I don't think some of the most fundamental things (at least problem-less standard behaviour for decades with sc) should randomly crash X clients, but that's probably the price to pay if you want to run X today... > It is also remarkable that now I cannot kill the Xserver with > Control+Alt+Backspace any more. How can I regain this possibility? There seem to be several ways, and you need to experiment to find out which one works for you. A partial configuration file for your input device, for example: Section "InputDevice" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection Another one for the server layout: Section "ServerLayout" Option "DontZap" "false" EndSection And if you're using MATE, you're probably also using the dreaded combination of HAL and Dbus, things long forgotten in Linux land, but still required and present on many FreeBSD X desktop solutions. So here's something for /usr/local/etc/hal/fdi/policy/x11-input.fdi: terminate:ctrl_alt_bksp This seems to require the "DontZap" option mentioned earlier. Or a command for your X initialization file: setxkbmap -option terminate:ctrl_alt_bksp I have given up on using the console mode. Even if you can return to it, the screen might appear in a font only suited for ants. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...