Keyboard misbehaviour with Firefox / Javascript after upgrade to 16.04
After upgrading to 16.04, when I type into a javascript text field like this search field, every keystroke erases the one before it. I've also noticed subtly different behaviour in the location bar; matching URLs are no longer pre-selected until I cursor down.
I have removed my entire ~/.mozilla directory, purged firefox* (and manually deleted all the hanging firefox files in /etc and /usr/lib).
Even after what should be a completely fresh install of Firefox 49.0 (and a short try with an early v48 build), the problem persists. The only way I can make the behaviour stop is to disable javascript in about:config.
Possibly related: when I attempted to post this question with Firefox, the post hung, and I got an error from StackExchange about an unusually high number of requests.
Anyone else seeing anything similar? What else can I try?
UPDATE:
It's more than just Firefox. All gecko-based applications seem to be misinterpreting keyboard input, as was Eclipse. I suspect keystrokes were going to the wrong windows, somehow.
16.04 firefox
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
add a comment |
After upgrading to 16.04, when I type into a javascript text field like this search field, every keystroke erases the one before it. I've also noticed subtly different behaviour in the location bar; matching URLs are no longer pre-selected until I cursor down.
I have removed my entire ~/.mozilla directory, purged firefox* (and manually deleted all the hanging firefox files in /etc and /usr/lib).
Even after what should be a completely fresh install of Firefox 49.0 (and a short try with an early v48 build), the problem persists. The only way I can make the behaviour stop is to disable javascript in about:config.
Possibly related: when I attempted to post this question with Firefox, the post hung, and I got an error from StackExchange about an unusually high number of requests.
Anyone else seeing anything similar? What else can I try?
UPDATE:
It's more than just Firefox. All gecko-based applications seem to be misinterpreting keyboard input, as was Eclipse. I suspect keystrokes were going to the wrong windows, somehow.
16.04 firefox
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
add a comment |
After upgrading to 16.04, when I type into a javascript text field like this search field, every keystroke erases the one before it. I've also noticed subtly different behaviour in the location bar; matching URLs are no longer pre-selected until I cursor down.
I have removed my entire ~/.mozilla directory, purged firefox* (and manually deleted all the hanging firefox files in /etc and /usr/lib).
Even after what should be a completely fresh install of Firefox 49.0 (and a short try with an early v48 build), the problem persists. The only way I can make the behaviour stop is to disable javascript in about:config.
Possibly related: when I attempted to post this question with Firefox, the post hung, and I got an error from StackExchange about an unusually high number of requests.
Anyone else seeing anything similar? What else can I try?
UPDATE:
It's more than just Firefox. All gecko-based applications seem to be misinterpreting keyboard input, as was Eclipse. I suspect keystrokes were going to the wrong windows, somehow.
16.04 firefox
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
After upgrading to 16.04, when I type into a javascript text field like this search field, every keystroke erases the one before it. I've also noticed subtly different behaviour in the location bar; matching URLs are no longer pre-selected until I cursor down.
I have removed my entire ~/.mozilla directory, purged firefox* (and manually deleted all the hanging firefox files in /etc and /usr/lib).
Even after what should be a completely fresh install of Firefox 49.0 (and a short try with an early v48 build), the problem persists. The only way I can make the behaviour stop is to disable javascript in about:config.
Possibly related: when I attempted to post this question with Firefox, the post hung, and I got an error from StackExchange about an unusually high number of requests.
Anyone else seeing anything similar? What else can I try?
UPDATE:
It's more than just Firefox. All gecko-based applications seem to be misinterpreting keyboard input, as was Eclipse. I suspect keystrokes were going to the wrong windows, somehow.
16.04 firefox
16.04 firefox
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
edited Oct 21 '16 at 17:44
DS Justice
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
asked Oct 12 '16 at 20:03
DS JusticeDS Justice
349214
349214
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
Alt-Gr key not working properly on Firefox
The solution is, to activate the checkbox Prevent accessibility services from accessing your browser in Firefox settings under Privacy & Security -> Permissions
answered Dec 17 '17 at 15:12
KareKare
112
Can't accept (no way to test) but it's always good to have other options to test for next time. Thanks!
– DS Justice
Dec 18 '17 at 17:24
add a comment |
A better workaround is to disable IBus, as described at the bottom of this thread https://bugs.launchpad.net/unity/+bug/1484157
As said on the ubuntu-fr forum, you could avoid the bug by going in
system option ▸ languages ▸ Input keyboard system and selecting an
option other than IBus.
(https://forum.ubuntu-fr.org/viewtopic.php?id=2020851)
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
Can't test it until next time it happens, but your answer seems plausible. Have an upvote.
– DS Justice
Feb 23 at 21:51
add a comment |
Well, after a week of fiddling, I gave up and deleted ~/.config. That fixed my specific problem, but it sure would've been nice to actually solve the problem. Marking solved, but if you figure it out, please post a new answer.
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
add a comment |
I had the same issue and deleting ~/.config/dconf solved it.
answered Jun 2 '18 at 21:55
GuestGuest
1
This is really poor answer. You need to provide good answer with more information.
– Eranda Peiris
Jun 3 '18 at 2:04
I disagree. It would benefit from more info, but even without, it is potentially useful to others to know that it may not be necessary to delete all of .config/
– DS Justice
Jun 3 '18 at 18:46
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f836228%2fkeyboard-misbehaviour-with-firefox-javascript-after-upgrade-to-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Alt-Gr key not working properly on Firefox
The solution is, to activate the checkbox Prevent accessibility services from accessing your browser in Firefox settings under Privacy & Security -> Permissions
answered Dec 17 '17 at 15:12
KareKare
112
Can't accept (no way to test) but it's always good to have other options to test for next time. Thanks!
– DS Justice
Dec 18 '17 at 17:24
add a comment |
Alt-Gr key not working properly on Firefox
The solution is, to activate the checkbox Prevent accessibility services from accessing your browser in Firefox settings under Privacy & Security -> Permissions
answered Dec 17 '17 at 15:12
KareKare
112
Can't accept (no way to test) but it's always good to have other options to test for next time. Thanks!
– DS Justice
Dec 18 '17 at 17:24
add a comment |
Alt-Gr key not working properly on Firefox
The solution is, to activate the checkbox Prevent accessibility services from accessing your browser in Firefox settings under Privacy & Security -> Permissions
answered Dec 17 '17 at 15:12
KareKare
112
Alt-Gr key not working properly on Firefox
The solution is, to activate the checkbox Prevent accessibility services from accessing your browser in Firefox settings under Privacy & Security -> Permissions
answered Dec 17 '17 at 15:12
KareKare
112
answered Dec 17 '17 at 15:12
KareKare
112
answered Dec 17 '17 at 15:12
KareKare
112
answered Dec 17 '17 at 15:12
KareKare
112
112
Can't accept (no way to test) but it's always good to have other options to test for next time. Thanks!
– DS Justice
Dec 18 '17 at 17:24
add a comment |
Can't accept (no way to test) but it's always good to have other options to test for next time. Thanks!
– DS Justice
Dec 18 '17 at 17:24
Can't accept (no way to test) but it's always good to have other options to test for next time. Thanks!
– DS Justice
Dec 18 '17 at 17:24
Can't accept (no way to test) but it's always good to have other options to test for next time. Thanks!
– DS Justice
Dec 18 '17 at 17:24
add a comment |
A better workaround is to disable IBus, as described at the bottom of this thread https://bugs.launchpad.net/unity/+bug/1484157
As said on the ubuntu-fr forum, you could avoid the bug by going in
system option ▸ languages ▸ Input keyboard system and selecting an
option other than IBus.
(https://forum.ubuntu-fr.org/viewtopic.php?id=2020851)
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
Can't test it until next time it happens, but your answer seems plausible. Have an upvote.
– DS Justice
Feb 23 at 21:51
add a comment |
A better workaround is to disable IBus, as described at the bottom of this thread https://bugs.launchpad.net/unity/+bug/1484157
As said on the ubuntu-fr forum, you could avoid the bug by going in
system option ▸ languages ▸ Input keyboard system and selecting an
option other than IBus.
(https://forum.ubuntu-fr.org/viewtopic.php?id=2020851)
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
Can't test it until next time it happens, but your answer seems plausible. Have an upvote.
– DS Justice
Feb 23 at 21:51
add a comment |
A better workaround is to disable IBus, as described at the bottom of this thread https://bugs.launchpad.net/unity/+bug/1484157
As said on the ubuntu-fr forum, you could avoid the bug by going in
system option ▸ languages ▸ Input keyboard system and selecting an
option other than IBus.
(https://forum.ubuntu-fr.org/viewtopic.php?id=2020851)
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
A better workaround is to disable IBus, as described at the bottom of this thread https://bugs.launchpad.net/unity/+bug/1484157
As said on the ubuntu-fr forum, you could avoid the bug by going in
system option ▸ languages ▸ Input keyboard system and selecting an
option other than IBus.
(https://forum.ubuntu-fr.org/viewtopic.php?id=2020851)
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
answered Feb 23 at 19:33
Andrzej SzombierskiAndrzej Szombierski
111
111
Can't test it until next time it happens, but your answer seems plausible. Have an upvote.
– DS Justice
Feb 23 at 21:51
add a comment |
Can't test it until next time it happens, but your answer seems plausible. Have an upvote.
– DS Justice
Feb 23 at 21:51
Can't test it until next time it happens, but your answer seems plausible. Have an upvote.
– DS Justice
Feb 23 at 21:51
Can't test it until next time it happens, but your answer seems plausible. Have an upvote.
– DS Justice
Feb 23 at 21:51
add a comment |
Well, after a week of fiddling, I gave up and deleted ~/.config. That fixed my specific problem, but it sure would've been nice to actually solve the problem. Marking solved, but if you figure it out, please post a new answer.
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
add a comment |
Well, after a week of fiddling, I gave up and deleted ~/.config. That fixed my specific problem, but it sure would've been nice to actually solve the problem. Marking solved, but if you figure it out, please post a new answer.
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
add a comment |
Well, after a week of fiddling, I gave up and deleted ~/.config. That fixed my specific problem, but it sure would've been nice to actually solve the problem. Marking solved, but if you figure it out, please post a new answer.
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
Well, after a week of fiddling, I gave up and deleted ~/.config. That fixed my specific problem, but it sure would've been nice to actually solve the problem. Marking solved, but if you figure it out, please post a new answer.
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
answered Oct 21 '16 at 17:43
DS JusticeDS Justice
349214
349214
add a comment |
add a comment |
I had the same issue and deleting ~/.config/dconf solved it.
answered Jun 2 '18 at 21:55
GuestGuest
1
This is really poor answer. You need to provide good answer with more information.
– Eranda Peiris
Jun 3 '18 at 2:04
I disagree. It would benefit from more info, but even without, it is potentially useful to others to know that it may not be necessary to delete all of .config/
– DS Justice
Jun 3 '18 at 18:46
add a comment |
I had the same issue and deleting ~/.config/dconf solved it.
answered Jun 2 '18 at 21:55
GuestGuest
1
This is really poor answer. You need to provide good answer with more information.
– Eranda Peiris
Jun 3 '18 at 2:04
I disagree. It would benefit from more info, but even without, it is potentially useful to others to know that it may not be necessary to delete all of .config/
– DS Justice
Jun 3 '18 at 18:46
add a comment |
I had the same issue and deleting ~/.config/dconf solved it.
answered Jun 2 '18 at 21:55
GuestGuest
1
I had the same issue and deleting ~/.config/dconf solved it.
answered Jun 2 '18 at 21:55
GuestGuest
1
answered Jun 2 '18 at 21:55
GuestGuest
1
answered Jun 2 '18 at 21:55
GuestGuest
1
answered Jun 2 '18 at 21:55
GuestGuest
1
1
This is really poor answer. You need to provide good answer with more information.
– Eranda Peiris
Jun 3 '18 at 2:04
I disagree. It would benefit from more info, but even without, it is potentially useful to others to know that it may not be necessary to delete all of .config/
– DS Justice
Jun 3 '18 at 18:46
add a comment |
This is really poor answer. You need to provide good answer with more information.
– Eranda Peiris
Jun 3 '18 at 2:04
I disagree. It would benefit from more info, but even without, it is potentially useful to others to know that it may not be necessary to delete all of .config/
– DS Justice
Jun 3 '18 at 18:46
This is really poor answer. You need to provide good answer with more information.
– Eranda Peiris
Jun 3 '18 at 2:04
This is really poor answer. You need to provide good answer with more information.
– Eranda Peiris
Jun 3 '18 at 2:04
I disagree. It would benefit from more info, but even without, it is potentially useful to others to know that it may not be necessary to delete all of .config/
– DS Justice
Jun 3 '18 at 18:46
I disagree. It would benefit from more info, but even without, it is potentially useful to others to know that it may not be necessary to delete all of .config/
– DS Justice
Jun 3 '18 at 18:46
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f836228%2fkeyboard-misbehaviour-with-firefox-javascript-after-upgrade-to-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
