Caps Lock sometimes switches on CAPS mode instead of switching layouts

Bug #1294560 reported by Alexander
48
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I'm running 14.04 Beta with daily updates. I've got English (US) and Russian layouts, source switching is set to Caps Lock. However, if i'm typing fast I often have my input switched to CAPS mode instead of changing layout. Looks like that:
wwWWWWцццЦЦЦЦwwWWWWwwwцццЦЦЦЦwwWWWWWwwWW

I don't know which package is responsible for this bug and what can I do to investigate it.
---
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: xapg 2037 F.... pulseaudio
 /dev/snd/controlC1: xapg 2037 F.... pulseaudio
 /dev/snd/controlC0: xapg 2037 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=ff446442-f368-454d-8fc0-3b82e35f9163
InstallationDate: Installed on 2014-03-18 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=d9f42808-7350-427f-8823-4f20a0dc50c2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-18-generic N/A
 linux-backports-modules-3.13.0-18-generic N/A
 linux-firmware 1.126
RfKill:

Tags: trusty
Uname: Linux 3.13.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/19/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77-DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd09/19/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1294560/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
John Kim (kotux) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

tags: added: iso-testing
affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Alexander (jufofu) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Alexander (jufofu) wrote : BootDmesg.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : CRDA.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : Lspci.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : Lsusb.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : ProcEnviron.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : ProcModules.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : PulseList.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : UdevDb.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : UdevLog.txt

apport information

Revision history for this message
Alexander (jufofu) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Alexander (jufofu) wrote :

I've installed Ubuntu on 2014-03-18 (I believe it was daily build from 2014-03-17, was updated during installation), but barely used it that day, and I've noticed the issue on 2014-03-19, so I think it was there from the beginning.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Danil Ilinykh (woodroof) wrote :

Has the same behaviour on current (released) version (after update from 13.10).

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Danil Ilinykh (woodroof) wrote :

And sometimes CapsLock works like Shift, with or without layout change.

Revision history for this message
Mike (0x656b694d) wrote :

To ensure the switch I have to wait a couple of seconds after releasing the key, which annoys very much if you used to type fast.

Revision history for this message
astroiLL (astroill) wrote :

Работающий костыль. Чтобы переключатель раскладки CAPS LOCK работал нормально, приходиться ставить пакет gnome-tweak-tool и в нем в разделе "Клавиатура" пункт "Поведение клавиши CAPS LOCK" ставить в состояние "CAPS LOCK отключен". После этого включаем CAPS LOCK как переключатель раскладки. Ubuntu 14.10

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.