Summary: | Game "Flightgear" crashes at startup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lorazo <patrick.lorazo> |
Component: | [OLD] Games | Assignee: | Gentoo Games <games> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | avuton, extronus, patrick.lorazo, paulo, x11 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrick Lorazo
2005-12-10 11:36:02 UTC
Fresh stage1 gentoo install, then installed flightgear 0.9.9 Same problem as the other guy.. Removed and reinstalled flightgear and it's dependencies (replaced glut with freeglut, and rebuilt openal plib simgear & flightgear), afterwards I got the intro screen for about a second "setting up scenegraph and user interface", then exits with nothing but a Segmentation fault. Occasionaly, i get the intro screen and this instead of a segfault. FATAL: PUI: No Live Interface! Forgot to call puInit ? tried downgrading to 0.9.8 and contiued having the problem. upgraded again, then emerge -e world. Same segfault problem continued. Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r4 i686) ================================================================= System uname: 2.6.14-gentoo-r4 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] 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.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe -mmmx -msse" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /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/qmail/alias /var/qmail/control /var/vpopmail/domains /var/vpopmail/etc" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -pipe -mmmx -msse" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.pacific.net.au/linux/Gentoo http://ftp.planetmirror.com/pub/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="x86 X a52 aac acpi alsa apache2 apm arts audiofile avi bash-completion berkdb bitmap-fonts bzip2 cddb cdparanoia cdr crypt css cups curl dbus directfb divx dts dvb dvd dvdr dvdread emboss encode exif expat fbcon ffmpeg fftw firefox flac foomaticdb fortran freeglut ftp gd gdbm gif glut gmp gphoto2 gpm gstreamer gtk gtk2 hal idn ieee1394 imagemagick imap imlib ipv6 jack java javascript joystick jpeg kde lcms libg++ libwww lm_sensors mad maildir matroska mikmod mmx mmxext mng motif mp3 mpeg mpeg2 msn mysql nas ncurses nls nsplugin ogg oggvorbis openal opengl oss pam pcre pdflib perl perlsuid png portaudio python qmail qt quicktime readline samba sdl session sharedmem slp speex spell sse ssl tcltk tcpd theora tiff truetype truetype-fonts type1-fonts udev usb userlocales v4l vcd vorbis win32codecs wxwindows xine xml2 xmms xosd xv xvid zlib video_cards_nvidia video_cards_radeon video_cards_sis video_cards_trident video_cards_savage video_cards_via userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY (In reply to comment #0) > After updating "Flightgear" to version 0.9.9, the program crashes at startup > (i.e., after typing "fgfs") with the following details: ...... Ahem... Forgot to mention I had a -mfpmath=sse in my CFLAGS before.. I just rebuilt flightgear dependencies again without it (I was in the middle of the recompile while I submitted - naughty me for not being patient, sorry) Things now work as they are supposed to.. The original problem I was having (similar to the other guy) potentially caused by not having freeglut libraries maybe? the segfault issue was my own stoopidness. I'm off to fly around with my nice new joystick... :) The proposed solution (replace "glut" by "freeglut" and re-emerge "openal", "plib", "simgear", and "flightgear") has not worked for me... what version of X are you running, Lorazo? Also, are you running ati-drivers or nvidia-glx/kernel or just plain X drivers? I use version 6.8.2-r6 of X as well as the ATI drivers (I have a Radeon 9200 SE video card) provided in the kernel itself. I also reinstalled version 0.9.8 of "Flightgear" this morning and it works fine; just to make sure the problem is really related to the latest version of "Flightgear"... I do not know if this is of any help, but it seems other people have recently experienced similar problems; please see http://www.mail-archive.com/flightgear-devel@flightgear.org/msg36189.html Look also at http://www.opensubscriber.com/message/flightgear-devel@flightgear.org/2439056.html and related messages. I was have same problem. I tried recompiling things but it does not fixed.. when i changed bit depth from 24 to 16 and it worked. :) 32 bit display may also work. I also switched depth to 16 and it now works... I'm curious regarding the 'real' status of this bug among users. Has nobody solved this? Are there known workarounds (patches)? Regarding official bug solving, is any dev looking at this? This bug is over a year old. (In reply to comment #9) > I'm curious regarding the 'real' status of this bug among users. Has nobody > solved this? Are there known workarounds (patches)? > It might be fixed in 0.9.10. Have you tried? > Regarding official bug solving, is any dev looking at this? This bug is over a > year old. > It appears to be an upstream problem, so you'd have to look around the mailing lists there. http://www.flightgear.org/Downloads/source.shtml says to use the older version of freeglut. Seems like a known issue so I'll mark this UPSTREAM. Hopefully, it'll be fixed up in the next release. |