Known issues in Stellarium 0.10.2
This page lists bugs and other issues specific to Stellarium 0.10.2 that are known to the community and/or the development team. The purpose of this list is to provide solutions and information about common problems, please report new bugs to the bug tracker.
It looks like this is a video card driver issue. If youo have this problem, please add your details to this list so we can get a picture of what is going on:
|OS||Video Card||Driver version||Notes|
|???||ATI Radeon X300/X550/X1050 Series, RAM 128 MBytes||???||Details from astrohobby's forum post|
|Vista 64||ATI||???||jose1dav's forum post|
Description: Pressing the Stop button in the Configuration/Scripts dialog causes Stellarium to freeze. Reported on Windows XP and Vista.
- Feedback forum - problem in 0.10.1
- Bug ID 2571821 - Windows XP, 0.10.1: Stopping a script freezes Stellarium
Status: Fixed in development code.
Solution: Use development version, or wait for next release (sorry!). We fixed it only just after the freeze for 0.10.2.
There is no Text User Interface (TUI)
Description: The TUI feature (used in planetariums) is not present in versions from 0.10.0 (beta) to 0.10.2. According to Fabien Chéreau, this feature should be recoded as a plugin. (source) As of March 2009, there is a development version of the plugin in the SVN repository (link).
- Feedback forum - 0.10.1 not functionally for use in planetariu
- Bug ID 2622956 - No TUI on "m" keypress
Dialog windows are rendered incorrectly (ATI video cards)
Description: Some of Stellrarium's dialog windows (i.e. the ones accessible through the left menu) are rendered incorrectly, making them unreadable. (The effect has been described as "out of phase"; see the links below for screenshots.) This issue seems to be limited to computers that use ATI graphics cards.
- Feedback forum - Left mau is...
- Bug ID 2684199 - Menus rendered incorrectly (screenshot)
- Bug ID 2688541 - Dialog boxes appear out of phase (screenshot)
Solution: Update your graphics card drivers. Several users have reported that this fixed the problem.