NOTE: I have only tried this on fluxbox-0.9.9 and x.org-6.7.0, but there is a forums thread at: http://forums.gentoo.org/viewtopic.php?p=1249495 when trying to open x11-terms/aterm-0.4.2-r4 a BLANK aterm window appears with no cursor. Additionally, the aterm process is chewing through close to %100 cpu. One suggestion on the thread was with regards to changing the default size of the aterm window. I do not have a .Xdefaults file. I also do not have a .fluxbox/apps file. I tried using these files to specify different initial window dimensions for aterm but they did not change anything. Reproducible: Always Steps to Reproduce: 1.launch aterm (doesn't matter how) 2. 3. Actual Results: aterm window appears and uses cpu cycles, but does not display anything inside the window. Expected Results: aterm should launchh a window which is usable Portage 2.0.50-r8 (default-ppc-2004.1, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.6) ================================================================= System uname: 2.6.6 ppc 7455, altivec supported Gentoo Base System version 1.4.16 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CFLAGS="-O2 -pipe -mcpu=7450 -maltivec -mabi=altivec -fno-strict-aliasing -fomit-frame-pointer" CHOST="powerpc-unknown-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/lib/pbbuttons /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe -fno-strict-aliasing" DISTDIR="/usr/portage/distfiles" FEATURES="buildpkg ccache userpriv usersandbox" GENTOO_MIRRORS="ftp://mirror.pacific.net.au/linux/Gentoo ftp://ftp.vic.keypoint.com.au http://ftp.gentoo.or.kr/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.0.1/gentoo-portage" USE="X aac alsa altivec berkdb cdr devfs26 dga directfb dnd doc escreen fbcon fbdev freetype gdbm gif gpm ieee1394 imap imlib jpeg ladcca libwww mitshm motif mozilla ncurses noreiserfs oggvorbis opengl pam pdflib perl png ppc pthreads python qt radeon readline scanner sdl slang softmmu ssl tcltk tcpd threads tiff truetype type1 usb xmms xv zlib"
Compiling with gcc-3.3.3_pre20040426 fixed the problem for me. I fixed the problem with older versions of gcc by compiling with -O1 instead of -O2.
2004.3 will have a gcc-3.4 based toolchain. We hope the toolchain will have stabilized upstream by then.
