Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Qingy not functioning after update world
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
tenspd137
Guru
Guru


Joined: 22 Aug 2006
Posts: 370

PostPosted: Wed Feb 20, 2013 12:13 am    Post subject: Qingy not functioning after update world Reply with quote

Hi all -

I did an emerge world today and in the revdep-rebuild, qingy needed to be relinked to DirectFB. Anyway, it keeps failing (both in revdep rebuild and when I try to emerge it). It appears that it can't find something in libncurses, even though it is definetly installed.

Here is the config.log:

http://pastebin.com/gphdY4XG

emerge --info

Code:

Portage 2.1.11.52 (default/linux/amd64/13.0, gcc-4.7.2, glibc-2.16.0, 3.7.2-gentoo x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-3.7.2-gentoo-x86_64-Intel-R-_Xeon-R-_CPU_E5-2620_0_@_2.00GHz-with-gentoo-2.2
KiB Mem:    16360996 total,   4684860 free
KiB Swap:    4194300 total,   4194300 free
Timestamp of tree: Tue, 19 Feb 2013 16:30:01 +0000
ld GNU ld (GNU Binutils) 2.23.1
app-shells/bash:          4.2_p42
dev-java/java-config:     2.1.12-r1
dev-lang/python:          2.7.3-r3, 3.2.3-r2, 3.3.0-r1
dev-util/cmake:           2.8.10.2-r1
dev-util/pkgconfig:       0.28
sys-apps/baselayout:      2.2
sys-apps/openrc:          0.11.8
sys-apps/sandbox:         2.6
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.10.3, 1.11.6, 1.13.1
sys-devel/binutils:       2.23.1
sys-devel/gcc:            4.6.3, 4.7.2
sys-devel/gcc-config:     1.8
sys-devel/libtool:        2.4.2
sys-devel/make:           3.82-r4
sys-kernel/linux-headers: 3.7 (virtual/os-headers)
sys-libs/glibc:           2.16.0
Repositories: gentoo x-portage science nbigaouette seden bitcoin drevilt betagarden
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j13"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /var/lib/layman/science /var/lib/layman/nbigaouette /var/lib/layman/seden /var/lib/layman/bitcoin /var/lib/layman/drevilt /var/lib/layman/betagarden"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X \ acl amd64 berkdb bzip2 cli consolekit cracklib crypt cxx dri fortran gdbm gpm iconv ipv6 mmx modules mudflap multilib ncurses nls nptl openmp pam pcre readline session sse sse2 ssl tcpd truetype unicode zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" GRUB_PLATFORMS="efi-64" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" PHP_TARGETS="php5-3" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_2" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

=================================================================
                        Package Settings
=================================================================

sys-apps/qingy-1.0.0 was built with the following:
USE="X directfb gpm (multilib) opensslcrypt pam -crypt -emacs -static" ABI_X86="64"


Build log
Code:

 * Package:    sys-apps/qingy-1.0.0
 * Repository: gentoo
 * Maintainer: base-system@gentoo.org
 * USE:        X abi_x86_64 amd64 crypt directfb elibc_glibc gpm kernel_linux multilib pam userland_GNU
 * FEATURES:   sandbox
>>> cfg-update-1.8.2-r1: Checksum index is up-to-date ...
>>> Unpacking source...
>>> Unpacking qingy-1.0.0.tar.bz2 to /var/tmp/portage/sys-apps/qingy-1.0.0/work
>>> Unpacking qingy-gentoo-theme-2.1.tar.bz2 to /var/tmp/portage/sys-apps/qingy-1.0.0/work
>>> Source unpacked in /var/tmp/portage/sys-apps/qingy-1.0.0/work
>>> Preparing source in /var/tmp/portage/sys-apps/qingy-1.0.0/work/qingy-1.0.0 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-apps/qingy-1.0.0/work/qingy-1.0.0 ...
 * econf: updating qingy-1.0.0/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating qingy-1.0.0/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --sbindir=/sbin --disable-optimizations --enable-pam --disable-static-build --enable-gpm-lock --enable-x-support --enable-DirectFB-support --enable-crypto=libgcrypt --disable-emacs --without-lispdir
configure: loading site script /usr/share/config.site
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-pc-linux-gnu-g++... gcc3
checking how to run the C++ preprocessor... x86_64-pc-linux-gnu-g++ -E
checking for x86_64-pc-linux-gnu-g77... no
checking for x86_64-pc-linux-gnu-xlf... no
checking for x86_64-pc-linux-gnu-f77... no
checking for x86_64-pc-linux-gnu-frt... no
checking for x86_64-pc-linux-gnu-pgf77... no
checking for x86_64-pc-linux-gnu-cf77... no
checking for x86_64-pc-linux-gnu-fort77... no
checking for x86_64-pc-linux-gnu-fl32... no
checking for x86_64-pc-linux-gnu-af77... no
checking for x86_64-pc-linux-gnu-xlf90... no
checking for x86_64-pc-linux-gnu-f90... no
checking for x86_64-pc-linux-gnu-pgf90... no
checking for x86_64-pc-linux-gnu-pghpf... no
checking for x86_64-pc-linux-gnu-epcf90... no
checking for x86_64-pc-linux-gnu-gfortran... x86_64-pc-linux-gnu-gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether x86_64-pc-linux-gnu-gfortran accepts -g... yes
checking the maximum length of command line arguments... 1572864
checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for correct ltmain.sh version... yes
checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by x86_64-pc-linux-gnu-g++... /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for x86_64-pc-linux-gnu-g++ option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-g++ PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-g++ static flag -static works... yes
checking if x86_64-pc-linux-gnu-g++ supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for x86_64-pc-linux-gnu-gfortran option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-gfortran PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-gfortran static flag -static works... yes
checking if x86_64-pc-linux-gnu-gfortran supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-gfortran linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
checking for a BSD-compatible install... /usr/bin/install -c
checking for x86_64-pc-linux-gnu-gcc... (cached) x86_64-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... (cached) gcc3
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking for emacs... emacs
checking where .elc files should go... no
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking grp.h usability... yes
checking grp.h presence... yes
checking for grp.h... yes
checking lastlog.h usability... yes
checking lastlog.h presence... yes
checking for lastlog.h... yes
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking for string.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for unistd.h... (cached) yes
checking linux/kd.h usability... yes
checking linux/kd.h presence... yes
checking for linux/kd.h... yes
checking linux/vt.h usability... yes
checking linux/vt.h presence... yes
checking for linux/vt.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for sys/wait.h that is POSIX.1 compatible... (cached) yes
checking for crypt in -lcrypt... yes
checking for dlopen in -ldl... yes
checking for pthread_create in -lpthread... yes
checking for getdomainname... yes
checking curses.h usability... yes
checking curses.h presence... yes
checking for curses.h... yes
checking term.h usability... yes
checking term.h presence... yes
checking for term.h... yes
checking for setupterm in -lncurses... no
configure: error: One or more function libraries that are necessary to compile this program are missing on this system. Cannot continue.



Any suggestions?

Thanks!


Last edited by tenspd137 on Wed Feb 20, 2013 4:28 am; edited 1 time in total
Back to top
View user's profile Send private message
duby2291
Guru
Guru


Joined: 17 Oct 2004
Posts: 426

PostPosted: Wed Feb 20, 2013 12:30 am    Post subject: Reply with quote

Hve you tried re-emerging ncurses? I don't know that will fix it. It could be something as simple as you need to symlink the lib to a name that qingy expects to find.
_________________
MB: Biostar TForce 6100 AM2 @ 250x10
CPU: AMD Athlon 64 3800+ X2 @ 2500mhz
MEM: G. Skill DDR2-800 2GB @ DDR2-1000
GPU: nVidia GeForce 7600 GT
OS: Gentoo Linux 2006.1
Back to top
View user's profile Send private message
tenspd137
Guru
Guru


Joined: 22 Aug 2006
Posts: 370

PostPosted: Wed Feb 20, 2013 12:52 am    Post subject: Reply with quote

Yeah - I tried that with no luck. In fact, I even emerge -C'd ncurses - oops. Had to copy the libs out of a stage 3 tarball to re-emerge them. This isn't the only problem I am having with qingy today. On another computer it compiles, but all of a sudden won't run. But - one thing at a time.
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5522

PostPosted: Wed Feb 20, 2013 2:26 am    Post subject: Reply with quote

Just a guess, but most likely qingy is one of those programs that hate ncurses[tinfo].
Back to top
View user's profile Send private message
tenspd137
Guru
Guru


Joined: 22 Aug 2006
Posts: 370

PostPosted: Wed Feb 20, 2013 4:42 am    Post subject: Reply with quote

Ok - that makes sense - when I go back to work I'll make sure that is off. I was using my work computer to try and compare what happened to my laptop, but that didn't work out. Anyway - I am not sure what else would have changed after the update world to cause it to stop working. My kernel is the same, so it isn't a problem with framebuffer / console configuration as far as I can tell. The update world did update DirectFB, but I tried both the updated and last version. Log files from Qingy are:

Linked against DirectFB 1.6.3:
Code:

Feb 19 21:19:00, qingy on tty1, [DEBUG] Native theme resolution is '800x600'
Feb 19 21:19:00, qingy on tty1, [DEBUG] Framebuffer resolution is '1920x1080'.
Feb 19 21:19:00, qingy on tty1, [DEBUG] firing up GUI
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] Session locking is enabled.
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] redirected stderr to logging facilities...
Feb 19 21:19:00, qingy-DirectFB on tty1, [ERROR] Unrecoverable DirectFB error: reverting to text mode!
Feb 19 21:19:00, qingy-DirectFB on tty1, [ERROR] This usually means that you have an issue with DirectFB, not with qingy...
Feb 19 21:19:00, qingy-DirectFB on tty1, [ERROR] Most likely you don't have your console framebuffer properly set up.
Feb 19 21:19:00, qingy-DirectFB on tty1, [ERROR] Please turn on DEBUG log level in qingy to see exactly why DirectFB is letting you down.
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] Starting GUI shutdown...
Feb 19 21:19:00, qingy-DirectFB on tty1, [DEBUG] GUI shutdown complete
Feb 19 21:19:00, qingy on tty1, [DEBUG] GUI exited
Feb 19 21:19:00, qingy on tty1, [DEBUG] GUI failed and no auth data present: reverting to text mode
Feb 19 21:19:01, qingy-DirectFB on tty1, [DEBUG] stderr logger process shutting down...
Feb 19 21:19:08, qingy on tty1, [DEBUG] Starting text session with argument #0: -bash


