[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

Had the same issue in Ubuntu 20.04. I plugged in a keyboard with a Numlock key and switch that off. That fixed it for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

Deactivating numlock before activting neo2 also fixed this issue for me. So it is an interference between those two. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

In my case, what helped was to remove package `numlockx` with `sudo apt- get purge numlockx`. This package `numlockx` was integrated into Xubuntu's startup with version 18.04 (see https://wiki.xubuntu.org/releases/18.04/release- notes#numlock). It always turns on Num Lock on startup, which is

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

** Changed in: xkeyboard-config Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1783987 Title: German Neo2 Problem with

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

Fine, thanks for that. As I use Neo 2 exclusively – no other keyboard layouts – there should be no further problems once the choice has been made. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

There is no reason to expect anything else. A live session and a fully installed system should behave identically in this respect. My own testing was on a fully installed Ubuntu 18.04. ** Changed in: xkeyboard-config (Ubuntu) Status: Incomplete => Confirmed -- You received this bug

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

Gunnar: Can you please make sure that NumLock is turned off when switching to Neo 2 and let us know if that helps. *** I tried that, and as you predicted, with NumLock turned off, the Neo 2 keyboard behaves normally. Does that mean I can go ahead and install 18.04, and everything will be fine?

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

Launchpad has imported 15 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=97024. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

I jumped at conclusions; sorry for that. I too see the issue you mention. However, I found an upstream bug report, and one of the ideas mentioned there was to disable NumLock. Once I had done so, the "German (Neo 2)" layout seemed to behave as expected. Can you please make sure that NumLock is

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

Thanks Gunnar :-) I don't think my report was invalid. I've been using Neo 2 for many years, so I know what it looks like when it works. So here's what happens in some more detail: 1. I insert a USB Stick with xubuntu-18.04-desktop-amd64.iso into my computer. 2. I start the computer and, by

[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

I think Neo 2 is it, but it's a complex keyboard layout. There are some hints in the file /usr/share/X11/xkb/symbols/de If you need help to understand how it's supposed to be used, please use one of the support resources, e.g. . There does not seem to be a bug here, so