Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Qingy GUI not working, falling back to text with no errors
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
Kimitsune
n00b
n00b


Joined: 26 May 2018
Posts: 2

PostPosted: Sun May 27, 2018 6:22 pm    Post subject: Qingy GUI not working, falling back to text with no errors Reply with quote

Hi,
I'm new to gentoo and have been using it only for about four months. I learnt quite a bit about GNU/Linux as a result :p .
As a beginner I tried on my first install to write a custom linuxrc for my custom initramfs, and it worked. I love gentoo so much !
I'll probably post all of my scripts on the forum once they are polished enough, in hope they'll be useful to someone.
I managed to fix most of the problems I encountered, until now, so here I am :) .

I tried to install Qingy because typing my zsh macro built around "startx" was getting old quickly, but Qingy DirectFB GUI never shows up.
There are no error messages in Syslog, Qingy just fallback to text mode. Qingy still print status to Syslog, so I know logging works.

Furthermore, in text mode, even after I symlinked ~/.Xsession to my ~/.Xinitrc (which contains "exec ck-launch-session startkde"), console kit do not start when using Qingy.
But this is another problem, probably fixed by setting qingy to launch X in an unused TTY instead of the current one (I remember reading that somewhere on the forum).

If the GPU driver matters : I'm using intel integrated graphics from an Intel P8700, so I915 kernel driver is used if I'm not mistaken.

So, here are the USEs :
Quote:
dev-libs/DirectFB-1.7.6-r1::gentoo USE="alsa drmkms dynload fbcon gif gstreamer jpeg mad mng opengl png tiff truetype vorbis zlib -X -bmp -cddb -debug -divine -doc -egl -fusiondale -fusionsound -gles2 -imlib2 -input_hub -jpeg2k -mpeg2 -mpeg3 -multicore -oss -pnm -sawman -sdl -static-libs (-swfdec) -timidity -tremor -v4l -vdpau -webp -xin"

Quote:
sys-apps/qingy-1.0.0-r4::gentoo USE="X consolekit crypt gpm opensslcrypt pam -emacs -static"


I'm using consolekit + polkit on X11. The DE is kde.

Inittab:
Code:

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


Qingy configuration file :
Code:
# Directory containing X sessions
x_sessions = "/etc/X11/Sessions/"
# Directory containing text mode sessions
text_sessions = "/etc/qingy/sessions/"
# Directory where qingy should put its temporary files
temp_files_dir = "/var/lib/misc"

# Full path to the X server
# x_server = "/usr/X11R6/bin/XFree86"
# Full path to the 'xinit' executable
xinit = "/usr/bin/xinit"

# Parameter we should pass to the X server
x_args = "-nolisten tcp -br"

# How verbose should qingy be?
# Possible values are debug, error
# Default value is error
log_level = debug

# Where should qingy messages be logged?
# Values can be one or more of the following:
# console, file, syslog
# Default value is console
# log_facilities = console, file
#log_facilities = console, file, syslog
log_facilities = syslog

# Offset to search for an available X server number.
# This number affects the DISPLAY env variable.
# Default is 1, setting it to 0 will make buggy OpenGL implementations
# (like the ATI one) work with qingy, but it will also make it impossible
# to start an X server from console using startx without passing it
# extra parameters.
#x_server_offset = 1

# Where should we start the X server?
# Accepted values are:
#   qingy_tty (default) to start it in the same tty qingy is running in
#   unused_tty to start it into an unused tty
x_server_tty = qingy_tty

# Scripts that should be executed just before/after qingy GUI is fired up/shut down
pre_gui_script  = "/etc/qingy/pre_GUI.sh"
post_gui_script = "/etc/qingy/post_GUI.sh"

# Where are the screen savers?
screensavers_dir = "/usr/lib64/qingy/screensavers"

# How much should we wait (in minutes) before the screen saver is fired up?
# A value of 0 disables screensaver completely.
screensaver_timeout = 5

# How much should we wait (in minutes) before the screen enters power saving mode?
# A value of 0 disables the feature
screen_powersaving_timeout = 30

#screensaver "pixel"
screensaver "running_time"#="%H:%S:%M"

