MX Linux Forum

and I am also going to suggest that you do another update.

Hi Charles,

I just ran the MX Cleanup with the setting suggested in both of my laptops, but the issue continues after rebooting them.

Charles,

I ran the MX Cleanup with the suggested settings in both of my laptops, the the issue continues after rebooting them.

I also updated both of my laptops with 6 new updates after checking for updates, but the issue continues after rebooting them.

Hi @VitalM

Plz post the output of the terminal commands on the two laptops ... Try the following terminal command to start evolution on the two non working laptops ... HTH, greetz l0dr3

Dear l0dr3,

Here is the terminal output after typing the first command (glxinfo |grep -i profile) on my Dell Inspiron E1505:

VitalMiranda@mx-Inspiron-E1505:~
$ glxinfo |grep -i profile
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 23.1.2-1~mx23ahs
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:
VitalMiranda@mx-Inspiron-E1505:~
$

And here is the terminal output for my Dell Inspiron 1501

VitalMiranda@mx-Inspiron-1501:~
$ glxinfo |grep -i profile
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 23.1.2-1~mx23ahs
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:
VitalMiranda@mx-Inspiron-1501:~
$

Wow! l0dr3,

The second command (MESA_GL_VERSION_OVERRIDE=4.5 evolution) did indeed launched the evolution app in both of my laptops, but with some warning and critical notifications. But they appear to be working fine. Nonetheless, after closing the application, the issue continues if I try to launch it from the Applications Menu.

Thanks a million for giving an alternative method to launch Evolution!

@VitalM

Here is the terminal output after typing the first command (glxinfo |grep -i profile) on my Dell Inspiron E1505:
:
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 23.1.2-1~mx23ahs

And here is the terminal output for my Dell Inspiron 1501
:
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 23.1.2-1~mx23ahs

Thats what i expected: your older 'radeon' drivers does not report a suitable high 'MESA_GL' core or compat profile version to the updated MESA framework
You may try to find/use some newer graphic card drivers for your two older Laptops ...

Nonetheless, after closing the application, the issue continues if I try to launch it from the Applications Menu.

... otherwise, if evolution (or other SW thats affected by this issue, e.g.: most wine-started windows programs) run fine with the environment override set to 4.5:

Option1: change the desktop launchers 'exec' statement by prepending the override
Option2: try to make that override permanent at least in your user sessions by adding, e.g.: in ~/.bashrc

good luck, greetz l0dr3

Thanks a lot l0dr3 for the valuable information. I greatly appreciate it.

I would really like to apply Option1, which seems to be the most simple task to perform, but how do I go about changing the desktop launchers 'exec' statement? Could you please walk me through?

Thanks again for all the help!