From owner-freebsd-questions@freebsd.org Sun Apr 21 19:17:21 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 B619B1582486 for ; Sun, 21 Apr 2019 19:17:21 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3100A867B8 for ; Sun, 21 Apr 2019 19:17:21 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.126.133]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.183]) with ESMTPA (Nemesis) id 1N8ojI-1gmnAS0WpS-015mrP; Sun, 21 Apr 2019 21:17:14 +0200 Date: Sun, 21 Apr 2019 21:17:13 +0200 From: Polytropon To: Victor Sudakov Cc: freebsd-questions@freebsd.org Subject: Re: AIGLX: Suspending AIGLX clients for VT switch Message-Id: <20190421211713.e7d55666.freebsd@edvax.de> In-Reply-To: <20190421050407.GB49101@admin.sibptus.ru> References: <20190420130228.GA31721@admin.sibptus.ru> <20190421044651.2332f5a1.freebsd@edvax.de> <20190421050407.GB49101@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:bZhz7szNADbGIEEnA0xmEsm1R1wcdROAWM7jKGO6tg1yG19nx2W qxQ3uhd6TpQOZJ3vGgsEjCFPbXWBEQLMw9mY8l5DSbo4mz67nGp6JGzzxKGlWukqKWzQW4G IjqGudfD0+yC81LvKH//tEh+lgNwUvaWfO3dyLfsQYFa53697gby3Yde1SS976v+jB8OqQ5 PW2ql7EDw/dSgvuUROuaQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:52dkfUSxS9s=:tiNnusCV3bTW3ahHdtsOLf VawE5NOhanaZ7ipgc/36rmt/28kBPa28LsAvkUIyIpCP8w0ww6CtWgwYaRMPSZMROeMwuRWn1 qx+F5XTMsdERk+KpdkL5N/gJLxe7IxY3pT+ye+0e/wrqpeCCyAMTuQhXVmyxYkR9uQaVqq5LR M+K2WADooJcM+qA5g+CCMep9GSy9v2xovljHMZP5ygYQoXgp0rvv2q3Vxj0qdmmRI7hnS+vJK PB3PrGYwElJ6SoP/0wXA7Zem1GXGX7yOk4aM14RGZPLZrEUtWl2CjPaq1GlX7bVyOFfjKC0bP lCTeo34IjSLfss6vwiy9wCjGdXgi3swH24i/nsg2Agx/dAHX8XppmeaPnremicbwSOj9OwWwQ I+u4VE1cAm/nbnYoqePc1tBPt9CEywX7JgK0x/RRjswfN3pd9SZQlxDckdZgZklUzeFZDo/WI ymoWjUOBQ/T29bBuD+jDjOh3W2tyARX1qjQgdYklpv4iHrlZPkZllwbCYUc92hZcPGMdwPB+m Z/hQR8J5KuRJekAFvWrchs9YfNAJgG+bAUAMVfyjDbK79lqyCWCbsI7N3x2w8rKGIfMtoeuxn rzZaH9/xYCKcbIo0XpwS79vl1rA6XveR66LkWHpJC2d5dCrH9T8txpwDfbGUW/qR9Myl0yWVp lU1vS6FptGvMI5Otmc5UOsl31KsulADAP5/8FZKxXnTNPPQ52uzAgRMy/GZTcsczJXq4n7E4J 6F75TpL1CdHEhrOEocp98J3t45OvD5D5zF3wLiBK+5opDXYxF+c94sNe5gM= X-Rspamd-Queue-Id: 3100A867B8 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.984,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 19:17:22 -0000 On Sun, 21 Apr 2019 12:04:07 +0700, Victor Sudakov wrote: > Polytropon 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. > > In better times, I used to have an XF86Config describing everything I > needed, even modelines. In fact, now I have zero X configs. Do you mean > I should create an incomplete config with only those tidbits you > provided? With xorg.conf.d, you can use one partial configuration file per item that you need to configure deviating from the auto- detection magic. In /usr/local/etc/X11/xorg.conf.d/, you can have multiple files with names of your choice. For example, /usr/local/etc/X11/xorg.conf.d/no_aiglx.conf could be the filename for the snippet shown above. In the past, I preferred to have a /etc/X11/Xorg.conf with all global settings in it, such as supported and switchable (!) screen sizes, keyboard language, or non-standard fonts. Today, you can still configure parts of X, and you don't need to have a complete ("valid") xorg.conf file. For example, I have /usr/local/etc/X11/xorg.conf.d/keyboard-de.conf which just contains this: Section "InputClass" Identifier "KeyboardDefaults" Driver "keyboard" MatchIsKeyboard "on" Option "XkbLayout" "de" EndSectio This makes sure I get a german keyboard independent from any window manager or desktop I use (unless the desktop environment thinks it's okay to override a priority setting, in which case I'll get very angry). In order to load a few additional modules, I also have a file /usr/local/etc/X11/xorg.conf.d/modules.conf: Section "Module" Load "fb" Load "vgahw" EndSection But the worst thing is /usr/local/etc/X11/xorg.conf.d/screen-resolution.conf which I need to switch screen size depending on using the laptop's LCD, a CRT, or a VGA->video converter: Section "Screen" Identifier "Screen0" Device "Card0" SubSection "Display" # Modes "1280x800" # LCD R500 Modes "1024x768" # CRT R61i # Modes "640x480" # CRT R61i + video link EndSubSection EndSection Even though I could get a bigger screen size, I cannot get more than 800px vertical, so I decided to stop worrying and love the CRT. ;-) Even though the CRT is capable of much higher resolutions, and even if I attach a LCD capable of 1280x1024, there is no way I can force X to support those modes. Sadly, just using Ctrl+Alt+[+]/[-] to switch through a set of resolutions doesn't seem to be possible anymore... :-( > > And if you're using MATE, you're probably also using the dreaded > > combination of HAL and Dbus, things long forgotten in Linux land, > > By the way, if the alternative to the dreaded combination of hald and > dbus on Linux is the dreaded systemd, I don't really know which is worse. Yes, it's hard to tell which one is worse. However, systemd is currently in a maintained state (actively developed, taking over many components of basic system startup and operations), but HAL and DBus have been abandoned years ago, they only seem to exist as legacy components. Don't ask me where the *Kit stuff (PolicyKit, ConsoleKit, etc.) fit into this mess, I have to admit that I never even tried to understand this on Linux. > But, once it comes to that, if I wanted to run an X desktop on a FreeBSD > system, like a modern fashionable guy, what alternatives do I have that > would not require the dreaded HAL and Dbus? You would need to compile the applications yourself, switching off HAL and DBus support. I'm currently writing this on a system that neither has nor runs HAL or DBUs, without their absence causing any problems. :-) > If I could find a way to run two independent sessions within one X > server, I would do that. This has been part of Gnome 2, and, if I remember correctly, at least _has_ been working on MATE. On a system I once upgraded, Gnome 2 became replaced with unusable Gnome 3, so I installed MATE instead (leaving the remains of Gnome 2 and 3 on the disk), and on the MATE desktop, there was the "Session switcher" still available. In the german version, it was called "Benutzer wechseln" (change user). I also replaced gdm by slim, so that probably is not a required part. I wonder if MATE supports (supported?) it natively, or if it really is just about what Gnome left behind... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...