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.)
Hello,
Csepp <raingloom@riseup.net> 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
happen on machines with modern graphics cards installed.
The list is longer for me on Gnome applications that will fail to start:
gnome-calculator, gnome-calendar, gnome-characters, gnome-clocks
gnome-contacts, gnome-font-viewer, etc.
Checkout is at 8f9588185d74f1f251b041b84d43302c337588ff.
Simon Streit <simon@netpanic.org> writes:
> Hello,
>
> Csepp <raingloom@riseup.net> 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
> happen on machines with modern graphics cards installed.
>
> The list is longer for me on Gnome applications that will fail to start:
>
> gnome-calculator, gnome-calendar, gnome-characters, gnome-clocks
> gnome-contacts, gnome-font-viewer, etc.
>
> Checkout is at 8f9588185d74f1f251b041b84d43302c337588ff.
It does work with LIBGL_ALWAYS_SOFTWARE=1, but it would be pretty messed
up if that had to be enabled globally.
Csepp <raingloom@riseup.net> 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 is already at 43.
Hi all, On Wed, Nov 30, 2022 at 09:47 PM, Simon Streit wrote: > Csepp <raingloom@riseup.net> 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 is already at 43. Is this the same issue as in <https://issues.guix.gnu.org/64981>? With potential fix <https://issues.guix.gnu.org/65375>? I'm looking to include this on the next mesa-updates round coming up soon. Thanks! John
John Kehayias <john.kehayias@protonmail.com> writes:
> Is this the same issue as in <https://issues.guix.gnu.org/64981>? With
> potential fix <https://issues.guix.gnu.org/65375>? 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
graphics cards. The newer ones are okay.
--
Simon
On Sat, Oct 07, 2023 at 09:32 PM, Simon Streit wrote:
> John Kehayias <john.kehayias@protonmail.com> writes:
>
>> Is this the same issue as in <https://issues.guix.gnu.org/64981>? With
>> potential fix <https://issues.guix.gnu.org/65375>? 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
> graphics cards. The newer ones are okay.
Thanks for confirming, hope to have the fix on mesa-updates and merged
soon. Soon depending on the next mesa point release and building the
branch.
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 <john.kehayias@protonmail.com> writes:
>>
>>> Is this the same issue as in <https://issues.guix.gnu.org/64981>? With
>>> potential fix <https://issues.guix.gnu.org/65375>? 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
>> graphics cards. The newer ones are okay.
>
> Thanks for confirming, hope to have the fix on mesa-updates and merged
> soon. Soon depending on the next mesa point release and building the
> branch.
And forgot to update/close this bug after mesa-updates was merged, with
37fc2c99e0067dfd669526c61dc10d014b89c08b the relevant commit.
John