Celestia 1.3.1 RPM randomly freezes Suse 9.1. Prof

Report bugs, bug fixes and workarounds here.
Topic author
Viciarg
Posts: 5
Joined: 21.06.2004
With us: 20 years 5 months
Location: Northern Germany

Celestia 1.3.1 RPM randomly freezes Suse 9.1. Prof

Post #1by Viciarg » 25.10.2004, 07:52

As the topic says, Celestia randomly freezes the whole system, so nothing works except the reset button. Are there any error-logfiles or similar which could contain some information about what happened?
Humanas actiones non ridere, non lugere, neque detestari; sed intellegere curavi. (Spinoza)

Topic author
Viciarg
Posts: 5
Joined: 21.06.2004
With us: 20 years 5 months
Location: Northern Germany

Post #2by Viciarg » 25.10.2004, 09:35

When I quit Celestia normally, it crashes with Sigsev 11:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1101579584 (LWP 4187)]
[KCrash handler]
#7 0x4043aefa in KAction::containerCount () from /opt/kde3/lib/libkdeui.so.4
#8 0x4024c090 in KBookmarkBar::clear () from /opt/kde3/lib/libkio.so.4
#9 0x40251010 in KBookmarkBar::~KBookmarkBar () from /opt/kde3/lib/libkio.so.4
#10 0x40b8e6d2 in QWidget::~QWidget () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40c4f009 in QMainWindow::~QMainWindow ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x405221e0 in KMainWindow::~KMainWindow () from /opt/kde3/lib/libkdeui.so.4
#13 0x080a050b in KdeApp::~KdeApp ()
#14 0x08144e84 in VTT for KdeApp ()
#15 0x00000195 in ?? ()
#16 0x40fbec20 in __JCR_LIST__ () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x081eb518 in ?? ()
#18 0x08a579f8 in ?? ()
#19 0x40fbec20 in __JCR_LIST__ () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40b547bc in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x40b8937f in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40c4d362 in QMainWindow::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40af240f in QApplication::internalNotify ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x40af3fb9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x407abd5e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#26 0x40af3250 in QApplication::sendPostedEvents ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x40b0a0c1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x40b09eb6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x40af3e8f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x0809558b in main ()
Humanas actiones non ridere, non lugere, neque detestari; sed intellegere curavi. (Spinoza)

Avatar
t00fri
Developer
Posts: 8772
Joined: 29.03.2002
Age: 22
With us: 22 years 7 months
Location: Hamburg, Germany

Post #3by t00fri » 25.10.2004, 10:54

You did not tell us what graphics card you use and what driver number. Thats the crucial issue.

I am using SuSE 9.1. on several machines without the slightest problems in case of NVIDIA cards. On my machine with an ATI 9200SE in the office,however, the celestia-1.3.1 from SuSE 9.1 just produces a runtime crash as you describe.

These are familiar bugs in the ATI drivers for Linux, /unrelated/ to celestia's code. This has been analyzed in detail. ATI drivers are unfortunately quite "renowned" for driver bugs...

There is an (unsatisfactory) workaround which needs a recompilation in my case of the 9200SE, at least. Only the 'multitexture' render path works in this case, no specular lights, no bump mapping, no ring shadows on Saturn etc...

Nevertheless, you might try to uncomment the line

IgnoreGLExtensions [ "GL_ARB_vertex_program" ]

in 'celestia.cfg' and watch whether the crash goes away. In case of my
ATI 9200SE, I need this AND a patch in the code.

Bye Fridger

Topic author
Viciarg
Posts: 5
Joined: 21.06.2004
With us: 20 years 5 months
Location: Northern Germany

Post #4by Viciarg » 25.10.2004, 21:27

Thanks for your answer...I use a nvidia Geforce 4 MX 440...The OpenGL-Info in Celestia says the following about the driver:

Vendor : NVIDIA Corporation
Renderer : GeForce4 MX 440/AGP/SSE/3DNOW!
Version : 1.4.1 NVIDIA 53.36
Max simultaneous textures: 2
Max texture size: 2048

