Perhaps it is well-known, but is there a workaround to make qingy work with these kernel series? The most we can expect when using qingy with kernel 2.6.7 is a hangup. I am aware that s4t4n is on the move on this one. Additional forum URLs: http://forums.gentoo.org/viewtopic.php?p=1336330#1336330 http://forums.gentoo.org/viewtopic.php?p=1273293#1273293 As refered to the first URL, it seems that it does work with kernels 2.6.8, so I would advise to put a note when emerging qingy... and also to upgrade gentoo-dev-sources to kernel 2.6.8 Reproducible: Always Steps to Reproduce: 1. Use qingy with gentoo-dev-sources (kernel 2.6.7) Actual Results: Spawning qingy hangs the computer. Portage 2.0.50-r9 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040619-r0, 2.6.7-gentoo-r11) ================================================================= System uname: 2.6.7-gentoo-r11 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.5.2 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=i686 -fomit-frame-pointer -funroll-loops -pipe -fforce-addr -fforce-mem -fmove-all-movables" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/share/config /usr/kde/3/share/config /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="-O3 -mcpu=i686 -fomit-frame-pointer -funroll-loops -pipe -fforce-addr -fforce-mem -fmove-all-movables" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache distcc fixpackages sandbox usersandbox" GENTOO_MIRRORS="http://ftp.caliu.info/pub/gentoo/ http://ftp.ntua.gr/pub/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dnow X aalib alsa apache2 apm arts audiofile avi berkdb bindist cdr crypt cups curl directfb divx4linux dvd dvdr encode esd ethereal fastcgi fbcon flac flash foomaticdb freetype gd gdbm ggi gif gmp gnome gphoto2 gpm gstreamer gtk gtk2 icq imagemagick imlib ipv6 java jikes jpeg junit kde lcms ldap libg++ libwww linguas_el linguas_es mad memlimit mikmod mmx motif mozilla mpeg msn ncurses nls nocd oggvorbis opengl oss pam pdflib perl pic png ppds python qt quicktime readline samba sdl slang spell sse ssl svg svga szip tcltk tcpd tetex tiff truetype ttf unicode usb video_cards_nvidia videos wmf x86 xml xml2 xmms xv xvid zlib"
I'm in the midst of compiling the new 2.6.8 vanilla sources, let's see if they resolve these issues...
I hope it works with the new kernel. Otherwise there might be needed a code revision in qingy.
added a warning to 0.4.1
Final comment: qingy does work with kernel 2.6.8 but with problems. Opening a new bug: 60402