After upgrading to Vivid, Cannot change language layout after waking from sleep mode

[David Cohen]

After upgrading to Vivid, Cannot change language layout after waking from sleep mode, either by keyboard or by layout indicator.
Workaround : open layout configuration deselect "configure layouts" Apply, select again "configure layouts" and OK.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Apr 27 10:15:03 2015
InstallationDate: Installed on 2013-12-17 (495 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to vivid on 2015-04-24 (3 days ago)
---
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015
 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CurrentDesktop: KDE
DistUpgraded: 2015-04-24 08:35:41,366 DEBUG enabling apt cron job
DistroCodename: vivid
DistroRelease: Ubuntu 15.04
DistroVariant: kubuntu
GraphicsCard:
 NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company ZBook 15 [103c:197b]
InstallationDate: Installed on 2013-12-17 (642 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
LightdmGreeterLog:
 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
LightdmGreeterLogOld:
 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
MachineType: Hewlett-Packard HP ZBook 15
NonfreeKernelModules: nvidia
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=30942efb-b4db-4aa6-a3cd-8a33b65a903f ro quiet
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Tags: vivid kubuntu
Uname: Linux 3.19.0-25-generic x86_64
UpgradeStatus: Upgraded to vivid on 2015-04-24 (149 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 10/25/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L70 Ver. 01.06
dmi.board.name: 1909
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 94.47
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.06:bd10/25/2013:svnHewlett-Packard:pnHPZBook15:pvrA3008CC10003:rvnHewlett-Packard:rn1909:rvrKBCVersion94.47:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ZBook 15
dmi.product.version: A3008CC10003
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Wed Jul 29 10:22:39 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.1-0ubuntu3

[penalvch (penalvch)]

David Cohen, thank you for reporting this and helping make Ubuntu better. Could you please run the following command from a terminal as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg 1448891

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[David Cohen (cdavid68)]

apport information

[penalvch (penalvch)]

David Cohen, as per http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5428369&swLangOid=8&swEnvOid=4060 an update to your computer's buggy and outdated BIOS is available (1.33). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then please mark this report Status New.

Thank you for your understanding.

[David Cohen (cdavid68)]

Hi Christopher,
You are right, upgrading the BIOS did help and the problem went away.
I'm still curious why this BIOS problem only appeared after upgrade to vivid.
But I think the bug can be marked as solved.

Thanks,

David

[penalvch (penalvch)]

David Cohen, when hardware drivers are updated to require a more strict adherence to BIOS standards and protocols,, a buggy and outdated BIOS manifests issues for that hardware. Despite this, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448891/comments/27 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.