GNU bug report logs - #59364
gnome clocks does not start due to missing libGLES.so

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: John Kehayias <john.kehayias <at> protonmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#59364: closed (gnome clocks does not start due to missing
 libGLES.so)
Date: Tue, 20 Feb 2024 03:35:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 20 Feb 2024 03:33:48 +0000
with message-id <87wmqz95d5.fsf <at> protonmail.com>
and subject line Re: bug#59364: gnome clocks does not start due to missing libGLES.so
has caused the debbugs.gnu.org bug report #59364,
regarding gnome clocks does not start due to missing libGLES.so
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
59364: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59364
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Csepp <raingloom <at> riseup.net>
To: Bug reports for GNU Guix <bug-guix <at> gnu.org>
Subject: gnome clocks does not start due to missing libGLES.so
Date: Fri, 18 Nov 2022 17:52:30 +0100

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.)

[Message part 3 (message/rfc822, inline)]

From: John Kehayias <john.kehayias <at> protonmail.com>
To: Simon Streit <simon <at> netpanic.org>
Cc: 59364-done <at> debbugs.gnu.org, Csepp <raingloom <at> riseup.net>
Subject: Re: bug#59364: gnome clocks does not start due to missing libGLES.so
Date: Tue, 20 Feb 2024 03:33:48 +0000

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 <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.