Jeff Licquia wrote:
Marc Oscar Singer wrote:
Jeff Licquia wrote:
Looks similar to me; I think I'll end up merging them.
As you wish. The assert makes it very debug-able. IMHO, this looks
like memory corruption. I haven't
run with MALLOC_CHECK_ (IIRC) just to see if the libc can tell us
something about memory.
It could be, but my working theory right now is that synergy is not
conforming to the X11 spec; it's assuming something that used to be
true, but strictly speaking couldn't be assumed. Moving from the old
X11 libs to the new XCB-based ones changed things, I think.
We had a similar problem with the client that should now be fixed.
Do you have any etch boxes you could test for this with? It may be
too much to ask, I know, to run etch for a few days. :-)
what test do you want run?
Using Gnome. Nothing non-standard ITO my Debian install. The other
computer is
a Mac.
OK, thanks.
--
Marc Singer
Bureau of Gizmology
[EMAIL PROTECTED]
t. 206.832.3712
800.682.0581
f. 206.381.0899
Synapse Product Development, LLC.
1511 6th Avenue, 4th floor
Seattle, WA 98101
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
