GNU bug report logs -
#59364
gnome clocks does not start due to missing libGLES.so
Previous Next
Reported by: Csepp <raingloom <at> riseup.net>
Date: Fri, 18 Nov 2022 17:08:02 UTC
Severity: normal
Done: John Kehayias <john.kehayias <at> protonmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 59364 in the body.
You can then email your comments to 59364 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#59364
; Package
guix
.
(Fri, 18 Nov 2022 17:08:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Csepp <raingloom <at> riseup.net>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 18 Nov 2022 17:08:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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.)
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59364
; Package
guix
.
(Wed, 30 Nov 2022 07:09:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 59364 <at> debbugs.gnu.org (full text, mbox):
Hello,
Csepp <raingloom <at> 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.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59364
; Package
guix
.
(Wed, 30 Nov 2022 16:48:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 59364 <at> debbugs.gnu.org (full text, mbox):
Simon Streit <simon <at> netpanic.org> writes:
> Hello,
>
> Csepp <raingloom <at> 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.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59364
; Package
guix
.
(Wed, 30 Nov 2022 20:48:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 59364 <at> debbugs.gnu.org (full text, mbox):
Csepp <raingloom <at> 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.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59364
; Package
guix
.
(Fri, 06 Oct 2023 15:43:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 59364 <at> debbugs.gnu.org (full text, mbox):
Hi all,
On Wed, Nov 30, 2022 at 09:47 PM, Simon Streit wrote:
> Csepp <raingloom <at> 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
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59364
; Package
guix
.
(Sat, 07 Oct 2023 19:34:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 59364 <at> debbugs.gnu.org (full text, mbox):
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.
--
Simon
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59364
; Package
guix
.
(Mon, 09 Oct 2023 01:33:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 59364 <at> debbugs.gnu.org (full text, mbox):
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.
Reply sent
to
John Kehayias <john.kehayias <at> protonmail.com>
:
You have taken responsibility.
(Tue, 20 Feb 2024 03:35:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Csepp <raingloom <at> riseup.net>
:
bug acknowledged by developer.
(Tue, 20 Feb 2024 03:35:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 59364-done <at> debbugs.gnu.org (full text, mbox):
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
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 19 Mar 2024 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 51 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.