On Intel video card don't show stars, config toolbar broken

Bug #507364 reported by zordsdavini
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
stellarium (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: stellarium

In 9.10 ubuntu I had problems with config windows as it was shown broken (Intel video card), now I dont see any stars. I guess it depends on qt4.6
I really need this program, please, ask any questions or make tasks.

Revision history for this message
zordsdavini (zordsdavini) wrote :

Stellarium window

Revision history for this message
Bogdan Marinov (daggerstab) wrote :

If you are trying to run Stellarium 0.10.2 on Ubuntu 10.04 (Lucid Lynx), please have in mind that Lucid is still an alpha version. Yes, Lucid includes the Qt 4.6 libraries, and yes, it seems that there are some problems, either with the Intel drivers, the Mesa library or the Qt libraries.

If you are running Karmic Koala (Ubuntu 9.10) and you have upgraded somehow Qt or Mesa, I suggest you roll them back to the previous version.

Revision history for this message
zordsdavini (zordsdavini) wrote :

I'm running Ubuntu 10.04 and problem still exists.

Revision history for this message
zordsdavini (zordsdavini) wrote :

svn version (0.10.3) works fine on 10.04 (tested from build directory). A little bit slowly but good. I guess Ubuntu needs new version and everything will be fine.

Revision history for this message
Wolfgang Kufner (wolfgangkufner) wrote :

Hi zordsdavini

Good to hear that the svn version of stellarium works on lucid.
I just want to mention that stellarium also works with intel graphics on karmic when using the graphics drivers form xorg-edgers ppa. This fixes Bug #426417 which fits the description of the problems in 9.10 in your original report.

I did some testing with the normal stellarium package in lucid with intel graphics. It always shows this bug 507364 here.
Tested with:
standard graphics drivers
xorg-edgers graphics drivers
LIBGL-ALWAYS-SOFTWARE=1 stellarium
This means that intels mesa driver is very likely not the culprit.

Moreover comparison of screenshots with bug 480553 shows identical corruption. I think this is the same bug, therefore I will set this bug here as a duplicate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.