A similar error occurs when one attempts to run evolution on a remote X Desktop. It seems there is a dependency on direct rendering which is not available in either the VNC or remote X windows environments.
Recreate with:
# ssh -X servername [where the server is running Ubuntu 18.04 Desktop]
# evolution
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libEGL warning: DRI2: failed to authenticate
(evolution:25704): Gdk-ERROR **: 06:48:35.588: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 207 error_code 1 request_code 153 (DRI2) minor_code 1)
(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)
A similar error occurs when one attempts to run evolution on a remote X Desktop. It seems there is a dependency on direct rendering which is not available in either the VNC or remote X windows environments.
Recreate with:
# ssh -X servername [where the server is running Ubuntu 18.04 Desktop]
# evolution
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libEGL warning: DRI2: failed to authenticate
(evolution:25704): Gdk-ERROR **: 06:48:35.588: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 207 error_code 1 request_code 153 (DRI2) minor_code 1)
(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)