An awesome app called Qingy (Part 1)

[s4t4n]

If I however delete /var/log/directfb.log, and run qingy (which then should run DirectFB which should create the logfile again), the log file is not created.

Right before qingy reverts to text mode I get the following

Code: Select all

TERM environment variable not set

This is also what I get when switching between the tty's.

I am using DirectFB 0.9.24 and qingy 0.9.1.

Does anyone have an idea of what might be wrong?

qingy disables debug logs (even those of DirectFB) if you don't enable them in its config file, where you should put the following:

Code: Select all

log_level = debug
log_facilities = console, file

Your logs will then be available in /var/log/qingy.log (DirectFB logs are also here).

[babrodtk]

Thanks for your swift reply s4t4n:)

qingy disables debug logs (even those of DirectFB) if you don't enable them in its config file, where you should put the following:

Code: Select all

log_level = debug
log_facilities = console, file 

I log to syslog, and it does not show any errors. I tried what you recommended. And get the following from cat /var/log/qingy.log (which is the same as I get from cat /var/log/syslog | grep qingy | tail -n 50)

Code: Select all

Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'win' will switch to left tty...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'menu' will switch to right tty...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Aug 30 11:48:50, qingy on tty1 [DEBUG] The following logging facilities will be used: FILE SYSLOG
Aug 30 11:48:50, qingy on tty1 [DEBUG] Session lockiing is NOT enabled.
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'win' will switch to left tty...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'menu' will switch to right tty...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Aug 30 11:48:50, qingy on tty1 [DEBUG] The following logging facilities will be used: FILE SYSLOG
Aug 30 11:48:50, qingy on tty1 [DEBUG] Session lockiing is NOT enabled.
Aug 30 11:48:50, qingy on tty1 [DEBUG] Native theme resolution is '800x600'
Aug 30 11:48:50, qingy on tty1 [DEBUG] Framebuffer resolution is '1400x1050'
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'win' will switch to left tty...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'menu' will switch to right tty...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Aug 30 11:48:50, qingy on tty1 [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...

And have the following in /etc/inittab

Code: Select all

c1:12345:respawn:/sbin/qingy tty1
c2:12345:respawn:/sbin/qingy tty2
c3:12345:respawn:/sbin/qingy tty3
c4:12345:respawn:/sbin/qingy tty4
c5:12345:respawn:/sbin/qingy tty5
c6:12345:respawn:/sbin/agetty 38400 tty6 linux

Running qingy-DirectFB gives me the same output (run from commandline), and still without any framebuffer. I have emerged qingy after I emerged DirectFB as well. Any clue as to what makes qingy not use the framebuffer?

[elKano]

Hello,
I have a small problem with qingy (I have had it for several versions, as far as I remember).

The problem is, it does not seem to load the path from '/etc/profile.env'. When I log in using getty, I have this path:

Code: Select all

% print $PATH
/bin:/usr/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.4.6:/opt/ati/bin:/opt/sun-jre-bin-1.5.0.06/bin:/opt/sun-jre-bin-1.5.0.06/javaws:/usr/kde/3.5/bin:/usr/qt/3/bin:/usr/kde/3.4/bin:/usr/games/bin:/home/elkano/bin

However, when I use qingy, I have this other path:

Code: Select all

% print $PATH
/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/usr/bin/:/home/elkano/bin

Any hints?

[s4t4n]

Hello,
I have a small problem with qingy (I have had it for several versions, as far as I remember).

The problem is, it does not seem to load the path from '/etc/profile.env'. When I log in using getty, I have this path:

Code: Select all

% print $PATH
/bin:/usr/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.4.6:/opt/ati/bin:/opt/sun-jre-bin-1.5.0.06/bin:/opt/sun-jre-bin-1.5.0.06/javaws:/usr/kde/3.5/bin:/usr/qt/3/bin:/usr/kde/3.4/bin:/usr/games/bin:/home/elkano/bin

However, when I use qingy, I have this other path:

Code: Select all

% print $PATH
/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/usr/bin/:/home/elkano/bin

Any hints?

Are you using PAM for authentication? If not, PATH settings are hardcoded into qingy, it won't parse /etc/profile.env... I can make it do so, btw.

[elKano]

Are you using PAM for authentication? If not, PATH settings are hardcoded into qingy, it won't parse /etc/profile.env... I can make it do so, btw.

I know I have the pam USE flag activated, and pam emerged, so I suppose I am, although I am not really sure .

[s4t4n]

I don't care that much for licenses:D I'm sure that whoever did that wallpaper, he will agree to use it in gentoo program:] and font isn't that important, I choosed it because it's the only font I know (windows user, I use desktop linux for few weeks)

