glx bad context

[krompus]

I have been running compton successfully for months now without issue, until recently. I have traced the issue to the -b flag (indeed, it mentions "Causes issues with certain drivers" in the manpage.)

It used to work with the -b flag, but now I have to run it without. I get this error:

[     0.05 ] error  169 Unknown      request  154 minor    5 serial    849:   "GLXBadContext" fork_after(): Failed to make GLX context current. 

[     0.05 ] error  169 Unknown      request  154 minor    4 serial   1041: "GLXBadContext" main(): Failed to create new session.

The issue seems to be in my config file, as compton runs without my config (albeit with some weird glitches when dragging transparent windows on top of others, which doesn't happen when I use my config).

When I don't have the -b flag, it works well. So, I'm wondering how I can troubleshoot this issue. Thanks!

[tjblackheart]

Same issue here. I am runing compton v0.1_beta2.5 on Arch Linux with nvidia-361.28. I suppose this issue is probably related to libglvnd as compton -b works perfectly fine when libglvnd is downgraded to 0.0.0.20160210-2.

[JacquesToerien]

Confirmed same issue with beta2.5, nvidia 361.28 drivers. Arch Linux fresh install as of yesterday with full system update.

[cinder1992]

Can also confirm this issue, using this config and the nvidia 361.28 drivers, running with compton -CG does not result in this crash.

[cinder1992]

A temporary workaround for me at least is to change my .xsession line from compton -CGb --config ~/.config/compton.conf to compton -CG --config ~/.config/compton.conf &

This does not result in the GLX crash.

[CodeMonkey80s]

I have the same issue (Nvidia) :

nvidia-settings:  version 364.16  (buildmeister@swio-display-x64-rhel04-17)  Fri Apr  8 08:51:37 PDT 2016

michal@blackhole ~ $ compton -b
[     0.17 ] error 169 (Unknown) request 155 minor 5 serial 869 ("GLXBadContext")
fork_after(): Failed to make GLX context current.
[     0.17 ] error 169 (Unknown) request 155 minor 4 serial 1043 ("GLXBadContext")
main(): Failed to create new session.

Workaround (previous comment) does not work neither :

michal@blackhole ~ $ [xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
compton: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.

[1]+  Aborted                 compton -CG --config ~/.compton.conf

[Brottweiler]

I'm getting this too.

I have compton -b &! in my .xinitrc and that works, but if I kill compton and restart it with compton -b I get

[     0.05 ] error  169 Unknown      request  154 minor    5 serial    849: "GLXBadContext"
fork_after(): Failed to make GLX context current.
[     0.05 ] error  169 Unknown      request  154 minor    4 serial   1005: "GLXBadContext"
main(): Failed to create new session.

If I remove the -b it works, so it's not really a big deal but still a bug.

[discoltk]

Same problem, though while it will start without the -b flag, the performance is severely degraded.

Nvidia 364.19-1 libglvnd 0.1.0.20160411-1

I tried downgrading libglvnd but that caused bigger problems. Was really happy to discover compton and with it tweaked properly its been great. Hope a fix is found soon!

[mxm43]

Confirmed same issue with 0.1beta2, nvidia 364.19 drivers. Gentoo Linux. Awesome WM.

[cars10]

I experience this issue again with the latest update. (also with @garnetius fork) see also https://forum.manjaro.org/t/compton-latest-nvidia-failed-to-get-glx-context/21187

$ compton --version
git-v0.1_beta2-88-ge5074a5-2016-05-04

$ pacman -Q |grep nvidia
lib32-nvidia-340xx-utils 340.101-6
linux410-nvidia-340xx 340.101-7
linux49-nvidia-340xx 340.101-18
mhwd-nvidia 1:375.39-1
mhwd-nvidia-304xx 1:304.134-1
mhwd-nvidia-340xx 340.101-1
nvidia-340xx-utils 340.101-8
opencl-nvidia 1:375.39-1

[hhirsch]

Same Issue

$ compton --version
v0.1_beta2.5

$ pacman -Q |grep nvidia
lib32-nvidia-cg-toolkit 3.1-5
lib32-nvidia-utils 1:396.54-2
linux418-nvidia 1:396.54-1
mhwd-nvidia 1:396.54-1
mhwd-nvidia-304xx 1:304.137-1
mhwd-nvidia-340xx 340.107-1
mhwd-nvidia-390xx 390.77-1
nvidia-cg-toolkit 3.1-4
nvidia-utils 1:396.54-2

I removed all drivers and re-installed with mhwd. Worked great.