[artful] Keyboard Logitech G15 doesn't work after logging in to gnome

[Ernst Persson]

After I type my password in GDM and come to the gnome desktop, no keys are working. Not even caps lock toggling.
However, I found out that if I toggle "Slow keys" in the accessibility settings, it starts working again!
To clarify, Slow keys and all other accessibility is disabled from start, but turning Slow keys on and off again makes my keyboard work.
I seem to have to do this once after every _reboot_.

This is on a system that has upgraded to Artful.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu5
Uname: Linux 4.13.0-rc2+ x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 14 21:04:46 2017
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-08-29 (16 days ago)

[Ernst Persson (ernstp)]

Also it doesn't matter if I use Gnome Xorg or Wayland or Ubuntu Xorg or Wayland.

[Ernst Persson (ernstp)]

Damn, I was certain that it was solved exactly when toggling Slow Keys, but next time that didn't work.
It's interesting that the problem remains after logging out, so I can't type my password anymore and log in a second time. Suggests it's outside the user session somehow...

[Ernst Persson (ernstp)]

Ok more clues. My keyboard is a Logitech G15 Gaming keyboard. It has lots of features, which present themselves to Linux as various devices. The regression somewhere around that.
And it's a userspace regression, the same kernel with Ubuntu 17.04 works fine.

If I connect a very plain USB keyboard that works fine, it's only the G15 that's giving problems.

So here's xinput from a Ubuntu where it works:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Razer Razer DeathAdder Chroma id=10 [slave pointer (2)]
⎜ ↳ Razer Razer DeathAdder Chroma id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ G15 Gaming Keyboard id=8 [slave keyboard (3)]
    ↳ G15 Gaming Keyboard id=9 [slave keyboard (3)]
    ↳ Razer Razer DeathAdder Chroma id=12 [slave keyboard (3)]
    ↳ G15 GamePanel LCD id=13 [slave keyboard (3)]
    ↳ Eee PC WMI hotkeys id=14 [slave keyboard (3)]

[Ernst Persson (ernstp)]

xinput when it's broken:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Razer Razer DeathAdder Chroma id=10 [slave pointer (2)]
⎜ ↳ Razer Razer DeathAdder Chroma id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ G15 Gaming Keyboard id=8 [slave keyboard (3)]
    ↳ G15 Gaming Keyboard id=9 [slave keyboard (3)]
    ↳ Razer Razer DeathAdder Chroma id=12 [slave keyboard (3)]
    ↳ G15 GamePanel LCD id=13 [slave keyboard (3)]
    ↳ Eee PC WMI hotkeys id=14 [slave keyboard (3)]
    ↳ Razer Razer DeathAdder Chroma id=15 [slave keyboard (3)]

[Ernst Persson (ernstp)]

Got it:

sep 15 19:39:45 mammut fwupd[2591]: failed to open: failed to ping G15 Gaming Keyboard: failed to receive: timeout
sep 15 19:39:45 mammut fwupd[2591]: failed to open: failed to ping G15 Gaming Keyboard: failed to send: failed to write: wrote -1 of 7
r

Uninstalling fwupd solves it.
Now let's see how to fix this properly...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ernst Persson (ernstp)]

This is fixed upstream, but it's not in a release yet.
Patch or git snapshot...?

[Mario Limonciello (superm1)]

Upstream is going to release 0.9.8 sometime soon(ish). Plan to bring that into Artful. For now, if this is busted for you you can generate packages from upstream too or remove fwupd.

[Alvin Cura (alvinc)]

This issue occurs for Logitech Gaming Keyboard G110 as well.

[Ernst Persson (ernstp)]

The upstream patch should fix it for all keyboards.

[Mark Cuypers (mark-cuypers)]

I have the same issue as well.
Logitech G15 keyboard. It works for a couple of seconds before it stops working.
Ik can login. I can logout (using mouse) and then I can't type my password anymore.
Also, when I disconnect the USB and reconnect it again, it works for a couple of seconds (5 or so)

[Nico Haesler (nhaesler)]

I don't know if this is the right place to ask, but can someone please bring the fixed fwupd into artful? It's been out for 20 days and this bug is affecting me and a few friends on several machines. I don't think this should be tagged low importance. There are a lot of new users who have no idea how to fix this problem.

[Mike G (mikeg321)]

Bitten by this bug too. Surprised it has not been added to 17.10 by now, or have I missed somehitng? I tried downloading a ver 1.0.2 .deb from upstream but ran into dependency issues and making my own package is not something I am sure on how to do. Waiting for a proper fix.

[Sketch (sorcher)]

can confirm this bug as well. Logitech G15 keyboard 2nd gen.
plugin the keyboard in and out a few times until it works properly usually works for me, and it even lasts until the next reboot.

Thanks to anyone working on this fix.

[Roberto Leinardi (leinardi)]

I just want to remember that, until we get a proper fix, there is a workaround available:

sudo apt remove fwupd

[Mario Limonciello (superm1)]

I don't believe we'll SRU any fix into artful as it is interim release that will EOL soon and the fix is in bionic.

For those affected in artful I would recommend to either:
1) Upgrade to bionic
2) Remove fwupd
3) blacklist the unifying plugin.

To blacklist the unifying plugin:
1) Modify /etc/fwupd/fwupd.conf
2) Adding unifying to the list of BlacklistPlugins
(eg https://github.com/hughsie/fwupd/blob/0_9_X/data/fwupd.conf#L16)
3) Reboot your system

[Rocky (brightstone8x)]

I'm still having this problem with Bionic, my keyboard is G613.
Can anyone help me plz!!!!!

[Rocky (brightstone8x)]

NVM, I've just unplug my unifying receiver and reinstall g15daemon and it works just fine now.