Bug#894144: libmutter-2.so.0: undefined symbol: glFramebufferTexture2D

[Simon McVittie]

Thanks for splitting this out to a separate bug.

On Mon, 26 Mar 2018 at 14:52:03 -0400, Christopher Sasarak wrote:
> This also happened inside a VirtualBox session

In the bug you reported, there are syslog entries from a machine named
"shelby". What is that machine? VirtualBox, or real hardware, or what?

> I will try to check my home machine which is not a virtual machine
> later tonight. To see if the same problem exists there.

Please answer the questions below for each differently-configured machine
where you see this bug.

If GNOME Shell crashes in a different way (without the symbol lookup
error for glFramebufferTexture2D), please report that as a separate bug,
and not as part of this one.

> Mar 26 12:20:36 shelby org.gnome.Shell.desktop[1451]: /usr/bin/gnome-shell: symbol lookup error: /usr/lib/x86_64-linux-gnu/libmutter-2.so.0: undefined symbol: glFramebufferTexture2D

What graphics hardware do you have?

Which 3D driver (libGL implementation) are you using? (NVIDIA
proprietary? Mesa? fglrx? Virtualbox precompiled guest driver? etc.)

> Mar 26 12:20:36 shelby org.gnome.Shell.desktop[1472]: /usr/bin/gnome-shell: symbol lookup error:
> /usr/lib/x86_64-linux-gnu/libmutter-2.so.0: undefined symbol: glFramebufferTexture2D

If you run this command:

ldd /usr/lib/x86_64-linux-gnu/libmutter-2.so.0

what do you get?

Thanks,
    smcv