Chromium stops accepting keyboard input after externally triggered open
Reported by
tinlo...@gmail.com,
Mar 5 2016
|
|||||
Issue descriptionChrome Version (from the about:version page): 48.0.2564.116 (Developer Build) (64-bit) Is this the most recent version: Yes, installed from portage OS + version: Gentoo Linux (no version here, sorry) CPU architecture (32-bit / 64-bit): AMD64 Window manager: awesome WM 3.5.8 URLs (if relevant): Behavior in Linux Firefox: Works Behavior in Windows Chrome (if you have access to it): Probably not relevant? What steps will reproduce the problem? 1. Open chromium 2. Open a site/tab in chromium via an external command (i.e. 'xdg-open http://google.com' on the command line) What is the expected result? Another tab opens and everything works. What happens instead? Another tab opens, but chromium completely ignores all keyboard input. No luck in the address bar, in form fields on any site, nothing. Even my window manager's 'close window' shortcut is ignored while chromium has the focus. Mouse input works without any problem. I'm not sure if that helps, but I'm experiencing the same issue with github's Atom editor, which is based on an encapsulated chromium (see github's "Electron"). If I open a new file inside an existing Atom window by issuing "atom /some/file", all keyboard input is ignored inside atom. So I think the flaw must be in a component that is common to atom and the "full browser".
,
Mar 7 2016
Hi, yes, I'm able to reproduce this even when starting with "--user-data-dir=~/tmp" (~/tmp does not contain a chromium profile, no extensions, ...) Since Gentoo's portage only offers 48.*, I'll have to get the latest 50.* build from somewhere else. I'll report back. Please let me know if there are any debug logs or similar that could help.
,
Mar 7 2016
brajkumar@ - In the video you attached, your xdg-open opens a new chromium *window*, not a new tab. I'm not sure why it does that (strange defaults on Ubuntu?), but I'm only experiencing the problem when opening a new tab inside an existing window via an external command.
,
Mar 9 2016
Thank you for providing more feedback. Assigning to requester "brajkumar@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 29 2016
Requesting an attempt from Bibin.
,
May 2 2016
Still am not able to reproduce the issue on Ubuntu 14.04 using chrome latest stable M50-50.0.2661.94. Observed the keyboard input is working fine as expected while opening the chrome tab via external command. tinloaf2@ - It's because that I have not launched the chrome prior to it. But as you said it open's as a new tab and not in a new chrome window. Are you still facing this issue on latest stable? Could you please recheck this issue on your latest stable M50 and kindly update this bug. If issue still persists it might be Gentoo OS specific issue. Thanks!
,
Jun 8 2016
tinloaf2@: Please update the thread if you still see this on the latest chrome stable.
,
Jul 14 2016
Due to lack of user response closing this issue, Please raise a new issue if you come across the similar one on latest chrome version. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by brajkumar@chromium.org
, Mar 7 2016Components: IO>Keyboard
Labels: Needs-Feedback
1.3 MB
1.3 MB Download