After merging new afterstep-2.00.05 ebuild I can't start aterm (1.00_beta2) anymore, downgrading afterstep to 2.00.04 helped with that problem for now. emerge info: Portage 2.0.51.21-r1 (default-linux/x86/2005.0, gcc-3.4.3-20050110, glibc-2.3.5-r0, 2.6.11-gentoo-r7 i686) ================================================================= System uname: 2.6.11-gentoo-r7 i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.6.11 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.5-r1 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.6.11 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.zie.pg.gda.pl http://src.gentoo.pl http://gentoo.ynet.sk/pub" LANG="pl_PL" LC_ALL="pl_PL" LINGUAS="pl" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X aalib alsa apache2 apm audiofile avi berkdb bitmap-fonts cdr crypt cups curl dba dts emboss encode esd esound extras fam flac font-server foomaticdb fortran gd gdbm gif gpm gtk gtk2 imagemagick imlib innodb jabber java jpeg libg++ libwww mad maildir mbox mikmod mmx mmx2 motif mozilla mp3 mpeg mysql ncurses nls nptl nptlonly ogg oggvorbis opengl pam pdflib perl png ppds python qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts usb vorbis xml xml2 xmms xv xvid zlib linguas_pl userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS Reproducible: Always Steps to Reproduce: 1. emerge =afterstep-2.00.05 2. try to run aterm 3. look at cool segfault Actual Results: sigsegv Expected Results: run aterm clearly with new afterstep [~]$ aterm Unknown X conn family 33272. Assuming remote. Naruszenie ochrony pamięci [it means segfault in polish] and this is end of my "$ strace aterm", don't want to post whole as it is easily reproducible open("/home/rane/.Xdefaults", O_RDONLY) = 4 fstat64(4, {st_mode=S_IFREG|0660, st_size=1491, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7 2c7000 read(4, "aterm*title: Gentoo\naterm*backgr"..., 4096) = 1491 read(4, "", 4096) = 0 _llseek(4, 0, [0], SEEK_SET) = 0 read(4, "aterm*title: Gentoo\naterm*backgr"..., 4096) = 1491 read(4, "", 4096) = 0 _llseek(4, 0, [0], SEEK_SET) = 0 read(4, "aterm*title: Gentoo\naterm*backgr"..., 4096) = 1491 read(4, "", 4096) = 0 _llseek(4, 0, [0], SEEK_SET) = 0 read(4, "aterm*title: Gentoo\naterm*backgr"..., 4096) = 1491 read(4, "", 4096) = 0 _llseek(4, 0, [0], SEEK_SET) = 0 close(4) = 0 munmap(0xb72c7000, 4096) = 0 write(3, "\3\0\2\0\244\0\0\0\16E\2\0\244\0\0\0", 16) = 16 read(3, "\1\0|\0\3\0\0\0!\0\0\0\1\0\1\1\377\377\377\377\0\0\0\0"..., 32) = 32 read(3, "?\300\372\0\0\0\0\0\0\0\370\10", 12) = 12 read(3, "\1\20}\0\0\0\0\0\244\0\0\0\0\0\0\0\0\5\0\4\0\0\0\0\310"..., 32) = 32 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++
CC'ing upstream afterstep (who I maintain afterstep for via proxy).
As aterm builds based on afterstep's libraries, yes. that's why. Re-emerging aterm will fix this, in my experience. Perhaps we can get this fixed in the ebuilds.
does it - you can mark it as solved - as soon as you will fix ebuilds of course: ]
currently, whenever I reemerge afterstep (usually daily off cvs), I always rebuild aterm too. At least aterm builds quickly. However, in the near future, I plan on dealing with this problem specifically. perhaps by revision bumps, or perhaps by building aterm with it's own libafterimage. or something.
this cannot be solved in an ebuild. Due to a shortcoming in portage, there is no way to solve this problem. The symptoms are cured by running revdep-rebuild, however, this doesn't make anyone happy here. This bug should be closed. :|
Closing per Nathan's request.
