Now, the problem is fixed for me. I think, the problem was in version mismatch of chromium-browser and chromium-browser-inpector. Probably, their dependencies should be changed to allow only [more] strict equivalence. Currently it's possible to have a very outdated inspector with a fresh browser.
-- Dmitry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org