This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Keyboard shortcuts stop working when using multiple keyboard layouts on Ubuntu

  • 2 antwoorde
  • 3 hierdie probleem
  • 11 views
  • Laaste antwoord deur milton.becker

more options

By shortcuts I mean ctrl+t, ctrl+w, even ctrl+c and ctrl+v. They all stop working when I set more than one keyboard layout on Ubuntu (for instance "USA Alternative Intl" and USA). I'm running Firefox 14.0.1 and Ubuntu 10.04 64-bit.

By shortcuts I mean ctrl+t, ctrl+w, even ctrl+c and ctrl+v. They all stop working when I set more than one keyboard layout on Ubuntu (for instance "USA Alternative Intl" and USA). I'm running Firefox 14.0.1 and Ubuntu 10.04 64-bit.

Gewysig op deur milton.becker

All Replies (2)

more options

The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information. Note: This will cause you to lose any Extensions, Open websites, and some Preferences.

To Reset Firefox do the following:

  1. Go to Firefox > Help > Troubleshooting Information.
  2. Click the "Reset Firefox" button.
  3. Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
  4. Firefox will open with all factory defaults applied.


Further information can be found in the Refresh Firefox - reset add-ons and settings article.

Did this fix your problems? Please report back to us!

more options

Nope, that did not fix it, Vlad. I've also tried Firefox 15 beta and the problem happens there too. Any other ideas? Where should I report a bug about this? Thank you.