also, at the terminal, it says something about DirectFB/core/system: no system found, but it doesn't get put in the above error log


Linked against DirectFB 1.4.9
Code:

Feb 19 21:24:09, qingy on tty1, [DEBUG] firing up GUI
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] Session locking is enabled.
Feb 19 21:24:09, qingy-DirectFB on tty1, [DEBUG] redirected stderr to logging facilities...
Feb 19 21:24:10, qingy-DirectFB on tty1, [ERROR] Unrecoverable DirectFB error: reverting to text mode!
Feb 19 21:24:10, qingy-DirectFB on tty1, [ERROR] This usually means that you have an issue with DirectFB, not with qingy...
Feb 19 21:24:10, qingy-DirectFB on tty1, [ERROR] Most likely you don't have your console framebuffer properly set up.
Feb 19 21:24:10, qingy-DirectFB on tty1, [ERROR] Please turn on DEBUG log level in qingy to see exactly why DirectFB is letting you down.
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] Starting GUI shutdown...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] GUI shutdown complete
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG]    ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.9 |~~~~~~~~~~~~~~~~~~~~~~~~~~
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG]         (c) 2001-2010  The world wide DirectFB Open Source Community
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG]         (c) 2000-2004  Convergence (integrated media) GmbH
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG]       ----------------------------------------------------------------
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Core: Single Application Core. (2013-02-20 04:22)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Memcpy: Using libc memcpy()
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'VT Flusher' (-1) [DEFAULT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/FBDev: Found 'inteldrmfb' (ID 0) with frame buffer at 0xb0072000, 8100k (MMIO 0x00000000, 0k)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: Power Button (1) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: Power Button (2) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: Video Bus (3) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: Video Bus (4) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: AT Translated Set 2 keyboard (5) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: SynPS/2 Synaptics TouchPad (6) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: HP HP Link-5 micro dongle (7) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: HP HP Link-5 micro dongle (8) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: HP TrueVision HD (9) 0.1 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Hotplug with Linux Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: Hot-plug detection enabled with Linux Input Driver
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Genefx: MMX detected and enabled
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Core/WM: Default 0.3 (directfb.org)
Feb 19 21:24:10, qingy-DirectFB on tty1, [DEBUG] stderr logger process shutting down...
Feb 19 21:24:10, qingy on tty1, [DEBUG] GUI exited
Feb 19 21:24:10, qingy on tty1, [DEBUG] GUI failed and no auth data present: reverting to text mode
Feb 19 21:24:56, qingy on tty1, [DEBUG] Starting text session with argument #0: -bash


This one is a little more detailed, and I think everything in the console made it into the log, but still isn't exactly helpful.

The only thing I can think of any more is that because I have a laptop with an integrated intel and discreet ATi gpu which are the newer muxless kind, maybe something with the driver isn't compatible with DirectFB. Not sure how to get any more debug info. On the bright side, slim works and I like it as well, although it feels a little slower - but that seems to be the way it works for me. Something breaks qingy, I move to slim. Later, something breaks slim but qingy works, so I move back and so on.

Any more thoughts on how to debug would be great - more than happy to try because I would like to know what got upgraded that broke qingy, but right now the only difference I see between my laptop and work computer is Nvidia vs Ati. BTW - my use flags for DirectFB/Qingy (on my laptop)
Code:

[ebuild     U  ] dev-libs/DirectFB-1.6.3-r1 [1.4.9-r1] USE="fbcon gif jpeg jpeg2k%* mmx mng%* opengl%* png sdl sse svg%* truetype zlib -X -bmp% -debug -doc -dynload% -gles2% -imlib2% -input_hub% -mpeg2% -multicore% -pnm% -static-libs -v4l -vdpau%" INPUT_DEVICES="evdev -dynapro -elo2300 -joystick -keyboard -lirc -mouse -mutouch -tslib" VIDEO_CARDS="intel radeon -mach64 -mga -neomagic (-nsc) -nvidia -r128 -s3 -sis -tdfx -via -vmware (-savage%)" 0 kB
[ebuild   R    ] sys-apps/qingy-1.0.0  USE="X directfb emacs gpm pam -crypt -opensslcrypt -static" 0 kB


Thanks!
Back to top
View user's profile Send private message
tenspd137
Guru
Guru


Joined: 22 Aug 2006
Posts: 370

PostPosted: Wed Feb 20, 2013 4:02 pm    Post subject: Reply with quote

So, I am at work, and indeed tinfo is enabled because I have other packages installed that require ncurses[tinfo]. I think I will just give slim a try there as well. I don't want to go and undo a whole bunch of other stuff. I would still like to try and debug what is going on with my laptop though if anyone has more debug hints.

Thanks again.
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5522

PostPosted: Thu Feb 21, 2013 12:49 am    Post subject: Reply with quote

Well, the [tinfo] part of the problem is trivial, but annoying to fix - with [tinfo] setupterm is in tinfo, not in ncurses.
Back to top
View user's profile Send private message
Perdignus
n00b
n00b


Joined: 29 Mar 2013
Posts: 2
Location: Sheboygan

PostPosted: Fri Mar 29, 2013 3:43 pm    Post subject: Reply with quote

Any updates on this? I just built a new system yesterday and was hoping to use Qingy but it's not compiling.
Back to top
View user's profile Send private message
tastytea
n00b
n00b


Joined: 01 May 2013
Posts: 1
Location: Germany

PostPosted: Mon Jul 22, 2013 2:31 pm    Post subject: Reply with quote

Perdignus wrote:
Any updates on this? I just built a new system yesterday and was hoping to use Qingy but it's not compiling.

You need to build qingy with EXTRA_ECONF="--disable-screen-savers", see Bug 462634
Also, I had to turn the "dynload" useflag of DirectFB on.
Hope this helps.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments 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