Bug#494368: synergy: Synergy quits with assertion failure.
Marc Oscar Singer wrote: Jeff Licquia wrote: 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? Just try to duplicate the crash you're seeing when running synergys under etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494368: synergy: Synergy quits with assertion failure.
Marc Singer wrote: Started synergys with the following command line: synergys -f -d INFO After running for a couple of days, it reported an assertion failure on the console. synergys: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int)((xcb_req) - (dpy-request)) = 0)' failed. This *could* be the same as the core dumping crashes, but there is no way to tell from the output. Looks similar to me; I think I'll end up merging them. What desktop setup do you have? Anything unusual (compiz, weird GNOME/KDE setup, etc.)? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494368: synergy: Synergy quits with assertion failure.
Jeff Licquia wrote: Marc Singer wrote: Started synergys with the following command line: synergys -f -d INFO After running for a couple of days, it reported an assertion failure on the console. synergys: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int)((xcb_req) - (dpy-request)) = 0)' failed. This *could* be the same as the core dumping crashes, but there is no way to tell from the output. 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. What desktop setup do you have? Anything unusual (compiz, weird GNOME/KDE setup, etc.)? Using Gnome. Nothing non-standard ITO my Debian install. The other computer is a Mac. -- 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]
Bug#494368: synergy: Synergy quits with assertion failure.
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. :-) Using Gnome. Nothing non-standard ITO my Debian install. The other computer is a Mac. OK, thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494368: synergy: Synergy quits with assertion failure.
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]
Bug#494368: synergy: Synergy quits with assertion failure.
Package: synergy Version: 1.3.1-4 Severity: important Started synergys with the following command line: synergys -f -d INFO After running for a couple of days, it reported an assertion failure on the console. synergys: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int)((xcb_req) - (dpy-request)) = 0)' failed. This *could* be the same as the core dumping crashes, but there is no way to tell from the output. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages synergy depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.3.1-2 GCC support library ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libsm62:1.0.3-2 X11 Session Management library ii libstdc++64.3.1-2The GNU Standard C++ Library v3 ii libx11-6 2:1.1.4-2 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension synergy recommends no packages. synergy suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
