Date: Wed, 25 Jan 2012 20:04:33 -0600 From: "Conrad J. Sabatier" <conrads@cox.net> To: Sebastian Chmielewski <chmiels@o2.pl> Cc: kwm@freebsd.org, x11@freebsd.org Subject: Re: libxcb 1.8 Message-ID: <20120125200433.52d26eba@cox.net> In-Reply-To: <CAHrc_evG7MAfaqk9-fXaHeagJ6tk0nkjaxqMFtpEW1byFmxo2g@mail.gmail.com> References: <20120125205727.GP2726@deviant.kiev.zoral.com.ua> <CAHrc_evG7MAfaqk9-fXaHeagJ6tk0nkjaxqMFtpEW1byFmxo2g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Jan 2012 22:17:30 +0100 Sebastian Chmielewski <chmiels@o2.pl> wrote: > 2012/1/25 Kostik Belousov <kostikbel@gmail.com> > > > This is a note that updating libxcb from xorg-dev to 1.8 killed my > > client-side X. Every client using libxcb hangs on start, eating > > 100% CPU in the poll(2) loop. Downgrading to 1.7 fixed the issue. > > > > Not much useful, but I hope to get less mail after the notice. > > > > I have the same issue. Rebuilding libxcb, xcb-util didn't help. I experienced the same roughly a week ago, and reported it on the xorg mailing list (xorg@lists.x.org). Reverting to 1.7 was absolutely necessary. I considered for a while upgrading every port that depended on libxcb, but according to pkg_info, that came out to be roughly 750+ packages(!). No thank you. :-) -- Conrad J. Sabatier conrads@cox.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120125200433.52d26eba>