# Where are the themes?
themes_dir = "/usr/share/qingy/themes"

# What theme do you want (you can also specify 'random')
# theme = random
theme = "default"

# Who is allowed to shut down the system?
# Allowed options are 'everyone', 'root', 'noone'
# default policy is everyone
# shutdown_policy = everyone

# How should latest user be calculated?
# global means get latest user that logged in using qingy from whichever tty
# tty    means get latest user that logged in using current tty
# none   means do not get (and set) latest user
# default policy is global
#last_user_policy = global

# How should latest user session be calculated?
# user means get last session of each user
# tty  means get last session of current tty
# none means do not get (and set) latest session
# default policy is user
#last_session_policy = user

# What happens when we press the 'sleep' button?
#sleep = "/usr/local/sbin/hibernate"

# whether we should clear background image during dialogs (default is no)...
# this is the default setting, it gets overridden if the theme you are using
# sets the same setting differently...
# clear_background = yes

# whether to allow session locking; if you enable this, when you try to
# switch to a qingy-controlled tty whose owner is not your current
# user, you will be asked for the password of that user before being
# allowed to continue. If you are root, of course, you can switch
# to any tty you chose to. Default setting is 'no'.
lock_sessions = yes

# whether to allow session timeout; if you enable this, after the amount
# of minutes specified in idle_timeout variable, idle_action will be
# performed. Allowed actions are:
# lock     will lock user session asking you for your password
# logout   will close your session
idle_timeout = 30
idle_action  = lock

# prevent qingy from logging in user or firing up its GUI if system
# is restarting / shutting down
#check_runlevel = yes
#exclude_runlevels = 0, 6

# these options are valid only if qingy is started from tty3
#tty = 3
#{
#       theme = "fireplace"
#       screensaver "pixel"

#       # Should we auto log in?
#       # Totally insecure, but very convenient ;-)
#       # Note that this section must be put inside a tty=n{} block
#       autologin
#       {
#               username = "myuser"
#               # You can also use 'session=lastsession' to automatically choose last user session
#               session  = "Text: emacs"
#               # if set to 'no', qingy will autologin only once every system restart
#               relogin  = no
#       }
#}

keybindings
{
        prev_tty    = "win"      # switch to left tty
        next_tty    = "menu"     # switch to right tty
        poweroff    = "ALT-p"    # shutdown your system
        reboot      = "ALT-r"    # restart your system
        screensaver = "ALT-s"    # activate screen saver
        sleep       = "ALT-z"    # put machine to sleep
#       kill        = "CTRL-c"   # kill qingy
        text_mode   = "CTRL-ESC" # Revert to text mode
}


And finally the only messages printed by qingy to syslog : (Captured by KSystemLog)
Quote:

qingy(tty1)[9882] You chose a screen saver timeout of 5 minutes.
qingy(tty1)[9882] You chose a screen power management timeout of 30 minutes.
qingy(tty1)[9882] added keybinding: 'win' will switch to left tty...
qingy(tty1)[9882] added keybinding: 'menu' will switch to right tty...
qingy(tty1)[9882] added keybinding: 'ALT-p' will poweroff machine...
qingy(tty1)[9882] added keybinding: 'ALT-r' will reboot machine...
qingy(tty1)[9882] added keybinding: 'ALT-s' will activate screen saver...
qingy(tty1)[9882] added keybinding: 'ALT-z' will put machine to sleep...
qingy(tty1)[9882] added keybinding: 'CTRL-ESC' will revert to text mode...
qingy(tty1)[9882] The following logging facilities will be used: SYSLOG
qingy(tty1)[9882] Session locking is enabled.

What is happening here ?

I did search the forums and internet for a solution (My directFB USEs are copy-pasted from another thread) but nothing worked, and also it seems Qingy is not really widely used.
Thanks for your help !
Back to top
View user's profile Send private message
CitizenKepler
n00b
n00b


Joined: 20 Jul 2012
Posts: 3
Location: Houston, TX

PostPosted: Tue Nov 06, 2018 12:00 am    Post subject: Reply with quote

I have also had this issue on two think pads (different models). In my logs it never trys to initiate DirectFB, like I see in your log files.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum