Hello, All of your solutions besides downgrading Chromium that I didn't try work for me.
Michel Le Bihan Le samedi 09 janvier 2021 à 17:08 +0200, Faidon Liambotis a écrit : > On Fri, Jan 08, 2021 at 07:30:03PM +0100, Michel Le Bihan wrote: > > After updating libx11-xcb1 chromium and google chrome UI is not > > responding to any input and clicking anywhere on the app window > > causes > > the GNOME app is not responding dialog to appear. The app actually > > is > > not frozen because if you pass a URL with dynamic web content as a > > parameter, it will be constantly updated. I didn't notice any other > > affected app, but I didn't test much. > > I was experiencing the same. Both Chromium (87.0.4280.88-0.4) and > Google > Chrome (87.0.4280.141-1) were entirely unusable for me. > > It turned out that for me, the cause was a disparity between libx11- > xcb1 > and libx11-6 -- the former was at 2:1.7.0-1, while the latter was at > 2:1.6.12-1 (don't ask why...). Any of the following are addressing > the > issue for me: > * Upgrading libx11-xcb1 + libx11-6 to 2:1.7.0-1 (duh) > * Downgrading libx11-xcb1 (+ libx11-6) to 2:1.6.12-1 > * Reverting to an older version of Chromium (83.0.4103.116) > * Google Chrome Beta (88.0.4324.79-1) > > Before I realized that the issue was a version disparity, I bisected > libx11, and found that commit dbb55e1 ("Fix poll_for_response race > condition") to be the "bad" commit. Reverting that commit on top of > 1.7.0-1, made the issue disappear as well. > > At minimum, it looks like libx11-xcb1 and libx11-6 need to be at the > same version, so perhaps libx11-xcb1 should have a versioned depends > on > libx11-6 (= ${binary:Version}). On that note, libx11-xcb1 doesn't > seem > to even Depend on libc6, with libX11-xcb.so.1 being statically > linked; > perhaps that's an issue of its own? > > #979443 may or may not be a related bug here. > > Faidon