I think this might be related:
journalctl -p 3 -xb
nov 15 12:53:55 cinnamon systemd-udevd[643]: event6: Failed to call
EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
sudo cat /proc/bus/input/devices | grep -C 5 event6
I: Bus=0019 Vendor= Product= Version=
N: N
Yes, Ctrl + zooms in and out. If we believe
https://www.microsoft.com/accessories/en-ww/products/keyboards/natural-
ergonomic-keyboard-4000/b2m-00012 (though my model is not B2M-00012 but
1048) , Microsoft intended the zoom slider on the keyboard to map to
zoom in and out, too.
--
You received
> As for the zoom in/out, I meant this:
that's typically done by holding "Ctrl" down and using scroll up/down to
zoom.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186
@ddstreet Thank for the explanation. (Myself, I don't know why the
keyboard behaves this way; I can imagine any option, e.g., a glitch of
the keyboard firmware or hardware, an unintended bug introduced by the
developers of the manufacturer, a cost-reducing design of the
manufacturer, or an politic
> Do you really mean it's broken?
by "broken", what I mean is it was designed with two separate HID-type
usb interfaces with identical identification
(vendor/product/model/revision ids) but with different operation.
> Is any combination of the sliding key with any modifier key(s)
> (such as Ctrl,
@ddstreet Thanks for the feedback. The keyboard has “Microsoft®
Natural® Ergonomic Keyboard 4000 v1.0”, “Model 1048” printed on its
bottom. The keyboard looks pretty standard to me from outside. Do you
really mean it's broken? Is any combination of the sliding key with any
modifier key(s) (suc
Ok here's my understanding of this:
Most keyboards report a single usb device 'interface' for the keyboard
(some have separate interface(s) for builtin mice or other non-keyboard
stuff). However, your keyboard reports two separate 'interfaces' for
your single keyboard. Unfortunately, both of the i
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186
Title:
Failed to call EVIOCSKEYCODE with scan c
In the meantime, I updated Ubuntu to groovy 20.10. My dmesg is
[0.00] microcode: microcode updated early to revision 0x28, date =
2019-11-12
[0.00] Linux version 5.8.0-33-generic (buildd@lgw01-amd64-036) (gcc
(Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35
OK. dmesg should be enough.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186
Title:
Failed to c
This command would disclose potentially sensitive information of a
production machine to the public; I won't do it unless given an
opportunity to anonymize the results upfront.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
This is more likely to be a kernel bug. Let's find out why IOCTL
EVIOCSKEYCODE failed.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubu
@kaihengfeng can you review this bug to see if you can tell what the
correct change to the hwdb should be?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186
Title:
Fa
After commenting the corresponding lines /lib/udev/hwdb.d/60-keyboard.hwdb out,
issuing
# systemd-hwdb update
and rebooting, the middle slider up/down keys stopped producing any effect
completely at least in Firefox (i.e., it got worse). The "Failed to call ..."
error is gone from the output of
# udevadm info /dev/input/event9
P:
/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.1/0003:045E:00DB.0003/input/input10/event9
N: input/event9
L: 0
S: input/by-path/pci-:00:14.0-usb-0:13.1:1.1-event-kbd
S: input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-if01-event-kbd
E:
# evemu-describe /dev/input/event8
# EVEMU 1.3
# Kernel: 5.4.0-42-generic
# DMI:
dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr:
# Input device name: "Microsoft Natural® Ergonomic Keyboard 4000"
# Input device ID: bus 0x03 vend
I rebooted once again to ensure that `sudo evtest` returns
/dev/input/event8: Microsoft Natural® Ergonomic Keyboard 4000
/dev/input/event9: Microsoft Natural® Ergonomic Keyboard 4000
The results of
# udevadm info /dev/input/event8
# udevadm info /dev/input/event9
# evemu-describe /dev/i
# evemu-describe /dev/input/event9
# EVEMU 1.3
# Kernel: 5.4.0-42-generic
# DMI:
dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr:
# Input device name: "Microsoft Natural® Ergonomic Keyboard 4000"
# Input device ID: bus 0x03 vend
# udevadm info /dev/input/event8
P:
/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9/event8
N: input/event8
L: 0
S: input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-event-kbd
S: input/by-path/pci-:00:14.0-usb-0:13.1:1.0-event-kbd
E:
DEVPA
Please ignore #8: at new boot, the device numbers have changed :-(.
Sorry, will post anew in short.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186
Title:
Failed to
With the original file /lib/udev/hwdb.d/60-keyboard.hwdb :
# udevadm info /dev/input/event8
P: /devices/platform/lis3lv02d/input/input9/event8
N: input/event8
L: 0
S: input/by-path/platform-lis3lv02d-event
E: DEVPATH=/devices/platform/lis3lv02d/input/input9/event8
E: DEVNAME=/dev/input/event8
E: M
> the lines /lib/udev/hwdb.d/60-keyboard.hwdb are still commented out
i think you also have to recreate the binary db after editing the file, with:
$ sudo systemd-hwdb update
and then reboot.
I think this has something to do with the keyboard providing multiple
event interfaces, can you gather i
@ddstreet However, if in sudo evtest I choose device 9 instead of device
8 and the lines /lib/udev/hwdb.d/60-keyboard.hwdb are in their original
state (i.e., active), I get this when pressing the slider up then down:
Event: time 1596495480.180989, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d
Ev
@ddstreet Similar stuff happens when I choose device 9 instead of device
8 and the lines /lib/udev/hwdb.d/60-keyboard.hwdb are still commented
out.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
I commented the lines out as shown here:
$ grep -A 4 Ergonomic /lib/udev/hwdb.d/60-keyboard.hwdb
# # Microsoft Natural Ergonomic Keyboard 4000
# evdev:input:b0003v045Ep00DB*
# KEYBOARD_KEY_c022d=up # zoomin
# KEYBOARD_KEY_c022e=down
@ddstreet : Will do. Before commenting out
# Microsoft Natural Ergonomic Keyboard 4000
evdev:input:b0003v045Ep00DB*
KEYBOARD_KEY_c022d=up # zoomin
KEYBOARD_KEY_c022e=down
from /lib/udev/hwdb.d/60-keyboard.hwdb , the output of `sudo evtest` is
this:
No device
it looks like the specific usb mapping adjustment for this kbd never got
finished in bug 1523675 so maybe that's needed to fix this
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/
this seems to be the same issue as bug 1389201, it's even the same kbd
in that bug. note while the scancodes match, the keycodes in the error
messages from that bug are different because in 2018 the hwdb mapping
was changed to set the scancodes from 'zoomin/zoomout' to the simpler
'up/down', and t
28 matches
Mail list logo
