Mouse not changing focus to application or workspace after system update [closed]
Hello,
Yesterday I did an update on my Arch Linux and this broke i3. Now, whenever I move the mouse over to a different application or even to another workspace, the focus doesn't change. However, if I reload i3 (mod+Shift+r), it goes back to normal for a few seconds, and then stops working. Changing focus with the keyboard works as expected. Below is Pacman's log.
Any help is appreciated. Thank you.
[2014-01-21 15:44] [PACMAN] Running 'pacman -Syu'
[2014-01-21 15:44] [PACMAN] synchronizing package lists
[2014-01-21 15:44] [PACMAN] starting full system upgrade
[2014-01-21 15:47] [PACMAN] upgraded cogl (1.16.0-3 -> 1.16.2-1)
[2014-01-21 15:47] [PACMAN] upgraded device-mapper (2.02.104-1 -> 2.02.105-1)
[2014-01-21 15:47] [PACMAN] upgraded iw (3.11-1 -> 3.13-1)
[2014-01-21 15:47] [PACMAN] upgraded libgcrypt (1.6.0-1 -> 1.6.0-2)
[2014-01-21 15:47] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-01-21 15:47] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Starting build: 3.12.8-1-ARCH
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Starting build: 3.12.8-1-ARCH
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-01-21 15:47] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2014-01-21 15:47] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-01-21 15:47] [PACMAN] upgraded linux (3.12.7-2 -> 3.12.8-1)
[2014-01-21 15:47] [PACMAN] upgraded linux-headers (3.12.7-2 -> 3.12.8-1)
[2014-01-21 15:47] [PACMAN] upgraded lirc-utils (1:0.9.0-68 -> 1:0.9.0-69)
[2014-01-21 15:47] [PACMAN] upgraded lvm2 (2.02.104-1 -> 2.02.105-1)
[2014-01-21 15:47] [PACMAN] upgraded python-dbus-common (1.2.0-1 -> 1.2.0-2)
[2014-01-21 15:47] [PACMAN] upgraded ...
This seems to be a bug and therefore does not belong here. I'd suggest to downgrade i3-wm to 4.7-1 and see if problem persists. You may notify the package maintainer for Arch and/or [post a bug report](http://newticket.i3wm.org/). The [i3 log](http://i3wm.org/docs/debugging.html) may help with that.
Kernel upgrade, funny behavior: You did restart your machine after the update, right?
Yes, I restarted the machine. I was with an external monitor when I noticed this behavior, now on a single monitor this isn't happening anymore. I'll try with an external monitor tomorrow and see how it goes.