On 06/08/14 17:08, Alexander Wolf wrote:
> >
> > > Thanks a lot for this!
> > > However, this is VERY weird since in theory stellarium 0.13 uses Qt5!
> > > Moreover, as I just checked, on some architectures libqt4-opengl is
> > > installed as a dependency, but not on amd64:
> > > https://packages.debian.org/sid/stellarium
> > >
> > > Why would a Qt5 application require Qt4 libraries in the case
> > > of your bug escapes me... Moreover, I've just removed libqt4-opengl
> > > from my system and stellarium works hapilly anyway, so it is
> > > probably still linked to your particular configuration. Is your
> > > previous bug still reproducible, even if you remove libqt4-opengl
> > > now? Maybe you did something also as well?
> > >
> > > Tomasz
> >
> > Hi Tomasz,
> >
> > Yes now, I removed libqt4-opengl and stellarium starts normally
> >
> >
> Hm. Looks like some opengl library did not installed - why? Has debian a
> separate library for shaders support?

Hi,
I don't think there is a special shader library. I've just installed
a clean jessie and sid chroots and installed stellarium 0.13.0-2 inside them.
It worked perfectly in both cases.
Considering that Davide has stellarium working now, I think it was some
kind of interference between packages coming from 
unstable/testing/deb-multimedia.org.
As I said before, I'll drop the severity of this bug and keep it open for
more or less 2 weeks unless somebody will hit the problem again.

Tomasz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to