After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 766421 - GLXBadContext abort under gtk_clutter_init_with_args() (NVidia based machine)
GLXBadContext abort under gtk_clutter_init_with_args() (NVidia based machine)
Status: RESOLVED OBSOLETE
Product: clutter-gtk
Classification: Platform
Component: general
1.8.x
Other Linux
: Normal critical
: ---
Assigned To: clutter-gtk maintainer(s)
clutter-gtk maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-05-14 09:56 UTC by Robert Fox
Modified: 2021-06-10 11:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Dump output of debug (9.10 KB, text/plain)
2016-05-17 11:37 UTC, Robert Fox
Details
Second dump with more debuginfos loaded (5.92 KB, text/plain)
2016-05-17 11:53 UTC, Robert Fox
Details

Description Robert Fox 2016-05-14 09:56:26 UTC
[rfox@foxmain ~]$ rpm -qa | grep evolution
evolution-data-server-3.20.2-1.mga6
evolution-3.20.2-1.mga6

Using Mageia Cauldron - NVidia based machine - created bug with Mageia with no progress - have to use Thunderbird!

https://bugs.mageia.org/show_bug.cgi?id=17500


[rfox@foxmain ~]$ evolution 
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast

(evolution:22675): Gdk-ERROR **: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 183 error_code 167 request_code 153 (GLX) minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
Comment 1 Milan Crha 2016-05-16 14:10:35 UTC
Thanks for a bug report. From "it crashed" is really hard to know what happened there. Could you install debuginfo packages for at least gtk3, evolution-data-server and evolution, and then follow the instructions from the error message itself, to get something useful to start with, please? The command used can be:
   $ GDK_SYNCHRONIZE=1 gdb evolution --ex "b gdk_x_error" --ex r --ex bt --ex q

which will run the evolution under gdb as described in the error message and will print the backtrace when the function is reached, then it'll quit the gdb. Copy the backtrace to a file, like bt.txt. Please check the bt.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only).

The referenced mageia bug report mentions also rhytmbox. I'm wondering whether this has anything to do with clutter, where the clutter support is rather limited in the evolution itself, though it can be compiled with it. Maybe install debugging information for the clutter too.

I do not understand the error "GLXBadContext", but I'd guess from it that there was some issue with a 3D rendering, which is usually not needed in the evolution, because it's a desktop application. The 3D rendering is used by the above mentioned clutter. I would guess that there is some issue with the video card driver.
Comment 2 Robert Fox 2016-05-17 11:25:12 UTC
YES - the original bug covered Evolution & Rhythmbox (which now works on same machine) - Evolution still gives the error (and there have been many updates on Mageia Cauldron since the original bug was filed!)

Let me try the debuginfo and see how far I can get - I will report back.
If this was a videocard issue, why does everything else work on it (under Gnome & Plasma) except Evolution??
Comment 3 Robert Fox 2016-05-17 11:37:32 UTC
Created attachment 328064 [details]
Dump output of debug

Using suggested command line in post #2
Comment 4 Robert Fox 2016-05-17 11:43:23 UTC
MY BAD - need to install more debuginfo files to cover more stuff - will be back with a more comprehensive debug file
Comment 5 Robert Fox 2016-05-17 11:53:41 UTC
Created attachment 328066 [details]
Second dump with more debuginfos loaded

Not much more to add from the last one . . .
Comment 6 Milan Crha 2016-05-17 14:00:03 UTC
(In reply to Robert Fox from comment #2)
> If this was a videocard issue, why does everything else work on it (under
> Gnome & Plasma) except Evolution??

Thanks for the update. I see from the backtraces that the crash is inside gtk_clutter_init_with_args(), thus in the clutter library. It can be that the other software you use doesn't use clutter at all.

I'm moving this bug to the clutter-gtk project for further investigation.
Comment 7 Milan Crha 2016-05-17 14:03:35 UTC
I forgot to add, one option for the evolution would be to build it without the clutter support, which means:

   $ ./configure --disable-contact-maps ...

which brings in the clutter-gtk.
Comment 8 Robert Fox 2016-05-17 14:29:30 UTC
Thanks - Seeing as I did not build this package myself (comes from prebuilt Cauldron Mageia packages) -  I'll have to turn to the package owner.  Maybe there is something from the clutter-gtk project which helps.  This seems to be in relation to the NVidia proprietary drivers, because same build works under laptop with Intel chipset

Thx,
R.Fox
Comment 9 Robert Fox 2016-05-30 10:04:59 UTC
Any movement on this bug?? I'm trying to get Mageia packagbe owner to look at this issue . . .
Comment 10 Emmanuele Bassi (:ebassi) 2016-05-30 10:10:27 UTC
Sorry, but I cannot reproduce this issue because I don't have a Mageia installation on an nVidia machine (the only nVidia machine I have uses Ubuntu and does not exhibit this crash).

The issue seems to be that Cogl or Clutter are trying to load the swrast driver from Mesa, which means they are not using the nVidia libGL. This may point to some installation issue with the nVidia binary blob driver, or with a build issue of Cogl.
Comment 11 André Klapper 2021-06-10 11:17:55 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of clutter-gtk, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a ticket at
  https://gitlab.gnome.org/GNOME/clutter-gtk/-/issues/

Thank you for your understanding and your help.