[REGRESSION 14.04] keyboard configuration systematically wrong after every boot

[Teo]

I have a spanish keyboard correctly configured as a spanish keyboard.
It's the only keyboard configuration I have.
On the upper right corner of the screen there's an indicator that reads "Es", and if I click it, "Spanish" is the only option and it is selected. All this is as expected.

This applies to both the laptop's built-in keyboard and an external usb keyboard that I always keep connected (together with an external screen) when my laptop is at home on my desktop.

SINCE THE UPGRATE TO 14.04, every time I boot, both keyboards start behaving as if they were US english keyboards.
[UPDATE: I think it's not systematically every time, more like randomly half of the times]

If I click on the Es indicator mentioned above, where "Spanish" already appears as selected, and I re-select it, it fixes the issue.

Also, for the external keyboard, another workaround that works is to unplug and replug the keyboard. After that, the keyboard works as expected as a Spanish keyboard.

Please don't tell me to update the bios, because this worked before on the same machine until recently. It broke with some update, most probably with the upgrade from 13.10 to 14.04.

P.S. I ran "ubuntu-bug keyboard-configuration", I don't know why "console-setup" got selected instead.
I'm not sure what package the issue belongs to, anyway.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: keyboard-configuration 1.70ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jun 17 14:15:21 2014
InstallationDate: Installed on 2013-10-11 (248 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: Upgraded to trusty on 2014-05-24 (23 days ago)

[Teo (teo1978)]

How many decades is it going to take to triage, let alone fix, this bug?

Still an issue in 15.10.

I'm confirming the bug despite it's my own because I have observed it on at least two computers.