Attempting to start warzone 2100 for amd64 immediately results in the following errors: ErrorBox: Couldn't open palette.bin ErrorBox: Couldn't load palette data Then returns to terminal Reproducible: Always Steps to Reproduce: 1.# ACCEPT_KEYWORDS="~amd64" emerge warzone 2100 2.$ warzone Actual Results: Outputs the following: Warning: Using colour depth of 32 instead of 24. ErrorBox: Couldn't open palette.bin ErrorBox: Couldn't load palette data Then returns to terminal. Expected Results: Should have displayed a nice GUI menu screen. Bug does not seem to depend on USE variables. Application runs on x86. Multiple reports of bug in gentoo forums. Possible solution: "What you have to do is, after you extract everything, and ./configure and then make. You dont do makeinstall, but what you have to do is copy or link the binary file from /src/ to /data/ in the directory that you extracted. Then you launch the game via the binary in the data folder." http://justlinux.com/forum/printthread.php?t=141666 http://forums.gentoo.org/viewtopic-t-365036-highlight-warzone.html And my emerge info... # emerge info Portage 2.0.51.22-r3 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.11-gentoo-r7 x86_64) ================================================================= System uname: 2.6.11-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 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.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -fomit-frame-pointer -pipe" CHOST="x86_64-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.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=k8 -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo.ccccom.com ftp://mirror.usu.edu/mirrors/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac aalib aim alsa audiofile avi bash-completion berkdb bitmap-fonts bzip2 cdr cjk crypt cups curl dhcp divx4linux dv dvd dvdr emboss emul-linux-x86 encode esd exif expat fam ffmpeg fftw flash foomaticdb fortran gif glut gphoto2 gpm gtk gtk2 idn imagemagick imlib ipv6 java jpeg jpeg2k kde kdeenablefinal kerberos krb4 lcms libwww logitech-mouse lzw lzw-tiff mad mhash mime ming mng mozilla mp3 mpeg msn mysql ncurses nls ogg oggvorbis openal opengl oscar oss pam pcre pdflib perl plotutils png posix povray ppds python qt quicktime readline sdl sharedmem shorten sndfile sockets sox speex spell spl ssl svg szip tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales v4l vcd videos vorbis wddx wmf wxwindows xine xml2 xpm xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
I'm also on amd64 and get this bug. This appears to be an upstream bug. Having talked to upstream (in #warzone ), 0.2.2 is considered old and they advise using the current svn version (see https://gna.org/projects/warzone/ for current project site) which has a totally different data directory structure (including a palette.bin file)
no worky for amd64. I dekeyworded it.
