Light rays inhibit visibility into Stellarium and others aplications

[fabianbur]

Light rays inhibit visibility into Stellarium.
Also visible in Google maps on Firefox and Chromium and cutegram

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: stellarium 0.14.2-1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 19 19:09:49 2016
ProcEnviron:
 LANGUAGE=es_EC:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_EC.UTF-8
 SHELL=/bin/bash
SourcePackage: stellarium
UpgradeStatus: No upgrade log present (probably fresh install)

[fabianbur (fabianbur)]

I tried uninstalling completely beignet and the problem is solved, however Boinc is not detecting OpenCL if beignet is uninstalled.
It is important to install beignet, but that does not cause these unwanted effects on other programs

[Rebecca Palmer (rebecca-palmer)]

I can't reproduce this (stellarium + an OpenCL-using Python script).

What hardware are you using? ( xrandr --listproviders ; lspci -nn | grep -e "\[03..\]:" )
Does OpenCL work?
Does the bug only happen if beignet is being used at the time, or is it enough for it to be installed?

[fabianbur (fabianbur)]

Thanks rebecca-palmer

Yes, OpenCL work

Reproduction was simply:

sudo apt install clinfo beignet

and open stellarium or google maps

Beignet was uninstalled because it was impossible to see google maps or stellarium. You are seeing this message again and now I installed works perfect. I do not know how update was fixed, but not by reporting this bug, because until now there was no developer assigned. Thanks again for your interest, but later.
I will mark the bug as fixed.

La reproducción era simplemente:

sudo apt install beignet clinfo

y abrir stellarium o google maps

Tenía beignet desinstalado porque era imposible ver google maps ni stellarium. Al ver este mensaje lo he instalado nuevamente y ahora trabaja perfecto. Desconozco con qué actualización fue arreglado, pero no fue mediante el reporte de este bug, debido a que hasta este momento no había ningún desarrollador asignado. Gracias nuevamente por interesarse, aunque tarde.
Marcaré el bug como arreglado.