[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
This bug definitely depends on kernel version. Both the fix mentioned
above in #8
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/comments/8
and mainline kernel after this commit (found with reverse bisect), are
required. Marking as linux bug. Would be very nice if fix could make it
into Ubuntu 16.04 LTS.
:~/linux/linux$ git bisect bad
e075b3c898e4055ec62a1f0ed7f3b8e62814bfb6 is the first bad commit
commit e075b3c898e4055ec62a1f0ed7f3b8e62814bfb6
Author: Pali Rohár
Date: Wed Jun 15 21:49:13 2016 +0200
dell-wmi: Generate one sparse keymap for all machines
This patch reworks code for generating sparse keymap and processing WMI
events. It unifies procedure for generating sparse keymap and also unifies
big switch code for processing WMI events of different types. After this
patch dell-wmi driver does not differ between "old" and "new" hotkey type.
It constructs sparse keymap table with all WMI codes. It is because on some
laptops (e.g. Dell Latitude E6440) ACPI/firmware send both event types (old
and new).
Each WMI code in sparse keymap table is prefixed by 16bit event type, so it
does not change functionality on laptops with "old" hotkey support (those
without scancodes in DMI).
This allow us to distinguish between same WMI codes with different types in
sparse keymap. Thanks to this WMI events of type 0x0011 were moved from big
switch into sparse keymap table too.
This patch also fixes possible bug in parsing WMI event buffer introduced
in commit 5ea2559726b7 ("dell-wmi: Add support for new Dell systems"). That
commit changed buffer type from int* to u16* without fixing code. More at:
http://lkml.iu.edu/hypermail/linux/kernel/1507.0/01950.html
Signed-off-by: Pali Rohár
Tested-by: Michał Kępień
Reviewed-by: Michał Kępień
Tested-by: Gabriele Mazzotta
Signed-off-by: Darren Hart
:04 04 babec68576f8756c9b0ee28a7ca7496de1c3c41a
b2e0e8cffb710d6ef2bdb9d4634cbd8b65867a34 M drivers
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on device node
'/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Hi,
the symptom is this error message in my system's logs:
juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
code 190): Invalid argument
According to /proc/bus/input/devices the corresponding input device
is:
I: Bus=0019 Vendor= Product= Version=
N: Name="Dell WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input10
U: Uniq=
H: Handlers=kbd event9
B: PROP=0
B: EV=13
B: KEY=1000b0400 0 e 0
B: MSC=10
This laptop is a Dell Latitude E6520.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu6
Uname: Linux 4.6.3-040603-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: KDE
CustomUdevRuleFiles: 60-ssd-scheduler.rules
Date: Wed Jun 29 17:43:01 2016
EcryptfsInUse: Yes
MachineType: Dell Inc. Latitude E6520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0NVF5K
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
Fix may be dependent on kernel version; testing with stock kernel for Ubuntu 16.04, v4.4, results in: Jan 10 19:32:33 Bethany systemd-udevd[332]: Error calling EVIOCSKEYCODE on device node '/dev/input/event11' (scan code 0x100150, key code 190): Invalid argument Previous testing used kernel v4.9 from here: http://kernel.ubuntu.com /~kernel-ppa/mainline/?C=N;O=D -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
https://github.com/systemd/systemd/pull/5012 Change "KEYBOARD_KEY_150=f20" to "KEYBOARD_KEY_100150=f20" should fix this issue. Confirming this fix works here. Editing /lib/udev/hwdb.d/60-keyboard.hwdb with the change above followed by :~$ udevadm hwdb --update ~:$ udevadm trigger Enables mic mute key. -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
I have the same on Dell Latitude 7370 on Zesty daily iso & 16.04. Marking my other report as a duplicate of this one. -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654827] Re: Microphone mute Fn hotkey does not work on Dell Latitude 7370
*** This bug is a duplicate of bug 1597415 *** https://bugs.launchpad.net/bugs/1597415 I tested this just now using the Zesty daily iso, and my mic mute button doesn't mute the mic. I see in my log: Jan 9 10:46:18 ubuntu systemd-udevd[1086]: Error calling EVIOCSKEYCODE on device node '/dev/input/event15' (scan code 0x150, key code 190): Invalid argument Which is the same one referenced in the pull request above. ** This bug has been marked a duplicate of bug 1597415 systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument -- 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/1654827 Title: Microphone mute Fn hotkey does not work on Dell Latitude 7370 Status in systemd package in Ubuntu: New Bug description: Mic mute hotkey (Fn+F4)on Dell Latitude 7370 does not work. It generates a correct keycode but this is not translated into 'action'. Mic mute can be activated in software by ticking the mute checkbox, and this correctly activates the mic mute key's LED. Also present in Zesty daily ISO. :~$ acpi_listen button/micmute MICMUTE 0080 K PNP0C14:01 00d0 :~$ sudo showkey -k keycode 248 press keycode 248 release :~$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Sleep Button /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:AlpsPS/2 ALPS DualPoint Stick /dev/input/event7:AlpsPS/2 ALPS DualPoint TouchPad /dev/input/event8:DELL Wireless hotkeys /dev/input/event9:ELAN Touchscreen /dev/input/event10: Integrated_Webcam_HD /dev/input/event11: HDA Intel PCH Headphone Mic /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event15: Dell WMI hotkeys Select the device event number [0-15]: 15 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "Dell WMI hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 148 (KEY_PROG1) Event code 149 (KEY_PROG2) Event code 161 (KEY_EJECTCD) Event code 202 (KEY_PROG3) Event code 203 (KEY_PROG4) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 227 (KEY_SWITCHVIDEOMODE) Event code 236 (KEY_BATTERY) Event code 240 (KEY_UNKNOWN) Event code 248 (KEY_MICMUTE) Event code 431 (KEY_DISPLAYTOGGLE) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Testing ... (interrupt to exit) Event: time 1483869894.006318, type 4 (EV_MSC), code 4 (MSC_SCAN), value 100150 Event: time 1483869894.006318, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 1 Event: time 1483869894.006318, -- SYN_REPORT Event: time 1483869894.006416, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 0 Event: time 1483869894.006416, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu13 Uname: Linux 4.9.0-040900-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 80-canon_mfp2.rules Date: Sun Jan 8 10:07:22 2017 InstallationDate: Installed on 2016-05-15 (238 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude 7370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic root=UUID=d96256e6-13a6-46a5-ba80-2e121d8f8dab ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0MMWGJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd10/31/2016:svnDellInc.:pnLatitude7370:pvr:rvnDellInc.:rn0MMWGJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 7370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1654827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654827] [NEW] Microphone mute Fn hotkey does not work on Dell Latitude 7370
Public bug reported: Mic mute hotkey (Fn+F4)on Dell Latitude 7370 does not work. It generates a correct keycode but this is not translated into 'action'. Mic mute can be activated in software by ticking the mute checkbox, and this correctly activates the mic mute key's LED. Also present in Zesty daily ISO. :~$ acpi_listen button/micmute MICMUTE 0080 K PNP0C14:01 00d0 :~$ sudo showkey -k keycode 248 press keycode 248 release :~$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: Video Bus /dev/input/event6: AlpsPS/2 ALPS DualPoint Stick /dev/input/event7: AlpsPS/2 ALPS DualPoint TouchPad /dev/input/event8: DELL Wireless hotkeys /dev/input/event9: ELAN Touchscreen /dev/input/event10: Integrated_Webcam_HD /dev/input/event11: HDA Intel PCH Headphone Mic /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event15: Dell WMI hotkeys Select the device event number [0-15]: 15 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "Dell WMI hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 148 (KEY_PROG1) Event code 149 (KEY_PROG2) Event code 161 (KEY_EJECTCD) Event code 202 (KEY_PROG3) Event code 203 (KEY_PROG4) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 227 (KEY_SWITCHVIDEOMODE) Event code 236 (KEY_BATTERY) Event code 240 (KEY_UNKNOWN) Event code 248 (KEY_MICMUTE) Event code 431 (KEY_DISPLAYTOGGLE) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Testing ... (interrupt to exit) Event: time 1483869894.006318, type 4 (EV_MSC), code 4 (MSC_SCAN), value 100150 Event: time 1483869894.006318, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 1 Event: time 1483869894.006318, -- SYN_REPORT Event: time 1483869894.006416, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 0 Event: time 1483869894.006416, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu13 Uname: Linux 4.9.0-040900-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 80-canon_mfp2.rules Date: Sun Jan 8 10:07:22 2017 InstallationDate: Installed on 2016-05-15 (238 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude 7370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic root=UUID=d96256e6-13a6-46a5-ba80-2e121d8f8dab ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0MMWGJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd10/31/2016:svnDellInc.:pnLatitude7370:pvr:rvnDellInc.:rn0MMWGJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 7370 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1654827 Title: Microphone mute Fn hotkey does not work on Dell Latitude 7370 Status in systemd package in Ubuntu: New Bug description: Mic mute hotkey (Fn+F4)on Dell Latitude 7370 does not work. It generates a correct keycode but this is not translated into 'action'. Mic mute can be activated in software by ticking the mute checkbox, and this correctly activates the mic mute key's LED. Also present in Zesty daily ISO. :~$ acpi_listen button/micmute MICMUTE 0080 K PNP0C14:01 00d0 :~$ sudo showkey -k keycode 248 press keycode 248 release :~$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Sleep Button /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:AlpsPS/2 ALPS DualPoint Stick /dev/input/event7:AlpsPS/2 ALPS DualPoint TouchPad /dev/input/event8:DELL Wireless hotkeys /dev/input/event9:ELAN Touchscreen /dev/input/
[Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
Oops - spoke too soon. Bug still present. Seems to be not quite 100% reproducible - correct behaviour occurs for some programs and some window configurations (maximised vs windowed), and possibly depending on how many programs have been opened since boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
For other reasons, I just moved all my ~/.* config files to a backup directory, rebuilt and reinstalled the NVIDIA driver (from NVIDIA's package), and this bug is gone, on my workstation at least. Both laptop and workstation were upgraded from 12.04 to 14.04 (apt-get dist-upgrade) , so perhaps some stale config is the cause? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
Hi Stephen, I had the same thought, but the devices are very different - a laptop with Intel graphics and a workstation with NVIDIA graphics and two monitors (one rotated 90°), so it seems unlikely to be just a config problem. Is there some debug / config info that would help test your idea? On 17 October 2014 14:43, Stephen M. Webb wrote: > This sounds remarkably like an X11 configuration issue. The only time > I've ever seen anything like it is when a monitor gives incorrect EDID > information or physical screens are explicitly placed incorrectly within > the X11 virtual screen using xrandr. > > Could this possibly be a themeing issue? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1371590 > > Title: > Global menu bar snatches defeat from the jaws of victory, à la Windows > 95 Start button > > To manage notifications about this bug go to: > https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
I just noticed that on a fresh boot, with only 'Videos' application open, expected behaviour occurs (menu items appear with cursor hard to top of screen). BUT - when I open another application (Thunderbird) both it and 'Videos' go back to the buggy behaviour - menu items only appear with cursor slightly away from absolute top of screen. So behaviour is somewhat inconsistent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
OK, here's a little video from my phone showing the menu disappearing and reappearing as the cursor goes over it. ** Attachment added: "14090026.mp4" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1371590/+attachment/4214025/+files/14090026.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
Thanks for looking at this. It's 100% consistent for me, on two very different devices, so I'm surprised that everyone else is having such trouble reproducing it. Perhaps the cursors are the problem, and the pointer is more pointy than expected, after the upgrade? I wanted to attach screenshots but I see now the cursor is excluded from the capture, unlike previous versions. It's literally a one pixel row difference in position that hides the menu bar items. It almost looks as though the cursor point itself is extending beyond the top limit of the monitor (i.e. into negative y values). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
Yes, it's 100% reproducible. The global menu bar does appear, but only if the mouse is a little bit (one pixel or so) away from the top, and not right at the top of the screen. The global menu bar menu items disappear when the mouse is pushed to the very top of the screen and reappear when the mouse cursor is brought back down. It affects a multi-monitor setup on NVIDIA's proprietary drivers (Dell T7600 with GTX 680) and my single-monitor laptop (Vaio SZ650) with really old Intel GM965 open drivers. Both machines were upgraded from Ubuntu 12.04 LTS to 14.04 LTS. On 22 September 2014 14:08, Andrea Azzarone <1371...@bugs.launchpad.net> wrote: > It works here. Is this 100% reproducible? > > ** Changed in: unity >Status: New => In Progress > > ** Changed in: unity (Ubuntu) >Status: New => Incomplete > > ** Changed in: unity >Status: In Progress => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1371590 > > Title: > Global menu bar snatches defeat from the jaws of victory, à la Windows > 95 Start button > > To manage notifications about this bug go to: > https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371590] [NEW] Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
Public bug reported: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in “unity” package in Ubuntu: New Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
