bug#59364: gnome clocks does not start due to missing libGLES.so

Hello, On Mon, Oct 09, 2023 at 01:31 AM, John Kehayias wrote: > On Sat, Oct 07, 2023 at 09:32 PM, Simon Streit wrote: > >> John Kehayias writes: >> >>> Is this the same issue as in ? With >>> potential fix ? I'm looking to >>>

bug#59364: gnome clocks does not start due to missing libGLES.so

On Sat, Oct 07, 2023 at 09:32 PM, Simon Streit wrote: > John Kehayias writes: > >> Is this the same issue as in ? With >> potential fix ? I'm looking to >> include this on the next mesa-updates round coming up soon. > > Yes, it

bug#59364: gnome clocks does not start due to missing libGLES.so

John Kehayias writes: > Is this the same issue as in ? With > potential fix ? I'm looking to > include this on the next mesa-updates round coming up soon. Yes, it is! I can only confirm this error on older Machines with older

bug#59364: gnome clocks does not start due to missing libGLES.so

Hi all, On Wed, Nov 30, 2022 at 09:47 PM, Simon Streit wrote: > Csepp writes: >> It does work with LIBGL_ALWAYS_SOFTWARE=1, but it would be pretty messed >> up if that had to be enabled globally. > > Thanks for that tip! > > I fired up a recent Fedora live image to see that these applications do

bug#59364: gnome clocks does not start due to missing libGLES.so

Csepp writes: > It does work with LIBGL_ALWAYS_SOFTWARE=1, but it would be pretty messed > up if that had to be enabled globally. Thanks for that tip! I fired up a recent Fedora live image to see that these applications do work in wayland on this old machine. Which they do. Gnome in Ferdora

bug#59364: gnome clocks does not start due to missing libGLES.so

Simon Streit writes: > Hello, > > Csepp writes: > >> This is the exact error: >> Couldn't open libGLESv2.so.2: libGLESv2.so.2: cannot open shared object >> file: No such file or directory > > I can confirm this error, though it only happens in wayland enabled > sessions on my old laptop with

bug#59364: gnome clocks does not start due to missing libGLES.so

Hello, Csepp writes: > This is the exact error: > Couldn't open libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: > No such file or directory I can confirm this error, though it only happens in wayland enabled sessions on my old laptop with an Intel GM965/GL960. This doesn't hap

bug#59364: gnome clocks does not start due to missing libGLES.so

This is the exact error: Couldn't open libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: No such file or directory (Yes, a clock application not starting because it needs OpenGL is... pretty weird indeed.)