Comment 47 for bug 1247668

My old laptop (a Samsung NP300E5Z, originally with Precise and upgraded all the way up to Yakkety) died a few days ago. I cannot tell for 100% but I'm like 99% sure that this bug still existed there in Yakkety, otherwise I pretty sure would have noticed being releived by the pain being gone while using Yakkety for about 1.5 months (since around its final beta freeze).

My new laptop (a Dell Inspiron 5559 210771, with a brand new Yakkety installation, same plain pretty much default Unity7, same two keyboard layouts and same Alt+Shift toggle configured) does not suffer from this bug. I enable NumLock, it looks like it stays enabled all the time.

In the mean time, changing the layout still switches off Caps Lock, including its feedback LED. Luckily I don't care about this too much.

At this point I have no clue whether:
- it was some system-wide leftover from the upgrade processes,
- it was some leftover in my home directory (I did not [yet] bring over my settings),
- or the behavior is somehow hardware related.