keyboard shortcuts are not working while national layout active

[peerus]

I used to have this bug with geany editror in my old install. But after i've made clean install of ubuntu gnome 13.04 and upgraded it to 13.10 this bug appeared while working with libreoffice. If my active keyboard layout is En - everything is just perfect. If i'm on Ru-ssian layout ctrl-C ctrl-F ctrl-S don't work at all. Geany is working without any problems.

Please see my comments here https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1218322
May be these problems are related somehow.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: libreoffice-core 1:4.1.2~rc3-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sat Oct 5 12:14:55 2013
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2013-10-01 (3 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
SourcePackage: libreoffice
UpgradeStatus: Upgraded to saucy on 2013-10-03 (2 days ago)

[peerus (tsifra)]

Looks like this problem is not related directly with libreoffice. A can't lock my screen by ctrl-alt-L while i'm in russian layout, if i switch to english combination works as expected.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[loquens (loquens)]

For me, keyboard shortcuts (for example, Ctrl-A, Ctrl-S) stop working in RU layout in LibreOffice and other apps.
But if in LibreOffice they don't work in RU layout all the time, in Chrome they not working after changing layout, but if I switch to other application and then return to Chrome (still Ru layout), shortcuts working normal.
And even more strange behaviour for Chrome:
* after switch en->ru: Ctrl-T stops working, switch to other app and back - starts working
* Ctrl-A works all the time

[peerus (tsifra)]

loquens, please see https://bugs.launchpad.net/unity/+bug/1226962
this bug is duplicate