I've just emerged celestia on my system (ACCEPT_KEYWORDS="~x86"), and it crashes with segmentation fault on startup. This is the output I get: =================================================== rmm@vincent rmm $ celestia nStars: 112521 Parent body 'TYC 5503-946-1' of 'b' not found. Initializing ARB vertex programs . . . Loading ARB vertex program: shaders/diffuse_arb.vp Loading ARB vertex program: shaders/specular_arb.vp Loading ARB vertex program: shaders/haze_arb.vp Loading ARB vertex program: shaders/bumpdiffuse_arb.vp Loading ARB vertex program: shaders/bumphaze_arb.vp Loading ARB vertex program: shaders/shadowtex_arb.vp Loading ARB vertex program: shaders/diffuse_texoff_arb.vp Loading ARB vertex program: shaders/rings_arb.vp Loading ARB vertex program: shaders/ringshadow_arb.vp Loading ARB vertex program: shaders/night_arb.vp Loading ARB vertex program: shaders/glossmap_arb.vp All ARB vertex programs loaded successfully. render path: 3 Segmentation fault =================================================== I'm using the folowing applications and libraries: media-libs/libpng-1.2.5-r4 media-libs/jpeg-6b-r3 media-libs/glut-3.7.1 x11-base/xfree-4.3.0-r5 sys-libs/zlib-1.2.1-r2 media-video/ati-drivers-3.7.0 sys-libs/glibc-2.3.3_pre20040117 sys-devel/gcc-3.3.3 I tried compiling with "kde -gtk" and "-kde gtk" and it has the same result. Reproducible: Always Steps to Reproduce: rmm@vincent config $ emerge info Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040117-r0, 2.6.3) ================================================================= System uname: 2.6.3 i686 Intel(R) Pentium(R) 4 CPU 2.53GHz Gentoo Base System version 1.4.3.13 distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -msse -mmmx -funroll-loops -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -msse -mmmx -funroll-loops -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.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.europe.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb bonobo cdr crypt cups dv dvd encode foomaticdb gdbm gif gphoto2 gpm gstreamer guile imlib java jpeg kde ldap libg++ libwww linguas_pt mad mikmod mmx motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png postgres pt pt_PT python qt quicktime radeon readline samba sdl slang spell sse ssl svga tcpd tiff truetype x86 xml2 xv zlib"
Try getting a backtrace of a core dump. `ulimit -c unlimited` to change core size to unlimited `celestia &` `gdb celestia /path/to/core` (emerge gdb if you don't have it, core is usually ~/core by default) In gdb, `bt` (attach this output)
I don't seem to get a core dump. I checked "ulimit -c" and it's unlimited, however I don't get a "core" file in either "./" or "~/".
Running celestia from gdb it seems to be related with ati-drivers: ====================================================== rmm@vincent rmm $ gdb --args celestia --nofork GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. [...] This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/celestia --nofork (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...nStars: 112521 Parent body 'TYC 5503-946-1' of 'b' not found. Initializing ARB vertex programs . . . Loading ARB vertex program: shaders/diffuse_arb.vp Loading ARB vertex program: shaders/specular_arb.vp Loading ARB vertex program: shaders/haze_arb.vp Loading ARB vertex program: shaders/bumpdiffuse_arb.vp Loading ARB vertex program: shaders/bumphaze_arb.vp Loading ARB vertex program: shaders/shadowtex_arb.vp Loading ARB vertex program: shaders/diffuse_texoff_arb.vp Loading ARB vertex program: shaders/rings_arb.vp Loading ARB vertex program: shaders/ringshadow_arb.vp Loading ARB vertex program: shaders/night_arb.vp Loading ARB vertex program: shaders/glossmap_arb.vp All ARB vertex programs loaded successfully. render path: 3 Program received signal SIGSEGV, Segmentation fault. 0x41854c6d in s11401 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so (gdb) bt #0 0x41854c6d in s11401 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so #1 0x46857040 in ?? () #2 0x4685edf8 in ?? () ========================================================= I'm using ati-drivers-3.7.0 and emerging ati-drivers-3.2.8 I'm able to run celestia successfuly. Changing the summary to reflect this.
Luca, could you have a glance at this?
Just tested ati-drivers-3.7.6 and Celestia still crashes.
As it does for 3.9.0. I'm one of the Celestia developers, and I've managed to track down the problem and find a workaround. It has to do with how many stars the ati-drivers seem willing to draw. It's impossible to say, but it might be that ATI has made some sort of limit since 3.2.8 that is being crossed.
Suggest modifying summary to reflect that is occurs in all versions of Celestia, with ati-drivers > 3.2.8.
I have contacted Pat to find out where the problem is.
Note: this even segfaults using DRI For me and i never got to test 3.2.8 could you all sync in 30 minutes after this note and try celestia-1.3.2_pre20040731 thanks this one works here, compiles with gcc-3.4 and works with DRI, but id like feedback from ati-drivers users Thank you
Well, it segfaults running CVS. A new release is imminent, but not much has changed since July 31st. It runs okay in Mesa mode. I'm beginning to think it's ATI's drivers.
i just recently got a ati card that use ati-drivers and i tried out the latest 3.11.1 and it still segfaults with the snapshot thats in portage Pat: has this been fixed in a newer snapshot? cause from looks of this bug and another one thats been opened bug #48744 id say ati-drivers is somehow broken and unless someone contacts ati i dont think it will be fixed and frankly even if ati is contacted i have a feeling it wont change
I did a great deal of testing with this today. Yes, it crashes when running celestia and attempting to run the ARB vertice program. But, all backtraces and debudding shows that it happens in the ATI driver. So, what I did was to see if X.org had some issues with the driver. I emerged the latest test release of the latest server (xorg-x11-6.7.99.2). *Right after emerging* it worked great. Celestia worked, all other GL apps worked. I emphasize that this is with the old server running the latest libraries. However, upon restart of the server (so that the running server is the latest), all GL apps (even glxinfo) crash the X-server. I know this is a prerelease, I know that the ATI drivers can be expected to have issues with it. I re-merged xorg-6.7.0-r2 and the previous problems returned. But the important thing is that with the latest libraries seem to run Celestia just fine. The server itself seems to have major issues with running any GL applications, but when that is fixed, perhaps complex GL programs like Celestia will run properly. Is anyone brave enough to confirm my findings, especially those of Celestia working after merging the new x-server, but before restarting?
i checked that out as i hadnt upgraded to .99.2 yet on that comp yes celestia works its due to x switching to Mesa indirect GLX help about opengl info shows this
I really don't think that was the case here, since glxgears ran at 800fps. That's a little fast for software.
i didnt check glxgears but i know what celestia reported also .99.2 seems to just blow up when trying to do any 3d with at-drivers had to drop back to -r2 to be able to use it
Pat and I are working in the background to see if we can resolve this issue.
what is the status of the work in background?
I'm now running on xorg-x11-6.7 with ati-drivers-3.12 and Celestia still crashes on load. Tried xorg-x11-6.8, but the xserver crashes with ati-drivers.
I can confirm this behaviour. My experience is that in the 6.8.0 pre-releases, the ATI drivers crashed on anything GL. Now, with the official 6.8.0 release, the commercial drivers do not work at all. The official versions supported by ATI are X 4.1.0-4.3.0 on RedHat EL and SuSe. Since these distributions won't be using X.org for at least another half-year, I don't know that we can be expected to have support. But I do hope that it's at least being considered in-house. You may be interested to know that the drivers included in X work pretty well on all the cards I've tried, though they have issues with things like Saturn's ring transparency and cloud maps.
*** Bug 48744 has been marked as a duplicate of this bug. ***
As bug 48744 has been marked as duplicate of this bug, here is the information about my seg fault (which happen with nvidia drivers, not ati). Could someone empowered to do so change the summary to reflect the merging of these two bugs (that is the fact that this happens with both ati and nvidia cards)? Copied from the other bug: I just tried to install celestia, and it also crashed here. I'm using: app-sci/celestia-1.3.2 x11-base/xorg-x11-6.7.0-r2 media-video/nvidia-glx-1.0.5336-r2 sys-libs/glibc-2.3.4.20040808 Here is the backtrace: [New Thread 1090223168 (LWP 24642)] nStars: 112524 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1090223168 (LWP 24642)] 0x080c50c3 in readGConfMain () (gdb) bt #0 0x080c50c3 in readGConfMain () #1 0xbffff1c0 in ?? () #2 0xbffff1c0 in ?? () #3 0x40012cc0 in _dl_argv () from /lib/ld-linux.so.2 #4 0x0815aa2d in typeinfo name for CelScriptWrapper () #5 0x080c5630 in loadSavedPreferences () #6 0x0815aa2c in typeinfo name for CelScriptWrapper () #7 0x00000000 in ?? () #8 0x087122c8 in ?? () #9 0x40012cc0 in _dl_argv () from /lib/ld-linux.so.2 #10 0x087122c8 in ?? () #11 0x0815b726 in typeinfo name for CelScriptWrapper () #12 0x080c614e in main () and some more info: charm ~ # emerge info Portage 2.0.50-r11 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.7-gentoo-r11) ================================================================= System uname: 2.6.7-gentoo-r11 i686 Intel(R) Pentium(R) M processor 1700MHz Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-Os -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-Os -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://mir.zyrianes.net/gentoo/ http://mirror.switch.ch/mirror/gentoo/ ftp://gentoo.inode.at/source/ http://ftp.ntua.gr/pub/linux/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 acpi acpi4linux alsa avi berkdb bonobo cdr crypt cups dga dvd dvdr encode esd evms2 foomaticdb gdbm gif gnome gtk gtk2 gtkhtml guile imlib java jpeg libg++ libwww linguas_en linguas_fr mad mikmod mmx mpeg ncurses nls nptl oggvorbis opengl oss palm pam pda pdflib perl png python quicktime readline sasl sdl slang spell sse ssl svg svga tcltk tcpd tetex truetype x86 xml2 xmms xv zlib"
Alan: the version you show your using for nvidia isnt current in tree i see up to 6111 try the latest version and see if that helps
I would prefer if this discussion was strictly ATI-related. The bugs are known to be reproducible on every ATI card I've tried. The nVidia drivers have no problems with Celestia. I see that what caused this crash is a lack of a proper make install. My hypothesis is that the gconf schema never got installed. It has nothing to do with your video card and should behave exactly the same if you were to run mesa instead of the proprietary nVidia driver. This is a known omission.
I tried upgrading to nvidia 6111 (which I avoid because of flickering issues with Neverwinter Nights) and it does work with it. Sorry for the noise.
Is this still an issue with 3.14.6?
yeap still seg faults bret@ghoststar bret $ celestia nStars: 112524 Initializing ARB vertex programs . . . Loading ARB vertex program: shaders/diffuse_arb.vp Segmentation fault
for those stuck with this bug but still wanting to play ether move or rm this file: /usr/share/celestia/shaders/diffuse_arb.vp it allowed it to load here the star field had a weird flickering effect but i could fly around at least pat: any kind of work around you could provide a patch or somethin? check for fgl and not use that file for the time being? it would be nice to be able to close this bug before its a year old...
I'll be honest, I dropped this bug since I need X.org to run smoothly on my machines and the ATI commercial drivers do not currently run on X.org. I will continue looking if this is still an issue with any release that runs on X.org. One of these will presumably be available soon. However, if you have an r200 card, you can use the drivers provided with the X.org server to use Celestia with hardware acceleration. They work perfectly except for a few little rendering (non-crashing) glitches.
http://bugs.gentoo.org/show_bug.cgi?id=78937 for those that havent tried it out yet after doing whats in that bug i do have celesita working cept for some odd flickering under the latest ati and xorg [ebuild R ] x11-base/xorg-x11-6.8.1.902 [ebuild R ] media-video/ati-drivers-8.8.25 are the versions i have installed at the moment
fyi turning off star rendering gets rid of the flickering for me
Yes, this is a bug that has cropped up in Windows as well over the last year or so. However, the bug is specifically about the segfault, which does appear to have been resolved in recent drivers.
looks like that is related to a problem in the libGL.la will be fixed either on opengl-update or in the 8.8.25-r1 and backported
Is the issue still valid?
i think its safe to finally close this bug
seems to be fixed with 8.8.25
