Picom failed to get GLX context

TroubleClef · 2022-08-13 14:55:43

I'm using the picom-jonaburg-git AUR package on my installation with DWM, but I'm having a few issues that don't come up when I'm was previously using the regular picom package.

When I try running picom without root permissions it fails to start with the following output:

[ 08/13/22 10:23:35.771 parse_kawase_blur_strength INFO ] blur-strength: 7 [.iter = 3, .offset = 4.250000, .expand = 50]
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_SGI_video_sync.
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_SGI_swap_control.
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_OML_sync_control.
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_MESA_swap_control.
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_EXT_swap_control.
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_EXT_texture_from_pixmap.
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_ARB_create_context.
[ 08/13/22 10:23:35.847 glx_has_extension INFO ] Found GLX extension GLX_EXT_buffer_age.
[ 08/13/22 10:23:35.848 glx_init ERROR ] Failed to get GLX context.
[ 08/13/22 10:23:35.848 initialize_backend FATAL ERROR ] Failed to initialize backend, aborting...

When I launch picom with sudo transparency works at first, but none of the other changes like the blur or rounded corners work. Then, when any windows change or move it crashes with the following output:

x_set_picture_clip_region() has failed to allocate memory, at ../src/x.c:311. Aborting...
Aborted

If I change the back end in the config to xrender, picom launches alright and all the features work, but it lags the whole system and makes smears when resizing or moving windows.

Here's the output of picom --diagnostic:

[ 08/13/22 10:50:17.868 parse_kawase_blur_strength INFO ] blur-strength: 7 [.iter = 3, .offset = 4.250000, .expand = 50]
**Version:** vgit-e3c19

### Extensions:

* Shape: Yes
* XRandR: Yes
* Present: Present

### Misc:

* Use Overlay: Yes* Config file used: /home/marina/.config/picom.conf

### Drivers (inaccurate):

modesetting

I found a few posts with a similar issue but they were all either nvidia driver issues, or they didn't have a solution. I'm running a laptop that uses an intel cpu with built in graphics.

Does anyone have any possible solutions?

Lone_Wolf · 2022-08-13 17:16:32

Looks very similar to https://github.com/jonaburg/picom/issues/73 .

Since that poster uses arm and a broadcom video card, this doesn't seem to be hw or architeture specific.

Picom-jonaburg-git upstream would be best suited to investigate this.
Maybe you could add your findings to the issue report ?

Edit :
Welcome to archlinux forums.

Last edited by Lone_Wolf (2022-08-13 17:18:27)

seth · 2022-08-13 19:21:22

When I launch picom with sudo

Don't do that and make sure it didn't leave any root owned files behind in your $HOME

find $HOME -user root

Post the output of

glxinfo -B

and can you run "glxgears"? (from the mesa-demos package)

TroubleClef · 2022-08-13 19:58:27

Lone_Wolf wrote:

Maybe you could add your findings to the issue report ?

Oh I didn't see that issue before. I will definitely add my information when I have a chance later.
Thanks for that and for the welcome. I've lurked for a long time and that usually fixes my problems lol.

seth wrote:

Don't do that and make sure it didn't leave any root owned files behind in your $HOME

Don't worry, I know not to run it like this in normal use. I just did this to check for any permissions issues and it seems like that may be part of the problem. I did make sure to check for any file changes after testing.

Here is my glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics (ILK) (0x46)
    Version: 22.1.5
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    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 vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics (ILK)
OpenGL version string: 2.1 Mesa 22.1.5
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 2.0 Mesa 22.1.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

and glxgears runs just fine getting consistently 58-60 fps.

seth · 2022-08-13 20:14:49

    Max core profile version: 0.0
    Max compat profile version: 2.1

See if you've more luck w/ https://archlinux.org/packages/extra/x86_64/mesa-amber/ but if that version of picom requieres OpenGL 3.x, it's not gonna run on that HW.
You can try to "export MESA_GL_VERSION_OVERRIDE=3.3" but I'd not hold my breath.

Arch Linux

#1 2022-08-13 14:55:43

Picom failed to get GLX context

#2 2022-08-13 17:16:32

Re: Picom failed to get GLX context

#3 2022-08-13 19:21:22

Re: Picom failed to get GLX context

#4 2022-08-13 19:58:27

Re: Picom failed to get GLX context

#5 2022-08-13 20:14:49

Re: Picom failed to get GLX context

Board footer