Unity keyboard shortcuts stopped working after update

Bug #1786922 reported by Diogo Miguel Constantino dos Santos on 2018-08-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)

Bug Description

After running the latest updates on 16.04, Unity keyboard shortcuts stopped working.
Examples of shortcuts that stopped working:
 * move window to a workspace other workspaces (shift + ctrl + alt + arrow key)
 * move to workspace (ctrl + alt + arrow)
 * make windows stick to edges (ctrl + super + arrow keys)

This breaks my workflow and renders Unity much less usable :(

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.5+16.04.20180221-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64

ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Aug 14 12:05:33 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
 virtualbox, 5.1.38, 4.15.0-29-generic, x86_64: installed
 virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
EcryptfsInUse: Yes
 Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:1313]
InstallationDate: Installed on 2018-01-30 (195 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic root=/dev/mapper/ubuntu--vg-root ro elevator=noop quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.08
dmi.board.asset.tag: Tag 12345
dmi.board.name: PRO
dmi.board.vendor: SLIMBOOK
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SLIMBOOK
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd10/27/2017:svnSLIMBOOK:pnPRO:pvrNotApplicable:rvnSLIMBOOK:rnPRO:rvrNotApplicable:cvnSLIMBOOK:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: PRO
dmi.product.version: Not Applicable
dmi.sys.vendor: SLIMBOOK
 (unity-panel-service:5568): Indicator-Appmenu-WARNING **: Already have a menu for window ID 71303185 with path /com/canonical/menu/4400011 from :1.93, unregistering that one

 (unity-panel-service:5568): Indicator-Appmenu-WARNING **: Already have a menu for window ID 71303213 with path /com/canonical/menu/440002D from :1.93, unregistering that one
version.compiz: compiz 1:
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Aug 14 12:00:39 2018
xserver.configfile: default

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

After searching on the web, I've found the information that this may have been caused by compiz deactivating plugins. So I suspect that it has deactivated: 'desktop wall' and 'grid'.

I've enabled them back and this seams to restore functionality. Can someone confirms me the cause andd the solution?

If the cause was this, how can I find the issue that led compiz to do this?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers