gnome clocks does not start due to missing libGLES.so

  • Done
  • quality assurance status badge
Details
3 participants
  • John Kehayias
  • Csepp
  • Simon Streit
Owner
unassigned
Submitted by
Csepp
Severity
normal
C
(name . Bug reports for GNU Guix)(address . bug-guix@gnu.org)
87y1s8chuh.fsf@riseup.net
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.)
S
S
Simon Streit wrote on 30 Nov 2022 08:08
(name . Csepp)(address . raingloom@riseup.net)(address . 59364@debbugs.gnu.org)
ygusfi0ex7t.fsf@netpanic.org
Hello,

Csepp <raingloom@riseup.net> writes:

Toggle quote (3 lines)
> 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.
C
(name . Simon Streit)(address . simon@netpanic.org)
87iliw8k5f.fsf@riseup.net
Simon Streit <simon@netpanic.org> writes:

Toggle quote (18 lines)
> 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.
S
S
Simon Streit wrote on 30 Nov 2022 21:47
(name . Csepp)(address . raingloom@riseup.net)(address . 59364@debbugs.gnu.org)
ygu1qpkb25m.fsf@netpanic.org
Csepp <raingloom@riseup.net> writes:
Toggle quote (3 lines)
> 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.
J
J
John Kehayias wrote on 6 Oct 2023 17:41
(name . Simon Streit)(address . simon@netpanic.org)
875y3jahcc.fsf@protonmail.com
Hi all,

On Wed, Nov 30, 2022 at 09:47 PM, Simon Streit wrote:

Toggle quote (11 lines)
> 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
S
S
Simon Streit wrote on 7 Oct 2023 21:32
(name . John Kehayias)(address . john.kehayias@protonmail.com)
ygupm1q1b50.fsf@netpanic.org
John Kehayias <john.kehayias@protonmail.com> writes:

Toggle quote (4 lines)
> 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
J
J
John Kehayias wrote on 9 Oct 2023 03:31
(name . Simon Streit)(address . simon@netpanic.org)
87msws8ttk.fsf@protonmail.com
On Sat, Oct 07, 2023 at 09:32 PM, Simon Streit wrote:

Toggle quote (9 lines)
> 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.
J
J
John Kehayias wrote on 20 Feb 04:33 +0100
(name . Simon Streit)(address . simon@netpanic.org)
87wmqz95d5.fsf@protonmail.com
Hello,

On Mon, Oct 09, 2023 at 01:31 AM, John Kehayias wrote:

Toggle quote (15 lines)
> 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
Closed
?