@simon Okay, one reason is: that extension is not enabled in the Debian build. And it seems the chrome.runtime API is made available if any extension allows the current page to communicate. Just no idea yet, why the new tab page can do that sometimes.