[Bug 1247584] [NEW] [keymap] Since upgrade to Ubuntu 13.10, udev doesn't map middle mouse button.

Launchpad Bug Tracker 1247584 at bugs.launchpad.net
Mon May 26 11:06:18 UTC 2014


You have been subscribed to a public bug by Shock (mmiron):

On Ubuntu 13.04 I had the middle mouse button of my Logitech T400 mapped
correctly, but after upgrading to 13.10 the /lib/udev/kemap utility has
disappeared and now I can no longer assign the middle button to the
middle button function. This mouse has assigned by default the middle
button to the left_meta keyboard key (super key). That's very annoying
because I can't do middle clicking with this mouse. This mouse has two
middle buttons, in the trackpad that serves as middle wheel, but the
button that currently serves as middle click it's in a very
uncomfortable position, and the button with the left_meta functionality
is the one I'd like to use as middle button.

I tried modifying the file at /lib/udev/hwdb.d/60-keyboard.hwdb with
this rule:

keyboard:usb:v046DpC52B*
 KEYBOARD_KEY_700E3=middle

and also with

keyboard:usb:v046DpC52B*
 KEYBOARD_KEY_700E3=274

evtest returns the following results and codes:

BUTTON I WANT TO ASSIGN:
Event: time 1383485540.705610, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e3
Event: time 1383485540.705610, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 1
Event: time 1383485540.705610, -------------- SYN_REPORT ------------
Event: time 1383485540.809618, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e3
Event: time 1383485540.809618, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0
Event: time 1383485540.809618, -------------- SYN_REPORT ------------

THE BUTTON IN UNCOMFORTABLE POSITION
Event: time 1383485765.956075, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1383485765.956075, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1
Event: time 1383485765.956075, -------------- SYN_REPORT ------------
Event: time 1383485766.173978, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1383485766.173978, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0
Event: time 1383485766.173978, -------------- SYN_REPORT ------------

So, I would like to assign the BTN_MIDDLE function to the 700e3
scancode, but it does not work. With the previous utility included in
Ubuntu I could do this, but now with this SystemD way I can't do the
assignment.

I have not rebooted, but I did rebuild the hwdb database with the
"udevadm hwdb --update", and replugged the mouse.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: udev 204-0ubuntu19 [modified: lib/udev/hwdb.d/60-keyboard.hwdb]
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CustomUdevRuleFiles: 60-android-devices.rules
Date: Sun Nov  3 14:23:16 2013
InstallationDate: Installed on 2011-12-24 (680 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
MachineType: ASUSTeK Computer Inc. N53SN
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/ubunturoot-raiz ro quiet splash audit=1
SourcePackage: systemd
UpgradeStatus: Upgraded to saucy on 2013-10-28 (5 days ago)
dmi.bios.date: 01/10/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N53SN.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N53SN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SN.209:bd01/10/2012:svnASUSTeKComputerInc.:pnN53SN:pvr1.0:rvnASUSTeKComputerInc.:rnN53SN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: N53SN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: amd64 apport-bug saucy
-- 
[keymap] Since upgrade to Ubuntu 13.10, udev doesn't map middle mouse button.
https://bugs.launchpad.net/bugs/1247584
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list