Pledging and partying are a lot more important.  You are only young once!

On Tuesday 23 February 2010 07:32:34 pm jboisture wrote:
> Hey,
> 
>     Sorry I haven't had any free time to work on this and it doesn't look
> like I'm going to have any time until spring break.  That's only a week and
> a half away and I should be able to spend a lot of time on this then.  I'm
> not sure if I'll be back in Arlington or not, but I should have plenty of
> time to do my best to fix this by March 15th, when Luke said we needed to
> have something done.  I hope this is acceptable, I just don't have any time
> between school and pledging.
> 
> Jamie
> 
> On Tue, Feb 23, 2010 at 9:05 AM, Michael Babcock <email address hidden> wrote:
> > Simple test case for many xcb-based libX11 bugs:
> >
> > ico -threads 10
> >
> > You will likely get a deadlock, "_XAllocID: Assertion `ret != inval_id'
> > failed." or the error mentioned here.
> >
> > Locally we have problems with any X program that uses multi-threading
> > since the switch to libxcb X11. Sometimes one or two bugs will be fixed
> > but then others will turn up. We have resorted to maintaining our own
> > compile of pre-xcb libX11 in order to make our in-house programs
> > reliable.
> >
> > At this point I think libxcb libX11 is a failed experiment. If the
> > threading bugs haven't been fixed after a couple years now, will they
> > ever be? Should we simply revert to the old libX11? Last time this was
> > suggested the answer was that compiz depended on xcb, but is some
> > desktop eye-candy really more important than real applications working
> > that people use to get real work done?
> >
> > Someone found the root cause of another of these bugs recently, so maybe
> > there is hope:
> > http://lists.freedesktop.org/archives/xcb/2009-October/005102.html
> >
> > --
> > apport-kde assert failure: python: ../../src/xcb_io.c:242:
> > process_responses: Assertion `(((long) (dpy->last_request_read) - (long)
> > (dpy->request)) <= 0)' failed.
> > https://bugs.launchpad.net/bugs/419501
> > You received this bug notification because you are subscribed to GASP
> > Core.
> >
> > Status in GASP Core Code: Confirmed
> > Status in “libxcb” package in Ubuntu: Confirmed
> > Status in “libxcb” source package in Lucid: Confirmed
> >
> > Bug description:
> > Binary package hint: apport
> >
> > Description:    Ubuntu karmic (development branch)
> > Release:        9.10
> >
> > ProblemType: Crash
> > Architecture: amd64
> > AssertionMessage: python: ../../src/xcb_io.c:242: process_responses:
> > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <=
> > 0)' failed.
> > CrashCounter: 1
> > Date: Wed Aug 26 16:14:40 2009
> > DistroRelease: Ubuntu 9.10
> > ExecutablePath: /usr/share/apport/apport-kde
> > InterpreterPath: /usr/bin/python2.6
> > NonfreeKernelModules: nvidia
> > Package: apport-kde 1.8-0ubuntu1
> > PackageArchitecture: all
> > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde
> > ProcEnviron:
> >  PATH=(custom, no user)
> >  LANG=en_US.UTF-8
> >  LANGUAGE=
> >  SHELL=/bin/bash
> > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
> > Signal: 6
> > SourcePackage: apport
> > StacktraceTop:
> >  raise () from /lib/libc.so.6
> >  abort () from /lib/libc.so.6
> >  __assert_fail () from /lib/libc.so.6
> >  ?? () from /usr/lib/libX11.so.6
> >  _XEventsQueued () from /usr/lib/libX11.so.6
> > Title: apport-kde assert failure: python: ../../src/xcb_io.c:242:
> > process_responses: Assertion `(((long) (dpy->last_request_read) - (long)
> > (dpy->request)) <= 0)' failed.
> > Uname: Linux 2.6.31-3-generic x86_64
> > UserGroups:
> 

-- 
Roland Hughes, President
Logikal Solutions
(630)-205-1593  (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.logikalsolutions.com