Bryce, as far as fixing the applications are concerned, I don't quite follow why applications that used to work need to be fixed because libxcb apparently one way or another changes an API contract that it has no business of changing.
That being said, if somebody claims its the application's fault, I'd really appreciate some information about what I need to fix around somthing that wasn't even apparently broken with Xlib. I can attach 3 backtraces of various ways xvidcap deadlocks with libxcb (variant 3 resulting in a complete X11 lockup, so I need to ssh into the box and kill xvidcap). The only thing I can see is that in one thread I'm trying to do XShmGetImage on a locked X display while in the other thread GTK does its stuff. Have I been doing this completely wrong for years without noticing? And I've just recorded more than an hour of screencasts without a single hang with your non-xcb libraries. This issue keeps me from upgrading to intrepid because first I'll have to find a way of compiling the required X11 libs without xcb. ** Attachment added: "lock1.txt" http://launchpadlibrarian.net/19120781/lock1.txt -- hardy, locking assertion failure, xorg/libsdl https://bugs.launchpad.net/bugs/185311 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
