Waking up changes keyboard layout

[Jan Helbich]

After waking up from sleep I always get different keyboard layout - my default is EN, after waking up I always get CS. Also wireless adapter is always turned off.
Both issues are very annoying since I'm used to login with English keyboard layout. Also after logging in I have to manually turn wifi on.

Using latest 15.04 with 3.19.0-28-generic kernel. A part of syslog after waking up is below:

systemd[1]: Unit bluetooth.target is not needed anymore. Stopping.
systemd[1]: Stopped target Bluetooth.
systemd[1]: Stopping Bluetooth.
systemd[1]: Stopping Load/Save RF Kill Switch Status of rfkill0...
systemd-sleep[6544]: System resumed.
systemd[1]: Started Suspend.
systemd[1]: Unit sleep.target is not needed anymore. Stopping.
systemd[1]: Stopped Load/Save RF Kill Switch Status of rfkill0.
bluetoothd[804]: Unregister path: /org/bluez/804/hci0
bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/A2DPSink
bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/A2DPSource
bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/HFPAG
bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/HFPHS
NetworkManager[4215]: <info> WiFi now disabled by radio killswitch
NetworkManager[4215]: <info> wake requested (sleeping: yes enabled: yes)
NetworkManager[4215]: <info> waking up...
NetworkManager[4215]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill2...
systemd[1]: Stopped target Sleep.
systemd[1]: Stopping Sleep.
systemd[1]: Reached target Suspend.
systemd[1]: Unit suspend.target is bound to inactive unit systemd-suspend.service. Stopping, too.
systemd[1]: Starting Suspend.
systemd[1]: Stopped target Suspend.
systemd[1]: Stopping Suspend.
systemd[1]: Started Run anacron jobs at resume.
systemd[1]: Starting Run anacron jobs at resume...
systemd[1]: Started Load/Save RF Kill Switch Status of rfkill2.
bluetoothd[804]: bluetoothd[804]: Unregister path: /org/bluez/804/hci0
bluetoothd[804]: bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/A2DPSink
bluetoothd[804]: bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/A2DPSource
bluetoothd[804]: bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/HFPAG
bluetoothd[804]: bluetoothd[804]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/BlueZ4/HFPHS
NetworkManager[4215]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1499484/+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.]

[Martin Pitt (pitti)]

Please only file one report per issue, using that for the keyboard problem. This has got nothing to do with systemd, it's most probably some (mis)configuration or misbehaviour of unity-settings-dameon.