-
Notifications
You must be signed in to change notification settings - Fork 72
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
Error: write after end #142
Comments
What's your DISPLAY look like? Is it local connection? 'writeAfterEnd' means initial connection was successful but later server unexpectedly closed connection. Might be authentication issue ( afaik this library only supports |
Thanks for getting back to me. What do you mean by display? The environment variable? That's |
Error: write after end |
@jmccandles146 what's your OS? |
centOS-7 |
@jmccandles146 it looks to me that error is completely unrelated to node-x11. genieacs loggers tries to write to a socket after it was closed ( Stream is process stderr - https://github.com/zaidka/genieacs/blob/ec1360217b68e2947c47f8b3a17ea97af7a773f5/lib/logger.js#L38 ) something closes stderr fd |
is it the connection error with MongoDB |
I get the same when I try to get all the properties of a window, like in this smoke test:
|
My bad. The issue was recreating and terminating the x11 server for every command I executed... |
I'm trying to get a list of all open windows. Seems to me like an actual issue with node-x11 and not x11 itself:
This is the stacktrace:
This is the code I'm running:
_NET_CLIENT_LIST_STACKING
and_WIN_CLIENT_LIST
result in the same error. So does leaving out the additional parameters.The text was updated successfully, but these errors were encountered: