Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

picom fails to reinitialize itself on config update on xfce #392

Closed
absolutelynothelix opened this issue May 2, 2020 · 7 comments
Closed

Comments

@absolutelynothelix
Copy link
Collaborator

absolutelynothelix commented May 2, 2020

a while ago i noticed that picom throws this error when exits:

X Error of failed request:  GLXBadPixmap
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  23 (X_GLXDestroyPixmap)
  Serial number of failed request:  672
  Current serial number in output stream:  841

initially this seemed harmless, but today i discovered that looks like picom can't reinitialize itself on configuration file update, it just throws this error and won't restart.

this happens only with glx backend (both old and new), and looks like it's somehow related to xfce, since it works on bspwm just fine.

basically reproducible with:

picom --config /dev/null --backend glx
picom --experimental-backends --config /dev/null --backend glx

then hit ctrl-c.

vanilla picom built from latest commit.

@yshui
Copy link
Owner

yshui commented May 2, 2020

Can't seems to reproduce the problem here.

@absolutelynothelix
Copy link
Collaborator Author

@yshui, maybe you need some additional info? idk what else i can do to point to some particular cause.

@yshui
Copy link
Owner

yshui commented May 2, 2020

Is your build a debug build?

@absolutelynothelix
Copy link
Collaborator Author

nah, it's release build. but on debug build there is no additional info, the same message is printed.

@yshui
Copy link
Owner

yshui commented May 2, 2020

Weird. Maybe some pixmaps were not freed during shutdown

@absolutelynothelix
Copy link
Collaborator Author

hmu if you have an idea of fix that i can try :)

@absolutelynothelix
Copy link
Collaborator Author

related, i guess: #984

the error is still here, though now it has different style, but picom doesn't fail to reinitialize itself on configuration file change anymore so i'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants