[http://qingy.sourceforge.net/ Qingy] is a replacement for [[Getty]] and login-managers like slim, kdm gdm and so on, using [http://www.directfb.org 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.

−

{{i18n_links_end}}

+

−

[[Category:Boot process (English)]]

+

−

[[Category:Display managers (English)]]

+

−

[[Category:Eye candy (English)]]

+

−

[[Category:HOWTOs (English)]]

+

−

+

−

==What is qingy?==

+

−

+

−

[http://qingy.sourceforge.net/ Qingy] is a replacement for getty and login-managers like slim, kdm gdm and so on, using [http://www.directfb.org 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.

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 qingy service with:

+

# systemctl mask getty@ttyX

+

for each of the ttys you enabled qingy on.

+

+

===Initscripts===

To use qingy, you'll need to edit /etc/inittab.

To use qingy, you'll need to edit /etc/inittab.

Replace:

Replace:

−

c1:2345:respawn:/sbin/agetty -8 38400 vc/1 linux

+

c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux

−

c2:2345:respawn:/sbin/agetty -8 38400 vc/2 linux

+

c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux

−

c3:2345:respawn:/sbin/agetty -8 38400 vc/3 linux

+

c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux

−

c4:2345:respawn:/sbin/agetty -8 38400 vc/4 linux

+

c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux

−

c5:2345:respawn:/sbin/agetty -8 38400 vc/5 linux

+

c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux

−

c6:2345:respawn:/sbin/agetty -8 38400 vc/6 linux

+

c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux

−

by:

+

with:

c1:2345:respawn:/sbin/qingy tty1

c1:2345:respawn:/sbin/qingy tty1

c2:2345:respawn:/sbin/qingy tty2

c2:2345:respawn:/sbin/qingy tty2

Line 48:

Line 49:

Qingy's author suggest to keep agetty on a console (here on console 6) as a safety measure as qingy is still beta software.

Qingy's author suggest to keep agetty on a console (here on console 6) as a safety measure as qingy is still beta software.

−

Because qingy uses tty0-9 insead of vc/1-6 so you need add tty to /etc/securetty :

+

−

#

+

−

# /etc/securetty

+

−

#

+

−

console

+

−

vc/1

+

−

vc/2

+

−

vc/3

+

−

vc/4

+

−

vc/5

+

−

vc/6

+

−

tty0

+

−

tty1

+

−

tty2

+

−

tty3

+

−

tty4

+

−

tty5

+

−

tty6

+

−

tty7

+

==Configuring qingy==

==Configuring qingy==

Line 72:

Line 55:

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

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

−

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

+

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

# Full path to the X server

# Full path to the X server

#x_server = "/usr/bin/Xorg"

#x_server = "/usr/bin/Xorg"

Line 85:

Line 68:

All other options are well explained.

All other options are well explained.

+

+

You may need to set the path to the X server e.g.

+

# Full path to the X server

+

x_server = "/usr/bin/X"

==Starting X==

==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.

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

Line 97:

Line 86:

exec bash --login -c 'openbox-session'

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.

+

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.

−

This causes issues like no umlauts in xterm and malfunction of control keys like "Home", "End", "Del" and so on in the terminal.

+

+

For more details, visit the Ubuntu CustomXSession wiki at [https://wiki.ubuntu.com/CustomXSession]

+

+

If you want your X sessions to be started in an active state, you may need to add the following lines to the end of /etc/pam.d/qingy.

If you've changed the variable x_sessions or text_session in the config file of qingy replace the following pathes with the path you've set.

+

If you've changed the variable x_sessions or text_session in the config file of qingy replace the following paths with the path you've set.

===Text mode session===

===Text mode session===

−

Therefore add a new file into /etc/qingy/sessions/ while the name of the file is the name of the entry.

+

Create a file /etc/qingy/sessions/<sessionname>.

+

+

The file name is shown as entry in the session list.

−

The file should be a shell script for an example have a look into /etc/qingy/sessios/emacs.

+

The file should be a shell script. For an example have a look into /etc/qingy/sessions/emacs.

===X mode session===

===X mode session===

−

Create the folder /etc/X11/Sessions/ and save a new script file into it.

+

Create the folder /etc/X11/Sessions/ and save a new script file into it. (see Text mode session)

−

The name of the file is shown in the menu.

+

The name of the file is shown in the session list.

==Troubleshooting==

==Troubleshooting==

Line 120:

Line 118:

=== Synaptic touchpad and keyboard issue ===

=== Synaptic touchpad and keyboard issue ===

−

Qingy (and quite possibly other DirectFB applicationss) has some issues using Synaptics touchpad. Also the keyboard can behave strangely (like if each keys were pressed twice).

+

Qingy (and quite possibly other DirectFB applications) has some issues using Synaptics touchpad. Also the keyboard can behave strangely (like if each keys were pressed twice).

This can be solved by adding:

This can be solved by adding:

−

disable-module=linux_input

+

+

*If each keypress was doubled

+

disable-module=keyboard

+

*If mouse acts funny

+

disable-module=ps2mouse

+

disable-module=serialmouse

+

to /etc/directfbrc. If the file does not exist, create it. This will enable you to use your touchpad, however some extra functionality like tapping or tap-dragging might not work.

to /etc/directfbrc. If the file does not exist, create it. This will enable you to use your touchpad, however some extra functionality like tapping or tap-dragging might not work.

+

+

On computers with several pointing devices, such as the Lenovo ThinkPad, it may be necessary to add the line:

+

+

disable-module=linux_input

+

+

to /etc/directfbrc. This should correct both the mouse and keyboard issues.

Revision as of 09:34, 12 April 2013

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.

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.