Bug 38580 - Vicious freeze when launching freecraft-1.18-r2
|
Bug#:
38580
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: critical
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: games@gentoo.org
|
Reported By: arnaud.jeansen@insa-rouen.fr
|
|
Component: Games
|
|
|
URL:
|
|
Summary: Vicious freeze when launching freecraft-1.18-r2
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2004-01-18 01:29 0000
|
When I launched freecraft on the command line, It resulted in a high processor
use with nothing happening (infinite loop ?). I couldn't even kill it, the
system was too busy to react to any of my commands (including a frenzied
Ctrl+C)
Rebooted, tried a simple freecraft --help (I assumed I had done something
wrong), had to finally reboot as well...
Reproducible: Always
Steps to Reproduce:
1.run "freecraft"
2.
3.
Actual Results:
nothing happens, apart from a 100% used processor and a DE too slow to do
anything
Expected Results:
displayed the game menu
Portage 2.0.50_pre16 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9,
2.4.22_firewall)
=================================================================
System uname: 2.4.22_firewall i686 Intel(R) Celeron(R) CPU 2.40GHz
Gentoo Base System version 1.4.3.12
Autoconf: sys-devel/autoconf-2.59
Automake: sys-devel/automake-1.7.8
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer -falign-functions=4
-falign-jumps=4"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer -falign-functions=4
-falign-jumps=4"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
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="X Xaw3d aalib acpi alsa apm arts avi berkdb bonobo canna cdr crypt cups
emacs encode esd ethereal fbcon firebird foomaticdb gdbm ggi gif gnome gpm gtk
gtk2 gtkhtml guile imlib java jpeg ldap libg++ libwww mad mikmod motif mpeg
mule
ncurses nls oggvorbis opengl oss pam pcmcia pdflib perl png pnp python qt
quicktime readline ruby samba scanner sdl slang slp socks5 spell sse ssl svga
tcltk tcpd tetex tiff truetype trusted usb videos wmf x86 xinerama xml xml2
xmms
xv zlib"
sounds like freecraft fork bombed
what does /usr/games/bin/freecraft look like ?
Right, the program seems a bit too small :)
$ ls -l /usr/games/bin/freecraft
-rwxr-x--- 1 games games 510 18. Jan 09:41 /usr/games/bin/freecraft
I'm busy with exams today and tomorrow, but I'll emerge it again and post the output at the end of the week
ok, update to freecraft-1.18-r3
remember, you must re emerge freecraft-fcmp afterwards...
NOT Before!
well or at least again afterwards.
I suggest combining the ebuilds..
you can do both fcmp and war2 cd ...
although I haven't gotten the Cd to work from that script mentioned.
no, because you dont need fcmp to play freecraft
and personally, i think the graphics in it look horrible :)
as for the script not working, we didnt write it, the freecraft people did ... so unless you can give us a small patch to fix it, i dont plan on trying ;)
Why not making three ebuilds instead of the actual 2 ???
* keep fcmp the way it is now
* a new freecraft ebuild without the *ccl files (graphics independant)
* a small warcraft-graphics package with the ccl files linking to warcraft graphics and the script to extract it from the cdrom...
I think it would make more sense : you install freecraft and one of the graphics package, without having to reinstall fcmp every time at every freecraft emerge because the fcmp ccl files got overwritten.
(well I don't know if it's possible to make an ebuild depend on either ... or ... ; might make this complicated... OK forget it)
Anyway, I'll stop complaining about these packages, already 2 new releases in a few weeks and still bitching :)
Oh, and yes Spanky, the graphics are ugly (can't deny it) but I didn't buy warcraft...
Don't plan to work on the script either :)
i didnt realize that the packages were clobbering each other ... you guys
failed to mention that fact :P
file a new bug for this please ;)