and I dont want any credit, I just took already created theme, switched wallpaper and asked friend to create buttons.

Unfortunately, we cannot publish / make available items those license we cannot be sure of... The arial font, for example, afaik can only be used on a machine with a valid MS windows license...

I made some minor modifications to the theme, including a font change, so the lic. issues should be fixed now. Expect the Gentoo theme to be installed and activated by default in next qingy version/revision

[Vync3]

I'm having trouble getting Qingy to work. When I switch to a tty that uses qingy it changes resolution and the mouse pointer shows for a fraction of a second then qingy exits. Here is the error log:

Code: Select all

Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'win' will switch to left tty...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'menu' will switch to right tty...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Sep 10 14:35:22, qingy on tty5, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Sep 10 14:35:22, qingy on tty5, [DEBUG] Session locking is NOT enabled.
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Config: Parsing config file '/etc/directfbrc'.
Sep 10 14:35:24, qingy on tty5, [DEBUG]        ---------------------- DirectFB v0.9.24 ---------------------
Sep 10 14:35:24, qingy on tty5, [DEBUG]              (c) 2000-2002  convergence integrated media GmbH  
Sep 10 14:35:24, qingy on tty5, [DEBUG]              (c) 2002-2004  convergence GmbH                   
Sep 10 14:35:24, qingy on tty5, [DEBUG]         -----------------------------------------------------------
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Core: Single Application Core. (2006-09-09 06:20) 
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) Direct/Memcpy: Using SSE optimized memcpy()
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 5917)...
Sep 10 14:35:24, qingy on tty5, [DEBUG]  (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Genefx: MMX detected and enabled
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence integrated media GmbH)
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
Sep 10 14:35:24, qingy on tty5, [ERROR] Unrecoverable DirectFB error: reverting to text mode!
Sep 10 14:35:24, qingy on tty5, [ERROR] This usually means that you have an issue with DirectFB, not with qingy...
Sep 10 14:35:24, qingy on tty5, [ERROR] Most likely you don't have your console framebuffer properly set up.
Sep 10 14:35:24, qingy on tty5, [ERROR] Please turn on DEBUG log level in qingy to see exactly why DirectFB is letting you down.
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) DirectFB/Config: Parsing config file '/etc/directfbrc'.
Sep 10 14:35:26, qingy on tty5, [DEBUG]        ---------------------- DirectFB v0.9.24 ---------------------
Sep 10 14:35:26, qingy on tty5, [DEBUG]              (c) 2000-2002  convergence integrated media GmbH  
Sep 10 14:35:26, qingy on tty5, [DEBUG]              (c) 2002-2004  convergence GmbH                   
Sep 10 14:35:26, qingy on tty5, [DEBUG]         -----------------------------------------------------------
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) DirectFB/Core: Single Application Core. (2006-09-09 06:20) 
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) Direct/Memcpy: Using SSE optimized memcpy()
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 5917)...
Sep 10 14:35:26, qingy on tty5, [DEBUG]  (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) DirectFB/Genefx: MMX detected and enabled
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence integrated media GmbH)
Sep 10 14:35:26, qingy on tty5, [DEBUG] (*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
Sep 10 14:35:26, qingy on tty5, [DEBUG] Unrecoverable DirectFB error: reverting to text mode!
Sep 10 14:35:26, qingy on tty5, [DEBUG] This usually means that you have an issue with DirectFB, not with qingy...
Sep 10 14:35:26, qingy on tty5, [DEBUG] Most likely you don't have your console framebuffer properly set up.
Sep 10 14:35:26, qingy on tty5, [DEBUG] Please turn on DEBUG log level in qingy to see exactly why DirectFB is letting you down.

Here is the output of dfbinfo:

Code: Select all

(*) DirectFB/Config: Parsing config file '/etc/directfbrc'.

       ---------------------- DirectFB v0.9.24 ---------------------
             (c) 2000-2002  convergence integrated media GmbH  
             (c) 2002-2004  convergence GmbH                   
        -----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2006-09-09 06:20) 
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 5961)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 5962)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence integrated media GmbH)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)


