Updated DirectFB-0.9.21 to 0.9.22, rebooted (for other reasons), and when machine came back up, I was presented with the text login prompt on my framebuffer. Have tried unsetting "quiet" in /etc/directfbrc, but nothing is output before the login prompt appears. Reproducible: Always Steps to Reproduce: Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r5 i686) ================================================================= System uname: 2.6.11-gentoo-r5 i686 AMD Athlon(tm) XP 3000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 8 2005, 14:18:11)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -mcpu=athlon-xp -O2 -frename-registers -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -mcpu=athlon-xp -O2 -frename-registers -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms userpriv usersandbox" GENTOO_MIRRORS="ftp://gentoo.blueyonder.co.uk/mirrors/gentoo http://ftp.easynet.nl/mirror/gentoo/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" LDFLAGS="-Wl,-O1" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.0.2/gentoo-portage" USE="x86 3dnow 3dnowex S3TC X a52 aac aalib acpi alsa amd apm avi berkdb bitmap-fonts bluetooth bonobo bzip2 bzlib cdda cddb cdio cdr chroot clamav crypt cscope cups curl dga directfb disablexmb divx4linux dmx dvd dvdr dvdread edl emboss encode esd ethereal faac faad fam fb fbcon ffmpeg fla flac fmod font-server foomaticdb freetype gb gd gdbm geoip gif gimpprint gmail gnokii gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile howl ieee1394 imagemagick imap imlib imlib2 java javascript jpeg jpeg2k junit lcms libcaca libg++ libgda libwww live lzo lzw lzw-tiff mad maildir mailwrapper matroska md5sum mikmod mjpeg mmx mmx2 mng monkey motif mozcalendar mozdevelop mozilla moznoirc mozsvg mp3 mpeg mpeg2 mpeg4 mplayer msn mysql nas ncurses network nls nptl nptlonly ntlm nvidia oav odbc ogg oggvorbis opengl operanom2 pam pcntl pcre pdf pdflib perl pic png ppds python qt quicktime readline real rtc samba sasl scanner sdl slang slp sms snmp speex spell sse ssl stream svg symlink sysfs tcpd tga theora tiff truetype truetype-fonts type1 type1-fonts usb utf8 v4l v4l2 vcd vidix vlm vorbis wmf wxwindows xanim xface xine xml xml2 xmms xosd xpm xprint xrandr xv xvid xvmc yahoo yv12 zlib video_cards_nvidia" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LINGUAS
Uh, I see DirectFB 0.9.22 available on my own machine, will try updating and see what happens...
You simply have to re-emerge qingy after updating DirectFB, as stated by the DirectFB ebuild itself: Each DirectFB update in the 0.9.xx series breaks DirectFB related applications. Please run "revdep-rebuild" which can be found by emerging the package 'gentoolkit'.
I did. revdep-rebuild didn't rebuild qingy. Please don't mark bugs as invalid before getting feedback from the user. ldd reports no libdirectfb links. Is DirectFB compiled in staticly?
Reopening.
> I did. revdep-rebuild didn't rebuild qingy. Strange. Anyway, you have to re-emerge qingy. > Please don't mark bugs as invalid before getting feedback from the user. I'm pretty certain about my actions here... ;-) > ldd reports no libdirectfb links. qingy links to DirectFB in its graphical user interface: /sbin/qingy-DirectFB > Is DirectFB compiled in staticly? That depends on wether you are using the "static" USE flag...
I did rebuild qingy, straight after revdep-rebuild didn't. I'm not using the static USE flag, and I just realised that the graphical part of qingy is /sbin/qingy-DirectFB: # ldd /sbin/qingy-DirectFB ... libdirectfb-0.9.so.22 => /usr/lib/libdirectfb-0.9.so.22 (0xb7f65000) libfusion-0.9.so.22 => /usr/lib/libfusion-0.9.so.22 (0xb7f60000) libdirect-0.9.so.22 => /usr/lib/libdirect-0.9.so.22 (0xb7f57000) ... So that's not the cause. Removing /etc/directfbrc doesn't help, so it's not that causing it.
On my working laptop, running: # /sbin/qingy-DirectFB tty2 while logged in on vc2 (not via qingy), brings up a qingy screen. Running the same on the broken machine, results in the screen flickering for a second, then printing "Killed" and back to the prompt. # /sbin/qingy-DirectFB -v tty2 gives: Session locking is NOT enabled. (*) DirectFB/Config: Parsing config file '/etc/directfbrc'. ---------------------- DirectFB v0.9.22 --------------------- (c) 2000-2002 convergence integrated media GmbH (c) 2002-2004 convergence GmbH ----------------------------------------------------------- (*) DirectFB/Core: Single Application Core. (2005-04-14 09:50) (!) Direct/Modules: Unable to dlopen `/usr/lib/directfb-0.9.22/systems/libdirectfb_sdl.so'! --> libdirectfb-0.9.so.21: cannot open shared object file: No such file or directory (*) Direct/Memcpy: Using MMXEXT optimized memcpy() (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 16169)... (!) Direct/Modules: Unable to dlopen `/usr/lib/directfb-0.9.22/inputdrivers/libdirectfb_sdlinput.so'! --> libdirectfb-0.9.so.21: cannot open shared object file: No such file or directory (*) Direct/Thread: Running 'PS/2 Input' (INPUT, 16172)... (!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802] (*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH) (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 16173)... (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH) (*) Direct/Thread: Running 'Linux Input' (INPUT, 16174)... (*) DirectFB/Input: AT Translated Set 2 keyboard (1) 0.1 (convergence integrated media GmbH) (*) Direct/Thread: Running 'Linux Input' (INPUT, 16175)... (*) DirectFB/Input: ImExPS/2 Logitech Explorer MouseLinux (2) 0.1 (convergence integrated media GmbH) (!) DirectFB/linux_input: could not grab device --> Device or resource busy (!) [16129: 0.000] --> Caught signal 11 (at (nil), invalid address) <-- (!) DirectFB/core/vt: Unable to disallocate VT! --> Device or resource busy Killed It looks like it's erroring because it can't grab the mouse, but I doubt it. Any ideas?
Ok, that doesn't make sense... just read that output again and noticed the: (!) Direct/Modules: Unable to dlopen `/usr/lib/directfb-0.9.22/systems/libdirectfb_sdl.so'! --> libdirectfb-0.9.so.21: cannot open shared object file: No such file or directory I'll rebuild SDL.
That did nothing apart from fix that link. I guess it would only be used if there was a "system=sdl" in /etc/directfbrc. Same results: # qingy-DirectFB -v tty2 Session locking is NOT enabled. (*) DirectFB/Config: Parsing config file '/etc/directfbrc'. ---------------------- DirectFB v0.9.22 --------------------- (c) 2000-2002 convergence integrated media GmbH (c) 2002-2004 convergence GmbH ----------------------------------------------------------- (*) DirectFB/Core: Single Application Core. (2005-04-14 09:50) (*) Direct/Memcpy: Using MMXEXT optimized memcpy() (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 1380)... (*) Direct/Thread: Running 'PS/2 Input' (INPUT, 1383)... (!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802] (*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH) (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 1384)... (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH) (*) Direct/Thread: Running 'Linux Input' (INPUT, 1385)... (*) DirectFB/Input: AT Translated Set 2 keyboard (1) 0.1 (convergence integrated media GmbH) (*) Direct/Thread: Running 'Linux Input' (INPUT, 1386)... (*) DirectFB/Input: ImExPS/2 Logitech Explorer MouseLinux (2) 0.1 (convergence integrated media GmbH) (!) DirectFB/linux_input: could not grab device --> Device or resource busy (!) [ 1340: 0.000] --> Caught signal 11 (at (nil), invalid address) <-- (!) DirectFB/core/vt: Unable to disallocate VT! --> Device or resource busy Killed And I'm spent :p What to try next?
Uhm, maybe you are using gpm?
Any news? Looks like a DirectFB bug to me...
Uhm... no more feedback, plus it works here greatly under gentoo-sources-2.6.11-r8 DirectFB-0.9.22 You have a problem with DirectFB, not qingy, Mal, and this is not the correct place to discuss it. Feel free to start a thread on the discussion forums / mailing lists...
I updated my kernel and all is fine now. I really can't work out why tho. May have possibly been a change in the framebuffer parameters. Thanks anyway
Better this way :-) The framebuffer subsystem still gets major changes from kernel to kernel, and things are known to break fairly often...
