wew makes Emacs think that X closed the connection about opt HOT 4 CLOSED

I have also a problem and it can be related with yours. I use the application upplay (http://www.lesbonscomptes.com/upplay/) which is an upnp control point to listen to my music. When wew is started I can start the application. When wew -a is running I can't start it. I get the following error:

X Error: BadAccess (attempt to access private resource denied) 10
  Major opcode: 2 (X_ChangeWindowAttributes)
  Resource id:  0x100000a

This application depends on qtwebkit. If I stop wew -a I can start the application without a problem. kdenlive is another application which uses qtwebkit. It has the same problem. With vlc I also get the error when wew -a is running. The difference is that the error is displayed but the applications starts.

Probably it has nothing to do with bspwm. On my system I have no problem with emacs.

from opt.

This is a "known" problem with wew in fact. I also encountered a few applications that couldn't start when wew -a is running. It has to do with the event mask used, and how wew catch events. I still don't fully understand what wew is doing wrong though, but it forbid clients to change their attributes by themselves. If anyone as an idea, that'd be nice

from opt.

Issue should be fixed as of latest commit (c835abc). I finally figured what was going on! (read commit log for more details)

from opt.

Great, thank you very much! One application I'm using couldn't start and with your fix there is no problem anymore.

from opt.