Screen (00) FBDev Primary Screen            (primary screen)
   Caps: VSYNC POWER_MANAGEMENT 

     Layer (00) FBDev Primary Layer             (primary layer)
        Type:    GRAPHICS 
        Caps:    SURFACE BRIGHTNESS CONTRAST SATURATION 


Input (00) Keyboard                        (primary keyboard)
   Type: KEYBOARD 
   Caps: KEYS

Here is the contents of my fb.modes file:

Code: Select all

mode "1024x768-60"
    # D: 64.033 MHz, H: 47.714 kHz, V: 60.018 Hz
    geometry 1024 768 1024 1536 24
    timings 15617 159 52 23 1 107 3
    vsync high
    rgba 8/16,8/8,8/0,0/0
endmode

and my directfbrc file:

Code: Select all

mode=1024x768-60
depth=24

I'm using vesafb-tng built into the kernel. There are no other frame buffer drivers built in. I get a high resolution console, so the frame buffer appears to be working. Here is my kernel command line:

Code: Select all

kernel /boot/kernel-2.6.17-gentoo-r7 root=/dev/hda5 video=vesafb:mtrr:3,ywrap,1024x768-32@60

Links works fine with the frame buffer:

Code: Select all

links -g -driver directfb http://www.gentoo.org/

I have an ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) which uses the Mach64 chipset built into my laptop.

Qingy looks very cool and I'd like to get it working. Any ideas on what I could try would be helpful. Let me know if you need any other info.

Thanks

[s4t4n]

I'm having trouble getting Qingy to work. When I switch to a tty that uses qingy it changes resolution and the mouse pointer shows for a fraction of a second then qingy exits. Here is the error log:

Code: Select all

Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'win' will switch to left tty...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'menu' will switch to right tty...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Sep 10 14:35:22, qingy on tty5, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Sep 10 14:35:22, qingy on tty5, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Sep 10 14:35:22, qingy on tty5, [DEBUG] Session locking is NOT enabled.
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Config: Parsing config file '/etc/directfbrc'.
Sep 10 14:35:24, qingy on tty5, [DEBUG]        ---------------------- DirectFB v0.9.24 ---------------------
Sep 10 14:35:24, qingy on tty5, [DEBUG]              (c) 2000-2002  convergence integrated media GmbH  
Sep 10 14:35:24, qingy on tty5, [DEBUG]              (c) 2002-2004  convergence GmbH                   
Sep 10 14:35:24, qingy on tty5, [DEBUG]         -----------------------------------------------------------
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Core: Single Application Core. (2006-09-09 06:20) 
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) Direct/Memcpy: Using SSE optimized memcpy()
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 5917)...
Sep 10 14:35:24, qingy on tty5, [DEBUG]  (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Genefx: MMX detected and enabled
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence integrated media GmbH)
Sep 10 14:35:24, qingy on tty5, [DEBUG] (*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
Sep 10 14:35:24, qingy on tty5, [ERROR] Unrecoverable DirectFB error: reverting to text mode!
Sep 10 14:35:24, qingy on tty5, [ERROR] This usually means that you have an issue with DirectFB, not with qingy...
Sep 10 14:35:24, qingy on tty5, [ERROR] Most likely you don't have your console framebuffer properly set up.
Sep 10 14:35:24, qingy on tty5, [ERROR] Please turn on DEBUG log level in qingy to see exactly why DirectFB is letting you down.

Make sure you compiled DirectFB with the following USE flags enabled: fbcon jpeg png truetype as qingy themes require those capabilities...

[Vync3]

Thanks. It's working now. I didn't have DirectFB compiled with the truetype useflag - I don't think I saw that mentioned anywhere else. Now I've just got to get my Synaptics touchpad working.

[Spruit_elf]

Thanks. It's working now. I didn't have DirectFB compiled with the truetype useflag - I don't think I saw that mentioned anywhere else. Now I've just got to get my Synaptics touchpad working.

yeah same here synaptics stoppen working for me some version ago i always thought i fucked something up but after a fresh install it still didnt work

and enlightenment gives me some problems since they insisted on starting e17 with enlightenmwnt_start instead of enlightenment-0.17

does someone has a solution for that?

[dmvianna]

The new qingy came with strange settings. After upgrading, it wouldn't let me start neither X nor a console terminal. I found the way to get X working changing the default variables in /etc/qingy/settings to

Code: Select all

# Full path to the X server
x_server = "/usr/X11R6/bin/X"

as it was originally pointing to xfree86. But I still did not find the way to fix my console situation. Any hints?

[s4t4n]

The new qingy came with strange settings. After upgrading, it wouldn't let me start neither X nor a console terminal. I found the way to get X working changing the default variables in /etc/qingy/settings to

Code: Select all

# Full path to the X server
x_server = "/usr/X11R6/bin/X"

as it was originally pointing to xfree86. But I still did not find the way to fix my console situation. Any hints?

It was pointing to xfree86 but the line was probably commented by default. qingy tries to detect where the X server is, but does not necessarily get it right: /etc/qingy/settings is there so that users can edit it

As for your console situation, what is the problem exactly?

[dmvianna]

As for your console situation, what is the problem exactly?

Does not log in reliably. It tries to start X, or to open a console, but fails and returns to the qingy login screen. I'm using VESA-TNG and ATI-drivers for Xorg. I tried setting x_server_offset = 0, and it made my computer login after a number of tries, but it fails most of the time.

[s4t4n]

As for your console situation, what is the problem exactly?

Does not log in reliably. It tries to start X, or to open a console, but fails and returns to the qingy login screen. I'm using VESA-TNG and ATI-drivers for Xorg. I tried setting x_server_offset = 0, and it made my computer login after a number of tries, but it fails most of the time.

Strange issue.

So: qingy works nicely, even its GUI, but you have problems starting sessions with it...

- Does a pure Text: Console session work for you?
- You have problems starting X sessions only or also text sessions do not work?
- What is your login shell (bash, zsh, ...)?
- The X session fails completely to start, or dies after a short time?

[dmvianna]

So: qingy works nicely, even its GUI, but you have problems starting sessions with it...

- Does a pure Text: Console session work for you?

Agetty works.

- You have problems starting X sessions only or also text sessions do not work?

Qingy blanks the screen for some time then comes back, both X and text (console). Sometimes crashes, and I can't swich VT or recover the system.

- What is your login shell (bash, zsh, ...)?

Bash.

- The X session fails completely to start, or dies after a short time?

Fails. Works from time to time, like once after 10 tries, or not at all. I'm using 2.6.19-r3, and that appeared after I emerged a new version of qingy (0.9.4).

[s4t4n]

Agetty works.

Agreed. qingy and getty are very different

Qingy blanks the screen for some time then comes back, both X and text (console). Sometimes crashes, and I can't swich VT or recover the system.

OK. Let's try to sort out your session startup issues first, and qingy GUI problems later. Can you please tell qingy to perform a text-mode only login (by adding the -t command line arg to qingy in /etc/inittab, see 'qingy -h' for all possible arguments)? Do you still have issues in starting your session of choice? If so, you might try to temporarily add /bin and /usr/bin to your PATH in $HOME/.bashrc and see if that solves your issue. If it does, it is a known bug and will be fixed very shortly...

[dmvianna]

My /etc/inittab:

Code: Select all

# TERMINALS
c1:12345:respawn:/sbin/qingy -t tty1
#c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:2345:respawn:/sbin/qingy -t tty2
#c2:2345:respawn:/sbin/agetty 38400 tty2 linux
c3:2345:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux

Killing qingy didn't make it restart in textmode, so I rebooted. It went on a loop, giving the output of qingy -h and restarting each 15 s. I'm not sure how to include PATH in .bashrc, so for now I went back to 0.7.4, and it works perfectly.

[s4t4n]

My /etc/inittab:

Code: Select all

# TERMINALS
c1:12345:respawn:/sbin/qingy -t tty1
#c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:2345:respawn:/sbin/qingy -t tty2
#c2:2345:respawn:/sbin/agetty 38400 tty2 linux
c3:2345:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux

Killing qingy didn't make it restart in textmode, so I rebooted. It went on a loop, giving the output of qingy -h and restarting each 15 s. I'm not sure how to include PATH in .bashrc, so for now I went back to 0.7.4, and it works perfectly.

You didn't read the output of 'qingy -h' correctly: you must use
c1respawn:/sbin/qingy tty1 -t
and NOT
c1respawn:/sbin/qingy -t tty1

As for your .bashrc, just open (or create) that file in your home directory and a line something like
export PATH="/usr/bin:/bin:${PATH}"
into it...

Regarding qingy 0.7.4, it will be removed soon But, if you say that that version works for you, then probably qingy 0.9.5 will solve your issues...

[dmvianna]

Forget it. I updated qingy after an emerge -e world, hence, I did not read the warning telling me to run qingy-keygen... Now 0.9.4 runs perfectly.

[s4t4n]

Forget it. I updated qingy after an emerge -e world, hence, I did not read the warning telling me to run qingy-keygen... Now 0.9.4 runs perfectly.

The best problems are those that solve themselves

[dmvianna]

Still unstable. Either I have to log in three times for X to finally boot, or it hangs with a blinking cursor in a blank screen, and I have to switch to agetty and log in there. I'll wait for the next version, and will log in agetty during the wait, so I can check for anything you ask in case you want to.

One thing I've noticed, is that after logging in either in qingy or agetty, it starts working fine, so each time I do something I can't really test if it's OK until the next reboot.

[s4t4n]

Still unstable. Either I have to log in three times for X to finally boot, or it hangs with a blinking cursor in a blank screen, and I have to switch to agetty and log in there. I'll wait for the next version, and will log in agetty during the wait, so I can check for anything you ask in case you want to.

One thing I've noticed, is that after logging in either in qingy or agetty, it starts working fine, so each time I do something I can't really test if it's OK until the next reboot.

Well, this is strange, if it works, it should do this consistently...
You can try this: enable DEBUG logging in qingy and start an X session, in the logs should appear the arguments qingy is passing to xinit in order to start your session. Close your session. You could then (try to) start xinit in a shell, passing it the same arguments that are in the logs. If it fails, some message should appear stating what is wrong.

At first glance, it would appear that PAM is failing to set some environment variables at the first run, but gets it right later on...

[dmvianna]

I'll try that in the next reboot (tomorrow), thanks. I forgot to tell something (because those things don't happen exactly the same every time). It happened today again, as it did once or twice before. I try to log in, and it fails once or twice to load fluxbox. Then I got to start ratpoison. Then I logged out and tried fluxbox again. It started X, and I was locked on the gray background with the X cursor (I don't have twm), unable to switch VTs and unable to kill it. /var/log/Xorg.0.log does not mention any errors.

[NeddySeagoon]

Split and locked due to size.

Continued here