When opening aterm 1.00_beta2, I see this error aterm has encountered a problem interacting with X Windows : Request: 2, Error: 3(BadWindow (invalid Window parameter)) in resource: 0x0 There is a strange black line around the border of the terminal, and whenever you clear the screen gets covered in black, which causes a strange residue effect as demonstrated in the picture. Reproducible: Always Steps to Reproduce: 1. aterm Actual Results: strange version of aterm Expected Results: normal aterm This happens both on my ibook, and on my x86 desktop, with the composite extension enabled, and without. I have tried many versions of gcc, and tried just copying the tarball over to /usr/src and compiling it the normal way. None of my ideas have worked so far in getting rid of the blackness. # emerge info Portage 2.0.51.21 (default-linux/x86/2005.0, gcc-4.0.0-beta20050305, glibc-2.3.5-r0, 2.6.11.8 i686) ================================================================= System uname: 2.6.11.8 i686 AMD Athlon(TM) XP 2200+ Gentoo Base System version 1.6.11 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.3 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r8 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.4.19-r1, 2.6.11 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aalib alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl dba dvd dvdread emboss encode esd f77 fam flac foomaticdb fortran gd gd-external gdbm gif gnome gpm gtk gtk2 guile imagemagick imlib ipv6 java jpeg junit kde libg++ libwww mad mikmod motif mp3 mpeg mysql ncurses nls nvidia ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby sdl silc slang spell ssl svga tcltk tcpd tetex threads tiff truetype truetype-fonts type1-fonts unicode vorbis xine xml xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
i have the same problem when running aterm without arguments. however, when running aterm with these options: "aterm -name aterm -sl 3000 -tr +sb -sr -sk -bg black -fg white -fade 90 -bl -tn xterm -fn -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15 -g 116x57", it works. i don't really know what option in there makes it work, i just know it does. sorry if that doesn't help much, but it might... the result of the above makes aterm look as if it doesn't exist, and bash is running right on the desktop.
I also have this problem. Emerge Info: Portage 2.0.51.22-r1 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11 i686) ================================================================= System uname: 2.6.11 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.4.16 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [disabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.8 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig candy distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo.mirrors.pair.com/ http://mirrors.tds.net/gentoo ftp://ftp.ndlug.nd.edu/pub/gentoo/ ftp://mirrors.tds.net/gentoo http://mirror.datapipe.net/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aalib adns alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl eds emboss encode esd fam flac foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imagemagick imlib ipv6 java jpeg junit kde libg++ libwww mad mikmod motif mozilla mp3 mpeg mysql nas ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl slang spell ssl svga tcpd tiff truetype truetype-fonts type1-fonts vorbis win32codecs xine xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY In my case the background is normally black with a white foreground. I confirm this same behavior but the colors swapped. I receive the exact same message. Running the exact command and arguments in the previous comment seemed to resolve the issue. This seems like a problem with X. My aterm version is: [ebuild R ] x11-terms/aterm-1.00_beta2 -cjk -debug -xgetdefault 0 kB I would really love this to be resolved as I don't really know what aterm flags cause/resolve this behavior.
Does aterm-1.0.0 solve this issue?
I just started using transparant backgrounds, and that seemed to fix it, but it seems that now that the background is black by default, the issue seems to have been resoolved that way (you cannot leave black residue on a black background). It seems to work fine when "-bg white" also. I would say that this issue is resolved.
Thanks
