Ubuntu
input-utils package

lsinput protocol version mismatch error

Bug #628392 reported by Duncan McGreggor on 2010-09-01

This bug affects 11 people

Affects		Status	Importance	Assigned to	Milestone
	input-utils (Ubuntu)	Fix Released	High	Chase Douglas	Ubuntu ubuntu-10.10

Bug Description

Binary package hint: input-utils

When I try to run lsinput on my Lenovo T410s multitouch-enabled laptop, I get the following error:

$ sudo lsinput
[sudo] password for oubiwann:
/dev/input/event0
protocol version mismatch (expected 65536, got 65537)

Feature Freeze Exception Information:

Input-utils is hard coded to an evdev protocol version at build time. The Maverick kernel has a backwards compatible evdev version bump. As it is, there no input-utils tools work at all. A simple rebuild makes them work again.

---
Architecture: i386
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
Package: input-utils 0.0.20051128-4ubuntu1
PackageArchitecture: i386
ProcEnviron:
LANGUAGE=en_US.UTF-8
LC_CTYPE=C
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Tags: maverick ubuntu-une
Uname: Linux 2.6.35-19-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

See original description

Tags:

Related branches

lp:~chasedouglas/ubuntu/maverick/input-utils/lp628392

lp:ubuntu/maverick/input-utils

Revision history for this message

Duncan McGreggor (oubiwann) wrote on 2010-09-01: Dependencies.txt

Dependencies.txt Edit (545 bytes, text/plain)

apport information

tags:	added: apport-collected
description:	updated
summary:	- protocol version mismatch error + lsinput protocol version mismatch error

Revision history for this message

Cody Russell (bratsche) wrote on 2010-09-01:

I'm getting the same error on my Dell XT2, fully updated to latest Meerkat today.

Revision history for this message

Sundberg Pauli (susundberg) wrote on 2010-09-05:

Same error on Samsung N140, up-to-date, today.

Revision history for this message

Vsevolod Velichko (torkvemada) wrote on 2010-09-07:

Same error on HP TouchSmart tm2-1080er, up-to-date, today.

Revision history for this message

Pavel Mlčoch (pavkamlc) wrote on 2010-09-07:

The same on Lenovo T510 and latest Meerkat

Revision history for this message

Consumology (hans-georg-schmid) wrote on 2010-09-13:

And also on my HP tx2

Chase Douglas (chasedouglas) on 2010-09-17

Changed in input-utils (Ubuntu):
status:	New → In Progress
importance:	Undecided → High
assignee:	nobody → Chase Douglas (chasedouglas)
milestone:	none → ubuntu-10.10

Revision history for this message

Chase Douglas (chasedouglas) wrote on 2010-09-17:

input-utils_0.0.20051128-4ubuntu2_i386.build Edit (7.3 KiB, text/plain)

description:

updated

Revision history for this message

Chase Douglas (chasedouglas) wrote on 2010-09-17:

install.log Edit (311 bytes, text/plain)

Revision history for this message

Chase Douglas (chasedouglas) wrote on 2010-09-17:

debdiff Edit (552 bytes, text/plain)

Stefano Rivera (stefanor) on 2010-09-17

Changed in input-utils (Ubuntu):
status:	In Progress → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2010-09-17:

#10

This bug was fixed in the package input-utils - 0.0.20051128-4ubuntu2

---------------
input-utils (0.0.20051128-4ubuntu2) maverick; urgency=low

* Rebuild to update to the latest evdev protocol version. (LP: #628392)
-- Chase Douglas <email address hidden> Fri, 17 Sep 2010 21:28:17 +0200

Changed in input-utils (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

Dmitry Torokhov (dtor) wrote on 2010-11-16:

#11

Just rebuilding would mean that older kernels will not work. The check should be changed to "version >= 0x010000".

Revision history for this message

Chase Douglas (chasedouglas) wrote on 2010-11-17:

#12

Hi Dmitry,

This bug is only for the Ubuntu package (it's not obvious, but you can tell by the fact that the bug is against a package with "(Ubuntu)" in the name). Even more specifically, it's only a bug against the 10.10 version of Ubuntu.

As far as I can tell, the upstream source code is unmaintained. Since kernel versions will not change during the lifetime of a released version of Ubuntu, we don't really care too much about reworking this check for older kernels.

However, we will likely want to do something like this just for forward compatibility. I think there has been another version bump since 2.6.35, so we'll tackle this problem sometime during this Natty development cycle.

Thanks