{"action":"created","issue":{"url":"https://api.github.com/repos/adobe/brackets/issues/10598","labels_url":"https://api.github.com/repos/adobe/brackets/issues/10598/labels{/name}","comments_url":"https://api.github.com/repos/adobe/brackets/issues/10598/comments","events_url":"https://api.github.com/repos/adobe/brackets/issues/10598/events","html_url":"https://github.com/adobe/brackets/issues/10598","id":57707682,"number":10598,"title":"Keyboard not responding in 1.2","user":{"login":"Romane-T","id":8910312,"avatar_url":"https://avatars.githubusercontent.com/u/8910312?v=3","gravatar_id":"","url":"https://api.github.com/users/Romane-T","html_url":"https://github.com/Romane-T","followers_url":"https://api.github.com/users/Romane-T/followers","following_url":"https://api.github.com/users/Romane-T/following{/other_user}","gists_url":"https://api.github.com/users/Romane-T/gists{/gist_id}","starred_url":"https://api.github.com/users/Romane-T/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Romane-T/subscriptions","organizations_url":"https://api.github.com/users/Romane-T/orgs","repos_url":"https://api.github.com/users/Romane-T/repos","events_url":"https://api.github.com/users/Romane-T/events{/privacy}","received_events_url":"https://api.github.com/users/Romane-T/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-02-14T21:45:13Z","updated_at":"2015-02-21T12:42:49Z","closed_at":null,"body":"Good morning\r\nMachines involved:\r\nSamsung N120 on Debian Jessie with lxqt version 0.9.0-1, dual core, 32 bit, 1Gb of memory, about 5 or so years old\r\nMedionPC Akoya quad core running Jessie with KDE full, 64 bit, 4Gb of memory about 3 or 4 years old\r\nNot using live development.\r\nThe 32 bit version of Brackets is that at https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.32-bit.deb - see thread https://github.com/adobe/brackets/issues/10255 Debian - libgcrypt version breaks Brackets.\r\nThe 64 bit version is that in the same thread above - unknown by self if the same build as the 1.2 with requests for testing by @Sarath in the development channel, as no deb there and no idea how to build from source - have looked, head still spinning a little :)\r\n32 bit version - zero keyboard response. Mouse appears to have full functionality. Fresh boot. Tested with extensions enabled and with extensions disabled, multiple opens and closes. No change on any opening of package. Also tried taking focus from window and giving it back (se 64 bit below) and no change. Do not have another 32 bit machine on which to test to see if hardware or software.\r\n64 bit version has a similar problem, except is only very intermittant, and have not yet tried disabling extensions. Will add more to this when once done this part of testing - as occurs only over time, that may take a day or so. Issue seems to appear when there is a gap in usage of more than a couple of minutes (e.g. when I go for a meal, or answer nature). Keyboard has zero response, mouse appears to retain full functionality. After trying a few different things, found that by taking the focus away from the window and giving it back again (e.g. minimise/maximise, or open another application over the top then close it straight away) seems to resolve the issue in most occurances first time, but sometimes is stubborn and may need two or three unfocus/refocus attempts. Closing and restarting Brackets is not always a reliable fix in my experience to date.\r\nAs I do a lot of copy/paste, tested by clearing all the entries stored (cacherd?) from previous copy/paste actions, makes no difference to result.\r\nEdit: note that cannot assure reproducable on the 64 bit, as sometimes after a break from the keyboard, it still functions.\r\nWith greetings\r\nRomane\r\n\r\nLater edit: Working with extensions disable. After posting the above edit about two or three minutes ago, on return to Brackets keyboard frozen. Placing the browser window back over the top of Brackets did not fix, but minimise/maximise Brackets did again allow keyboard input into Brackets."},"comment":{"url":"https://api.github.com/repos/adobe/brackets/issues/comments/75370059","html_url":"https://github.com/adobe/brackets/issues/10598#issuecomment-75370059","issue_url":"https://api.github.com/repos/adobe/brackets/issues/10598","id":75370059,"user":{"login":"Romane-T","id":8910312,"avatar_url":"https://avatars.githubusercontent.com/u/8910312?v=3","gravatar_id":"","url":"https://api.github.com/users/Romane-T","html_url":"https://github.com/Romane-T","followers_url":"https://api.github.com/users/Romane-T/followers","following_url":"https://api.github.com/users/Romane-T/following{/other_user}","gists_url":"https://api.github.com/users/Romane-T/gists{/gist_id}","starred_url":"https://api.github.com/users/Romane-T/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Romane-T/subscriptions","organizations_url":"https://api.github.com/users/Romane-T/orgs","repos_url":"https://api.github.com/users/Romane-T/repos","events_url":"https://api.github.com/users/Romane-T/events{/privacy}","received_events_url":"https://api.github.com/users/Romane-T/received_events","type":"User","site_admin":false},"created_at":"2015-02-21T12:42:49Z","updated_at":"2015-02-21T12:42:49Z","body":"Good morning\n\nOn 19/02/15 13:41, Peter Flynn wrote:\n>\n> Thanks @Romane-T <https://github.com/Romane-T> -- I am curious to hear \n> if that 1.1 .deb has the same problem for you. For context, part of \n> why this matters is that the \"linux-cef-2171\" native shell has major \n> changes to the UI engine (Chromium) that could easily cause new bugs, \n> so it's useful to compare. We respond to hundreds of bug reports every \n> month, so I sometimes write quick replies and don't always provide as \n> much detail as I could :-)\n>\n> Even if you're only seeing the problem in the \"linux-cef-2171\" build, \n> I'd still be curious to hear info regarding my second paragraph above \n> -- more details on the symptoms may help get to the bottom of what's \n> going on.\n>\n> Thanks for helping us test out the bleeding edge builds!\n>\n> —\n> Reply to this email directly or view it on GitHub \n> <https://github.com/adobe/brackets/issues/10598#issuecomment-74994686>.\n>\nYou are very gracious, Peter.\n\nJust a quick note to affirm that 1.1 ( build 1.1.0-15558 (release \nea908cae5) build timestamp: Wed Dec 17 2014 13:00:52 GMT-0800) has run \nwithout error or fault since install two days ago.\n\nI will deal with your questions 1 by 1.\n\nThe 1.2 build am using is 1.2.0-15668 (master 027de3046) build \ntimestamp: Tue Feb 10 2015 0907:43 GMT-0800\n\nChromium is not installed on my machine. Whether that may or may not \naffect results I do not know.\n\nPeter: At times when the keyboard is not responding, does the editor \narea still look like it has keyboard focus? I.e. is there a blinking cursor?\nRomane: Yes. And am able to move blinking cursor to other places in the \ndocument with the mouse.\n\nPeter: If you drag a text selection using the mouse, is it colored blue \n(focused) or gray (unfocused)?\nRomane: It is coloured as normal, blue (focussed).\n\nPeter: If you use the mouse to invoke a feature where focus would move \nelsewhere -- e.g. /Find > Find/ or /File > Open/ in the menu -- does \ntyping work there?\nRomane: This was one had not thought of thus not tested. Reinstalled 1.2 \nto test.\nOn keyboard becoming non-functional (in case the information is useful, \nhad been away from the computer for 30 minutes - screen saver running \nwhen reached chair, screen power saving kicked in as I sat down), tested \nfor 'File->Save as' - able to type into save dialogue box fine, but \nwithout thinking used the mouse to OK, rather than tabbing to the OK. \nAfter this operation, keyboard was still non-functional. Tested for \n'Find->Find in files', and able to type into find box OK. 'Enter' was \nrecognised and the search was carried out successfully. On completion of \noperation, keyboard was functional, but as it accepted the 'Enter'  for \nthe find operation believe that the keyboard was functional again at \nthat point.\n\nWill continue running with 1.2 for the nonce to test this over a period \nof time, will report results in a week unless am advised otherwise, as \nthat will/might show any consistencies/inconsistencies.\n\nWith greetings\n\nRomane\n"}}