Hide Forgot
abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: stellarium component: stellarium crash_function: cs_gem_write_reloc executable: /usr/bin/stellarium kernel: 2.6.35.6-45.fc14.i686 package: stellarium-0.10.6-1.fc14 rating: 4 reason: Process /usr/bin/stellarium was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1306160292 uid: 500 comment ----- I ran the Stellarium installer immediately after installing the Fedora LXDE version 14 operating system. There are 15 dependencies the installer does not install but requires. The list follows: Core X11 protocol library GNU standard C++ library Monospace sans-serif font library X.Org11 SM runtime library GCC ver. 4.5 shared support library Mesa libGL runtime library & DRI drivers X.Org X11 libXext runtime library ZLib compression / decompression library X.Org X11 ICE runtime library Variable width sans-serif font faces QT toolkit The GNU libC libraries Utils to check for proper 3D support before launching 3D games Mesa libGLU runtime library I realize most operating systems will already have had these packages installed but your installer should check them before proceeding with this install. How to reproduce ----- 1.When I attempt to open "Stellarium" from the main menu after it was successfully installed it immediately displays the crash warning. The installer posted no errors. 2. 3.
Created attachment 500498 [details] File: backtrace
After reviewing the dependencies, I found that all of them are present on this machine.
I have successfully installed and run version 0.10.2 of Stellarium on a Ubuntu workstation running version 9.10 if this helps diagnose the problem.
Backtrace analysis of bugs across components suggests the actual bug is in component mesa or libdrm instead of component stellarium, reassigning to mesa. Bugs which were found to be similar to this bug: mesa: bug #652797 supertux: bug #662268 This comment is automatically generated.
*** Bug 652797 has been marked as a duplicate of this bug. ***
*** Bug 662268 has been marked as a duplicate of this bug. ***