I'm recommending [[Uvesafb]] but if you have some graphical issues with it use vesafb. Qingy may not work with [[KMS]].

I'm recommending [[Uvesafb]] but if you have some graphical issues with it use vesafb. Qingy may not work with [[KMS]].

−

[[Install]] the {{AUR|qingy}} package. Several extra themes are available in the {{AUR|qingy-themes}} package. {{AUR|qingy-theme-arch}} is an Arch specific theme.

+

[[Install]] the {{AUR|qingy}}{{Broken package link|{{aur-mirror|qingy}}}} package. Several extra themes are available in the {{AUR|qingy-themes}}{{Broken package link|{{aur-mirror|qingy-themes}}}} package. {{AUR|qingy-theme-arch}}{{Broken package link|{{aur-mirror|qingy-theme-arch}}}} is an Arch specific theme.

==Replace *getty with qingy==

==Replace *getty with qingy==

Revision as of 10:41, 20 August 2015

Qingy is a replacement for Getty and login-managers like slim, kdm gdm and so on, using DirectFB to provide a fast, nice GUI without the overhead of the X Window System. It allows users to log in and start the session of their choice (text console, gnome, kde, wmaker, etc.). Running several X sessions is also possible.

Replace *getty with qingy

Simply enable qingy@.service on the tty that you want it on and remove getty from that tty:

# systemctl enable qingy@ttyX
# systemctl disable getty@ttyX

where X is the tty you want qingy to be on. Do this as many times as needed.

Also, you need to mask the getty service with:

# systemctl mask getty@ttyX

for each of the ttys you enabled qingy on.

You may additionaly have to tweak/disable the autovt@.service. The latter spawns getty's on-the-fly when switching virtual-consoles and may interfere with an already spawned qingy. To disable automatic spawning of getty's altogether, modify /etc/systemd/logind.conf:

NAutoVTs=0

Configuring qingy

You can configure qingy by editing /etc/qingy/settings.

The default settings for X are fine so only edit them if you really know what you are doing.

Starting X

Please do note that .xinitrc is different from .xsession. The default login script, .xinitrc, works with startx, but graphical login managers generally do not look for .xinitrc. Instead, they look for a file named .xsession in your home directory.

If you want to start X with qingy you need to edit your .xsession.

Here a default .xsession for qingy.

#!/bin/sh
exec <login-shell command> <window manager starter>

An example:

#!/bin/sh
exec bash --login -c 'openbox-session'

The start of the window manager using a login shell is needed because qingy starts the X-session directly without the help of a shell. This causes issues like no umlauts in xterm and malfunction of control keys like "Home", "End", "Del" and so on in the terminal.