Previously, I was using qingy-0.6 with no problem. But since I install the 0.7.1, I' ve lots of problems. First of all, my system doesn't start any session anymore. I mean that qingy is launched well, but when I try to login, I only have an empty console where I can't do anything. It does that with all the users. In order to get logged, I have to switch to another console (where qingy isn't running) and login from there. Also, I've remark that when he is started, qingy take all my cpu time. So I must kill it. And what is even more strange is that after that, qingy is respauwn (this is normal) but doesn't take all my cpu time. (But i can't use it to get logged) Info about my system: Portage 2.1_pre4-r1 (default-linux/x86/2005.1, gcc-4.0.2, glibc-2.3.6-r1, 2.6.14-gentoo-r3 i686) ================================================================= System uname: 2.6.14-gentoo-r3 i686 AMD Athlon(tm) XP 2800+ Gentoo Base System version 1.12.0_pre11 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.91.0.4 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.inode.at/ http://mirror.datapipe.net/gentoo http://mirror.datapipe.net/gentoo " LINGUAS="fr fr_FR" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X aac acpi adns alsa apm audiofile avi bitmap-fonts bmp cairo cdr crypt cups curl dbus dga divx4linux dri dvd dvdr eds emboss encode fbcon flac foomaticdb fortran gb gcj gdbm gif gimp gpm gtk gtk2 gtkhtml hal imagemagick imap imlib ipv6 java jikes joystick jpeg kerberos libg++ libwww mad mikmod mmx mp3 mpeg ncurses nls nocd nptl nsplugin nvidia ogg oggvorbis openal opengl oss pdf pdflib perl png python quicktime readline samba scanner sdl sox spell sse ssl szip tcpd tiff truetype truetype-fonts type1-fonts unicode usb videos vorbis win32codecs wmf xml2 xv xvid zlib elibc_glibc kernel_linux linguas_fr linguas_fr_FR userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LANG, LC_ALL, LDFLAGS
May I see the contents of your /etc/inittab and /etc/qingy/settings? Also, does it say something if you start it with --verbose command line arg, then switch to text mode via CTRL-ESC?
/etc/inittab: # # /etc/inittab: This file describes how the INIT process should set up # the system in a certain run-level. # # Author: Miquel van Smoorenburg, <miquels@cistron.nl> # Modified by: Patrick J. Volkerding, <volkerdi@ftp.cdrom.com> # Modified by: Daniel Robbins, <drobbins@gentoo.org> # Modified by: Martin Schlemmer, <azarah@gentoo.org> # # $Header: /var/cvsroot/gentoo-x86/sys-apps/sysvinit/files/inittab,v 1.2 2004/12/22 03:25:20 vapier Exp $ # Default runlevel. id:3:initdefault: # System initialization, mount local filesystems, etc. si::sysinit:/sbin/rc sysinit # Further system initialization, brings up the boot runlevel. rc::bootwait:/sbin/rc boot l0:0:wait:/sbin/rc shutdown l1:S1:wait:/sbin/rc single l2:2:wait:/sbin/rc nonetwork l3:3:wait:/sbin/rc default l4:4:wait:/sbin/rc default l5:5:wait:/sbin/rc default l6:6:wait:/sbin/rc reboot #z6:6:respawn:/sbin/sulogin # TERMINALS c1:12345:respawn:/sbin/qingy tty1 linux #c1:12345:respawn:/sbin/agetty 38400 tty1 linux 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 # SERIAL CONSOLES #s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100 #s1:12345:respawn:/sbin/agetty 9600 ttyS1 vt100 # What to do at the "Three Finger Salute". ca:12345:ctrlaltdel:/sbin/shutdown -r now # Used by /etc/init.d/xdm to control DM startup. # Read the comments in /etc/init.d/xdm for more # info. Do NOT remove, as this will start nothing # extra at boot if /etc/init.d/xdm is not added # to the "default" runlevel. x:a:once:/etc/X11/startDM.sh # End of /etc/inittab =============================================================================== /etc/qingy/settings: # 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" # 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 impossible # to start an X server from console using startx without passing it # extra parameters. #x_server_offset = 1 # 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/lib/qingy/screensavers" #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 # 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 # default policy is user #last_session_policy = user # What happens when we press the 'sleep' button? #sleep = "/usr/local/sbin/hibernate" # wether 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 # wether 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 # How many times should we retry to fire app qingy interface # before reverting to text mode? Default is 0... #retries = 1 # 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 # # Also, if you decide to use this feature, it is better # # that you also make this settings file readable only by root # autologin # { # username = "myuser" # password = "mypassword" # # 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 } =============================================================================== I will try to see the output with --verbose as soon as I have time.
From /etc/inittab: c1:12345:respawn:/sbin/qingy tty1 linux This is wrong. You should correct it as follows: c1:12345:respawn:/sbin/qingy tty1 Also, make sure xdm is not added to runlevel default. From /etc/qingy/settings: pre_gui_script = "/etc/qingy/pre_GUI.sh" #post_gui_script = "/etc/qingy/post_GUI.sh" I notice you decommented pre_gui_script: what did you put in "/etc/qingy/pre_GUI.sh"? I notice there are some word-wrapped lines in /etc/qingy/settings, I assume this is bugzilla behaviour, and your actual file is not word wrapped. Finally, what USE flags did you use when you emerged qingy?
> From /etc/inittab: > c1:12345:respawn:/sbin/qingy tty1 linux > This is wrong. You should correct it as follows: > c1:12345:respawn:/sbin/qingy tty1 done, but it change nothing > Also, make sure xdm is not added to runlevel default. I'm sure of that ;) > From /etc/qingy/settings: > pre_gui_script = "/etc/qingy/pre_GUI.sh" > #post_gui_script = "/etc/qingy/post_GUI.sh" > I notice you decommented pre_gui_script: what did you put in > "/etc/qingy/pre_GUI.sh"? Oups, I made that? Anyway, reverting this change has no effect Also, I had the -v option to qingy, and now I have this message on the console: Warning: Application exited withoud deinitialisation of directfb... I assume the problem comes from that.
Try passing qingy the -t and -v arguments (in /etc/inittab). This will tell it to be verbose, but also to perform a text mode login. This way we can well wether there are problems with qingy authenticating you or with its graphical user interface.
And no, qingy exiting without deallocating DirectFB stuff is a feature, not a bug. This way it shuts down from DirectFB mode much faster (and DirectFB takes care to deinit all the stuff on qingy behalf)...
I've tried to use the text mode ... it works, so the problem seems to be gui related.
Guess so. Does other DirectFB apps (like directvnc) work on your machine?
yes, directfbterm works like a charm. The same is true for the flywithme demo (not in portage, i downloaded that directly from the directfb website). I think that dfbsee is working to, even if I haven't tested that recently. Perhaps will I need to hack the code myself to see what happens?
Any help of this kind is always welcome. Anyway, since you can login with text-mode qingy, would you try recompiling it with crypto_openssl USE flag enabled, and see if it works?
Created attachment 82313 [details] Fixed ebuild(at least for me)
Created attachment 82314 [details, diff] solve the problem This patch fix the problem for me. I also see that version 7.3 was out, I will try to see if this patch is also required or not (as 1st sight seems that yes, but...)
Interesting, you are the first user ever with a similar issue... and yes, 0.7.3 will have to be patched as well as that code section didn't change. I'm going to test your fix and merge it upstream...
Added new revision to Portage with a patch (similar to your own) that should solve your issue. Thanks for submitting this :-)
