13e8088d62
We have many places where we are sending an XCB request and expect an answer where the protocol guarantees that no error can occur and we are sure to get an answer. However, for example if the X11 server crashes, these places can still fail. This commit tries to handle failures at all these places. I went through the code and tried to add missing error checking (well, NULL-pointer-checking) to all affected places. In most cases these errors are just silently ignored. The exception is in screen querying during startup. If, for example, querying RandR info fails, we will fall back to Xinerama or zaphod mode. This is serious enough that it warrants a warning. In most cases, we should exit shortly afterwards anyway, because, as explained above, these requests should only fail when our connection to the X11 server breaks. References: https://github.com/awesomeWM/awesome/issues/1205#issuecomment-265869874 Signed-off-by: Uli Schlachter <psychon@znc.in> |
||
|---|---|---|
| .. | ||
| button.c | ||
| button.h | ||
| client.c | ||
| client.h | ||
| drawable.c | ||
| drawable.h | ||
| drawin.c | ||
| drawin.h | ||
| key.c | ||
| key.h | ||
| screen.c | ||
| screen.h | ||
| tag.c | ||
| tag.h | ||
| window.c | ||
| window.h | ||