Supported Extensions:
GL_ARB_imaging
GL_ARB_multitexture
GL_ARB_point_parameters
GL_ARB_point_sprite
GL_ARB_texture_compression
GL_ARB_texture_cube_map
GL_ARB_texture_env_add
GL_ARB_texture_env_combine
GL_ARB_texture_env_dot3
GL_ARB_texture_mirrored_repeat
GL_ARB_transpose_matrix
GL_ARB_vertex_buffer_object
GL_ARB_vertex_program
GL_ARB_window_pos
GL_S3_s3tc
GL_EXT_texture_env_add
GL_EXT_abgr
GL_EXT_bgra
GL_EXT_blend_color
GL_EXT_blend_minmax
GL_EXT_blend_subtract
GL_EXT_clip_volume_hint
GL_EXT_compiled_vertex_array
GL_EXT_draw_range_elements
GL_EXT_fog_coord
GL_EXT_multi_draw_arrays
GL_EXT_packed_pixels
GL_EXT_paletted_texture
GL_EXT_point_parameters
GL_EXT_rescale_normal
GL_EXT_secondary_color
GL_EXT_separate_specular_color
GL_EXT_shared_texture_palette
GL_EXT_stencil_wrap
GL_EXT_texture_compression_s3tc
GL_EXT_texture_cube_map
GL_EXT_texture_edge_clamp
GL_EXT_texture_env_combine
GL_EXT_texture_env_dot3
GL_EXT_texture_filter_anisotropic
GL_EXT_texture_lod
GL_EXT_texture_lod_bias
GL_EXT_texture_object
GL_EXT_vertex_array
GL_IBM_rasterpos_clip
GL_IBM_texture_mirrored_repeat
GL_KTX_buffer_region
GL_NV_blend_square
GL_NV_fence
GL_NV_fog_distance
GL_NV_light_max_exponent
GL_NV_packed_depth_stencil
GL_NV_pixel_data_range
GL_NV_point_sprite
GL_NV_register_combiners
GL_NV_texgen_reflection
GL_NV_texture_env_combine4
GL_NV_texture_rectangle
GL_NV_vertex_array_range
GL_NV_vertex_array_range2
GL_NV_vertex_program
GL_NV_vertex_program1_1
GL_NVX_ycrcb
GL_SGIS_generate_mipmap
GL_SGIS_multitexture
GL_SGIS_texture_lod
GL_SUN_slice_accum


Since I didn't found any other info on my nvidia-drivers (except that I have nvidia-installer 1.0.6) I hope that's the correct one...
Humanas actiones non ridere, non lugere, neque detestari; sed intellegere curavi. (Spinoza)

Avatar
t00fri
Developer
Posts: 8772
Joined: 29.03.2002
Age: 22
With us: 22 years 7 months
Location: Hamburg, Germany

Post #5by t00fri » 25.10.2004, 21:44

As you can read in your OpenGL output, you have driver #5336, which is not too old. The current one for SuSE 9.1 is #6111.

Did you check whether 'ldd celestia' finds all libs? Did you install the textures that may be in a separate package??

I am compiling Celestia on a daily basis from CVS, and have not tried the SuSE 9.1 version 1.3.1 myself. I have packaged 1.3.1 for > SuSE 8.x on Sourceforge, but that will also die in your case, since it is compiled with the incompatible gcc <3.1.

Sorry, I can't help you any further, except with the "encouraging" statement that I have no problems whatsoever with any Celestia version and my NVIDIA cards under SuSE 9.1.

Good luck

Bye Fridger

Topic author
Viciarg
Posts: 5
Joined: 21.06.2004
With us: 20 years 5 months
Location: Northern Germany

Post #6by Viciarg » 25.10.2004, 21:57

t00fri wrote:


I have packaged 1.3.1 for > SuSE 8.x on Sourceforge, but that will also die in your case, since it is compiled with the incompatible gcc <3.1.


These were the RPMs I used.../me = stupid, right?

Edit: Nur f???rs Protokoll: Uncommenting the said line in celestia.cfg didn't work either.
Humanas actiones non ridere, non lugere, neque detestari; sed intellegere curavi. (Spinoza)

Avatar
t00fri
Developer
Posts: 8772
Joined: 29.03.2002
Age: 22
With us: 22 years 7 months
Location: Hamburg, Germany

Post #7by t00fri » 25.10.2004, 22:39

Viciarg wrote:
t00fri wrote:


I have packaged 1.3.1 for > SuSE 8.x on Sourceforge, but that will also die in your case, since it is compiled with the incompatible gcc <3.1.

These were the RPMs I used.../me = stupid, right?

Edit: Nur f???rs Protokoll: Uncommenting the said line in celestia.cfg didn't work either.


Well then this case is solved!

You should install as soon as possible the Celestia-1.3.1 package from SuSE 9.1 or --which has many advantages--install Celestia-1.3.2 by compiling it yourself. The sources are at Sourceforge.
You must carefully install all needed header packages, i.e in SuSE terminology the respective *-devel*.rpm packages!

There are many great improvements between 1.3.1 and 1.3.2 and CVS...and the CVS version is completely stable.

Clearly, for your NVIDIA card, uncommenting the line in celestia.cfg has no positive effects. So forget about it.
It's at best needed for ATI cards. Since you forgot originally to tell us your card, I invested this extra work, just "in case"...

Bye Fridger


Return to “Bugs”