I'm new to Qingy and so far its been great, but I cant seem to get the GUI to start and it just keeps falling back to text. This is on gentoo.... Any ideas?
From the /var/log/qingy.log:
Oct 23 22:45:26, qingy on tty4, [DEBUG] You chose a screen power management timeout of 5 minutes.
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-t' will switch to right tty...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Oct 23 22:45:26, qingy on tty4, [DEBUG] The following logging facilities will be used: FILE CONSOLE
Oct 23 22:45:26, qingy on tty4, [DEBUG] Session locking is enabled.
Oct 23 22:45:26, qingy on tty4, [DEBUG] Native theme resolution is '1024x768'
Oct 23 22:45:26, qingy on tty4, [DEBUG] Framebuffer resolution is '1280x1024'.
Oct 23 22:45:26, qingy on tty4, [DEBUG] firing up GUI
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] You chose a screen power management timeout of 5 minutes.
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-t' will switch to right tty...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] The following logging facilities will be used: FILE CONSOLE
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] Session locking is enabled.
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] redirected stderr to logging facilities...
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (c) 2001-2008 The world wide DirectFB Open Source Community
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (c) 2000-2004 Convergence (integrated media) GmbH
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] ----------------------------------------------------------------
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (*) DirectFB/Core: Single Application Core. (2008-09-15 18:38) [ DEBUG ][ TRACE ]
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (!) DirectFB/FBDev/agp: Acquire failed!
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] --> Device or resource busy
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (!) [ 3653: 0.000] --> Caught signal 11 (at 0xb7bcee40, invalid address) <--
Oct 23 22:45:28, qingy on tty4, [DEBUG] GUI exited
Oct 23 22:45:28, qingy on tty4, [DEBUG] GUI failed and no auth data present: reverting to text mode
Oct 23 22:45:30, qingy-DirectFB on tty4, [DEBUG] stderr logger process shutting down...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, it seems you have some issue with your machine and DirectFB here...
I cannot help you more since this is an issue with DirectFB, not qingy.
I suggest you head to www.directfb.org and loog for help there, I remember they have mailing lists and/or irc channels...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm new to Qingy and so far its been great, but I cant seem to get the GUI to start and it just keeps falling back to text. This is on gentoo.... Any ideas?
From the /var/log/qingy.log:
Oct 23 22:45:26, qingy on tty4, [DEBUG] You chose a screen power management timeout of 5 minutes.
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-t' will switch to right tty...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Oct 23 22:45:26, qingy on tty4, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Oct 23 22:45:26, qingy on tty4, [DEBUG] The following logging facilities will be used: FILE CONSOLE
Oct 23 22:45:26, qingy on tty4, [DEBUG] Session locking is enabled.
Oct 23 22:45:26, qingy on tty4, [DEBUG] Native theme resolution is '1024x768'
Oct 23 22:45:26, qingy on tty4, [DEBUG] Framebuffer resolution is '1280x1024'.
Oct 23 22:45:26, qingy on tty4, [DEBUG] firing up GUI
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] You chose a screen power management timeout of 5 minutes.
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-t' will switch to right tty...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] The following logging facilities will be used: FILE CONSOLE
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] Session locking is enabled.
Oct 23 22:45:26, qingy-DirectFB on tty4, [DEBUG] redirected stderr to logging facilities...
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (c) 2001-2008 The world wide DirectFB Open Source Community
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (c) 2000-2004 Convergence (integrated media) GmbH
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] ----------------------------------------------------------------
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (*) DirectFB/Core: Single Application Core. (2008-09-15 18:38) [ DEBUG ][ TRACE ]
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (!) DirectFB/FBDev/agp: Acquire failed!
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] --> Device or resource busy
Oct 23 22:45:28, qingy-DirectFB on tty4, [DEBUG] (!) [ 3653: 0.000] --> Caught signal 11 (at 0xb7bcee40, invalid address) <--
Oct 23 22:45:28, qingy on tty4, [DEBUG] GUI exited
Oct 23 22:45:28, qingy on tty4, [DEBUG] GUI failed and no auth data present: reverting to text mode
Oct 23 22:45:30, qingy-DirectFB on tty4, [DEBUG] stderr logger process shutting down...
Hi, it seems you have some issue with your machine and DirectFB here...
I cannot help you more since this is an issue with DirectFB, not qingy.
I suggest you head to www.directfb.org and loog for help there, I remember they have mailing lists and/or irc channels...