Hello Margarita, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.3+14.04.20140826-0ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1347735 Title: Lockscreen capslock detection doesn't work well with remapped capslocks Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Remapped keys to activate the caps-lock are not correctly detected by the unity lockscreen [Test case] 1. Configure the keyboard so that "Both shifts together toggles CapsLock" 2. Lock the screen using Super+L or menus 3. Press both shifts together to turn the capslock on 4. The lockscreen input field should show a warning 5. Press the shifts again, and the warning should be hidden [Regression potential] None ----------------- Version: 7.2.2+14.04.20140714-0ubuntu1 (trusty) Some users like to remap the way the activate capslock. For example, using gnome-tweak-tool it's possible to set the CapsLock key to behave as an extra Ctrl, or an extra Alt (or several other extras) and then set "Both shifts together toggle CapsLock". This works perfectly well inside Unity, the hardware keyboard led indicator shows up, etc. However, the lockscreen detector doesn't correctly warn or not warn when this setup is used. * If the lockscreen was activated with capslock on, then the double-shift makes capslock go away, but not the warning. * If the lockscreen was activated with capslock off, then the double-shift makes capslock on, but no warning shows up. I believe the problem is in this piece of code in unity- shared/TextInput.cpp: void TextInput::OnKeyUp(unsigned keysym, unsigned long keycode, unsigned long state) { if (!caps_lock_on && keysym == NUX_VK_CAPITAL) caps_lock_on = true; else if (caps_lock_on && keysym == NUX_VK_CAPITAL) caps_lock_on = false; } This is checking for specific key, instead of the fact that CapsLock was activated or not. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1347735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
