When the layout order [en, ru] and current layout = ru, then Ctrl-C, Ctrl-V and other shortcuts are working fine.
However, When the layout order is reverse [ru, en] and current layout = ru, then Ctrl-C, Ctrl-V and other shortcuts are not working. I have to switch current layout = en to make it work.
It was rather annoying actually. For instance, when in clipboard there is some secret and you chat with someone. Then you want to copy-paste something to the correspondent. You press Ctrl-C somewhere (but it didn't work). Then in the chat program you press Ctrl-Ins (which is working) and immediately press enter. Just to see that you've sent something wrong...
These days I use [en, ru] layout order which doesn't have this issue. However I have to switch to [ru] everytime (because most of the time I obviously use russian layout).
Hope this helps.
P.S. I believe this bug could affect more people. But it is difficult to express it in a "google-way" and the workaround is not straightforward. So that people cannot find or discover both the workaround and this bug description. And they still suffer...
Hi, Pedro!
Thank you for your interest in this bug.
Yes, it is still an issue with Natty.
When the layout order [en, ru] and current layout = ru, then Ctrl-C, Ctrl-V and other shortcuts are working fine.
However, When the layout order is reverse [ru, en] and current layout = ru, then Ctrl-C, Ctrl-V and other shortcuts are not working. I have to switch current layout = en to make it work.
It was rather annoying actually. For instance, when in clipboard there is some secret and you chat with someone. Then you want to copy-paste something to the correspondent. You press Ctrl-C somewhere (but it didn't work). Then in the chat program you press Ctrl-Ins (which is working) and immediately press enter. Just to see that you've sent something wrong...
These days I use [en, ru] layout order which doesn't have this issue. However I have to switch to [ru] everytime (because most of the time I obviously use russian layout).
Hope this helps.
P.S. I believe this bug could affect more people. But it is difficult to express it in a "google-way" and the workaround is not straightforward. So that people cannot find or discover both the workaround and this bug description. And they still suffer...