Description of the issue: About two days ago my key bindings for ctrl+x, ctrl+c, ctrl+v, ctrl+d, ctrl+h and ctrl+f changed and I don’t know why. Looking at the bindings at brave://settings/system/shortcuts they all look correct there, saying that they’re cut, copy, past etc. Everywhere else on my ubuntu machine outside of Brave has those key-bindings working fine. It might be that other keybindings are also changed but I don’t use others very often.
For the record this is what currently happens:
ctrl+x does nothing I can see.
ctrl+c opens brave://downloads/
ctrl+v triggers Search Brave in the search bar
ctrl+d does the same as ctrl+v
ctrl+h adds a bookmark
ctrl+f opens View Source for the webpage I’m on.
This happens every time I’m on a webpage
**Brave Version( check About Brave):** Brave 1.81.131 (Official Build) (64-bit)
Additional Information: Ubuntu 22.04.5 LTS 64-bit OS
That’s certainly strange and sounds to me like it might be an extension of some kind hijacking those commands? It’s at least isolated to something in your browser profile – I don’t see any other recent reports of this behavior and this would be an issue that would be reported pretty readily by anyone seeing it.
Do you have any extensions installed in the browser at this time? If you open a Guest profile (Menu --> More tools --> Guest profile) and then close your original profile window, does the guest profile also have these same shortcut options?
Thank you for the reply. I followed through what you said and yes, the keybindings were still wrong in the guest profile. My extensions haven’t changed recently. I only use my password manager and ublock origin which don’t seem like the sort of things to change key bindings regardless.
Thank you for the information. Really not sure how this could happen unless it was done very deliberately. Did you install Brave initially via terminal (as instructed on brave.com/linux) or through some other method?
I had it installed through Ubuntu Software Center. Since my last post I uninstalled it from there and installed it through terminal as Brave recommends.
It didn’t change anything. Still got the problem. It’s entirely localised to Brave. I’ve tested ctrl+c ctrl+v on pretty much everything I routinely use that has text and Brave is the only thing that has these keybinding problems. Since I just uninstalled Brave I tried it with no extensions installed and yep, the problem’s still there.
Same thing for me on Ubuntu 24.04. Ctrl C, Ctrl T, etc all do random things now like making a bookmark, opening the Leo AI, etc. I have reinstalled brave from the apt repositiory. Might install it from a different source and see if that helps.
Well I’ll be damned. I had more than one keyboard set-up in my Ubuntu settings. I read your posts and deleted all but one. The problems went away. Didn’t even need to restart Brave.
If I may suggest, this still feels like a bug with Brave that needs addressing. Nothing else has this problem and Brave shouldn’t have it either. I should be able to have multiple keyboard layouts without my keybindings going to all hell.
I invite the Brave devs to look into this: I had multiple keyboard layouts enabled in my settings. This is (in Ubuntu) under settings>Keyboard> and under the Input Sources sub-menu I had several keyboard layouts on my list. Once I removed all but one my initial problem was solved.
This definitely feels like a new bug. I’m seeing this on Ubuntu 24.04.3 LTS with Brave 1.81.131. I did not see this behavior with earlier versions of Brave.
I have multiple keyboard input sources defined in Gnome (English Dvorak, English Colemak and English US). In Brave, the keyboard input correctly acts according to which keyboard layout is active in the Linux desktop. However, global Brave browser keyboard shortcuts (ctrl-t, ctrl-w, ctrl-f, etc.) seem to only respond to whichever keyboard layout is the first in the list in the Gnome keyboard settings. This seems like a new Brave browser bug. Brave global keyboard shortcuts should follow whichever keyboard layout is active in Linux.
(Incidentally, this issue does not seem to affect Chrome 139.0.7258.66, which I think uses the same Chromium version.)
Should this topic be in a Solved state since it appears there is an ongoing bug? I just tested this issue again using the latest Brave 1.81.135 (based on Chromium 139.0.7258.127). The issue is reproducible. Google Chrome 139.0.7258.127 does not have this issue.
