Carlo Wood wrote:
Any progress yet? Things I can test?

Nope, sorry. I probably won't have much to report for a while; day job interferes.

I noticed that you are using threads in synergys.
The assertion that we run into can be caused if
multiple threads do calls to GUI calls (X, Xt).

All such calls must be done from one thread.
Are you doing X calls from more than one thread?

I'm not entirely sure. If you look at the history of the package, the most recent upload was done to fix a problem in synergyc that was somewhat related, in that xcb seemed to trigger it.

The problem there was that we were noticing events from watching the X socket. The problem is that X events could sneak through due to a race condition, and the client would appear to hang.

For that problem, the client didn't do anything thread-unsafe with X calls, but it did detect events and handle them in separate threads. I suspect something similar may be happening in the server, but have no idea if that's causing this or some other problem.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to