On Tue, Jan 27, 2009 at 09:46:22PM +0200, Eddy Petrișor <eddy.petri...@gmail.com> was heard to say: > 2009/1/27 Daniel Burrows <dburr...@debian.org>: > > This is for everyone who can reproduce the bug. > > > > Could you build a libcwidget3 with the attached patch and see what's > > produced in /tmp/cwidget.input.log when you reproduce the bug? If I > > start aptitude, run dpkg once, and exit, I get this: > > > > Starting input thread > > Creating new input thread > > Input thread created > > Stopping input thread > > Destroying existing input thread > > Input thread destroyed > > Starting input thread > > Creating new input thread > > Input thread created > > Stopping input thread > > Destroying existing input thread > > Input thread destroyed > > > Starting input thread > Creating new input thread > Input thread created > Stopping input thread > Destroying existing input thread > Input thread destroyed > Starting input thread > Creating new input thread > Input thread created
Thanks. That's more interesting than I expected! I was assuming that the input thread wasn't restarting properly, but it looks like it is. So why aren't we responding to events after that? We're responding to some of them, or the display wouldn't redraw properly; only keyboard events are being dropped. I'll send you another patch with some ad-hoc logging in a bit. Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
