[intrepid] cannot see touchpad tab in mouse configuration

Bug #267611 reported by zombiepig
76
Affects Status Importance Assigned to Milestone
x11proto-input (Ubuntu)
Fix Released
High
William Grant
xserver-xorg-input-synaptics (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-input-synaptics

The touchpad tab is still missing from preferences->mouse, even with intrepid with all updates installed.

I've attached my xorg.log file

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :
Revision history for this message
William Grant (wgrant) wrote :

What is the output when you run `xinput list-props "SynPS/2 Synaptics TouchPad"`?

Also please post the output of `dpkg -l | grep gnome-control-center`

Changed in xserver-xorg-input-synaptics:
status: New → Incomplete
Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

~$ xinput list-props "SynPS/2 Synaptics TouchPad"
Device 'SynPS/2 Synaptics TouchPad':
X Error of failed request: BadDevice, invalid or uninitialized input device
  Major opcode of failed request: 146 (XInputExtension)
  Minor opcode of failed request: 37 ()
  Serial number of failed request: 13
  Current serial number in output stream: 13

~$ dpkg -l | grep gnome-control-center
ii gnome-control-center 1:2.23.90-0ubuntu5 utilities to configure the GNOME desktop

Revision history for this message
William Grant (wgrant) wrote : Re: [Bug 267611] Re: [intrepid] cannot see touchpad tab in mouse configuration

zombiepig wrote:
> ~$ xinput list-props "SynPS/2 Synaptics TouchPad"
> Device 'SynPS/2 Synaptics TouchPad':
> X Error of failed request: BadDevice, invalid or uninitialized input device
> Major opcode of failed request: 146 (XInputExtension)
> Minor opcode of failed request: 37 ()
> Serial number of failed request: 13
> Current serial number in output stream: 13

Looks like you're running an old X server. Are you sure you've installed
all updates and rebooted?

--
William Grant

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :
Download full text (5.3 KiB)

Definitely installed all updates from main server, here's my current x server versions:

 ~$ dpkg -l | grep xorg
ii python-xkit 0.3.4 library for the manipulation of the xorg.con
ii xorg 1:7.4~1ubuntu1 X.Org X Window System
ii xserver-xorg 1:7.4~1ubuntu1 the X.Org X server
ii xserver-xorg-core 2:1.4.99.906-2ubuntu5 Xorg X server - core server
ii xserver-xorg-input-all 1:7.4~1ubuntu1 the X.Org X server -- input driver metapacka
ii xserver-xorg-input-evdev 1:2.0.3-2 X.Org X server -- evdev input driver
ii xserver-xorg-input-kbd 1:1.3.1-1ubuntu2 X.Org X server -- keyboard input driver
ii xserver-xorg-input-mouse 1:1.3.0-1build1 X.Org X server -- mouse input driver
ii xserver-xorg-input-synaptics 0.15.0+git20080820-1ubuntu5 Synaptics TouchPad driver for X.Org/XFree86
ii xserver-xorg-input-vmmouse 1:12.5.1-1ubuntu3 X.Org X server -- VMMouse input driver to us
ii xserver-xorg-input-wacom 1:0.8.1.3-0ubuntu2 X.Org X server -- Wacom input driver
ii xserver-xorg-video-all 1:7.4~1ubuntu1 the X.Org X server -- output driver metapack
ii xserver-xorg-video-apm 1:1.2.0-1build1 X.Org X server -- APM display driver
ii xserver-xorg-video-ark 1:0.7.0-1build1 X.Org X server -- ark display driver
ii xserver-xorg-video-ati 1:6.9.0+git20080826.a3cc1d7a-2ubuntu1 X.Org X server -- ATI display driver wrapper
ii xserver-xorg-video-chips 1:1.2.0-1build1 X.Org X server -- Chips display driver
ii xserver-xorg-video-cirrus 1:1.2.1-1build1 X.Org X server -- Cirrus display driver
ii xserver-xorg-video-fbdev 1:0.4.0-1build1 X.Org X server -- fbdev display driver
ii xserver-xorg-video-i128 1:1.3.0-1build1 X.Org X server -- i128 display driver
ii xserver-xorg-video-intel 2:2.4.1-1ubuntu2 X.Org X server -- Intel i8xx, i9xx display d
ii xserver-xorg-video-mach64 6.8.0-1build1 X.Org X server -- ATI Mach64 display driver
ii xserver-xorg-video-mga 1:1.4.9.dfsg-1 X.Org X server -- MGA display driver
ii xserver-xorg-video-neomagic 1:1.2.1-1build1 X.Org X server -- Neomagic display driver
ii xserver-xorg-video-nv 1:2.1.10-1ubuntu1 X.Org X server -- NV display driver
ii xserver-xorg-video-openchrome 1:0.2.902+svn579-1 X.Org X server -- VIA display driver
ii xserver-xorg-video-r12...

Read more...

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

Not sure if this helps, but here's my output from xinput list

~$ xinput list
"Virtual core keyboard" id=0 [XKeyboard]
 Num_keys is 248
 Min_keycode is 8
 Max_keycode is 255
"Virtual core pointer" id=1 [XPointer]
 Num_buttons is 32
 Num_axes is 2
 Mode is Relative
 Motion_buffer is 256
 Axis 0 :
  Min_value is 0
  Max_value is -1
  Resolution is 0
 Axis 1 :
  Min_value is 0
  Max_value is -1
  Resolution is 0
"SynPS/2 Synaptics TouchPad" id=2 [XExtensionPointer]
 Num_buttons is 12
 Num_axes is 2
 Mode is Relative
 Motion_buffer is 256
 Axis 0 :
  Min_value is 0
  Max_value is -1
  Resolution is 1
 Axis 1 :
  Min_value is 0
  Max_value is -1
  Resolution is 1
"Video Bus" id=3 [XExtensionKeyboard]
 Num_keys is 248
 Min_keycode is 8
 Max_keycode is 255
"AT Translated Set 2 keyboard" id=4 [XExtensionKeyboard]
 Num_keys is 248
 Min_keycode is 8
 Max_keycode is 255
"Macintosh mouse button emulation" id=5 [XExtensionPointer]
 Num_buttons is 32
 Num_axes is 2
 Mode is Relative
 Motion_buffer is 256
 Axis 0 :
  Min_value is -1
  Max_value is -1
  Resolution is 1
 Axis 1 :
  Min_value is -1
  Max_value is -1
  Resolution is 1

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Try with the numerical device ID instead of the name?

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

that gives me the same error:

~$ xinput list-props 2
Device 'SynPS/2 Synaptics TouchPad':
X Error of failed request: BadDevice, invalid or uninitialized input device
  Major opcode of failed request: 146 (XInputExtension)
  Minor opcode of failed request: 37 ()
  Serial number of failed request: 13
  Current serial number in output stream: 13

I actually get the same error for all devices, eg:
~$ xinput list-props 4
Device 'AT Translated Set 2 keyboard':
X Error of failed request: BadDevice, invalid or uninitialized input device
  Major opcode of failed request: 146 (XInputExtension)
  Minor opcode of failed request: 37 ()
  Serial number of failed request: 13
  Current serial number in output stream: 13

Revision history for this message
Marc (m-chabot) wrote :

I got the EXACT same error message using xinput with a Macbook pro 2nd edition...

My Ubuntu 8.10 64bit alpha5 system is up-to-date with all updates and freshly rebooted.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please try the driver from my PPA:

http://ppa.launchpad.net/tjaalton/ubuntu/pool/main/x/xfree86-driver-synaptics/

if that doesn't help, upgrade your kernel. There was a new version uploaded today.

Revision history for this message
Marc (m-chabot) wrote :

I have to make a correction: I'm on a Macbook Pro 3rd generation.

Same result using xfree86-drivers-synaptics, but at least the mouse pad reacts a bit more, so my mouse movement is normal... but no two-finger scrolling, and no configuration available through GUI.

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

No luck still with 2.6.27-3, and xserver-xorg-input-synaptics 0.15.2-0ubuntu1

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please attach the output of 'lshal'.

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

Here's my lshal output

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

I'm still seeing the same behaviour with alpha 6, same symptoms as in the previous comments.

Revision history for this message
unclebob (ralfhedenhos) wrote :

I have the exact same problem. No touchpad tab, and the same weird output from xinput -list-props ...
I'm running alpha6.

Revision history for this message
Lukas Sabota (punkrockguy318) wrote :

hey i'm also having the exact same issue. I have a Dell XPS M1530 laptop. I've attached my lshal output. I'm running the latest 8.10. I really hope this gets resolved before the release.

Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :

My trackpad is also not being detected. This is on an EEEPC 901, which is likely to be an important model to support.

I will attach lshal and xinput list output shortly.

Assuming that the default tap-to-click doesn't finish driving me over the edge first when it activates while I'm typing.

Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :
Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :

Marking confirmed. AFAICS, all information has been provided, and there are a number of reporters.

Changed in xserver-xorg-input-synaptics:
status: Incomplete → Confirmed
Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :
Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :
Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :

Update: I found out that my particular problem is that the EEEPC 901 has an Elantech touchpad, which apparently doesn't have a driver, causing the touchpad to be recognized as a Logitech Wheel Mouse (bug #123775).

Revision history for this message
Harvey Muller (hlmuller) wrote :

This is also broken on the Dell Inspiron 1420, i.e. the touchpad pad is missing here also. In Hardy the 1420 autoconfigured /etc/X11/xorg.conf with a Synaptics Touchpad section. This is not the case in Intrepid.

`xinput list-props "SynPS/2 Synaptics Touchpad"` results in:

    unable to find device SynPS/2 Synaptics Touchpad

This is to be expected, as `xinput list` identifies the touchpad as "AlpsPS/2 ALPS Glidepoint"

`dpkg -l | grep gnome-control-center` results in:

   ii gnome-control-center 1:2.24.0.1-0ubuntu2

So it looks like the Glidepoint is not being mapped to the Synaptics Touchpad as was the past behavior.

Attaching lshal.log, if there are other requests related to this comment, they will be addressed swiftly.

Thanks,

Harvey

Revision history for this message
William Grant (wgrant) wrote :

Harvey: Your touchpad is being recognised correctly (the right driver and capabilities are shown in lshal). What if you list the properties of the proper device name instead?

Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

I own a Macbook 3,1. Trackpad/Touchpad is recognized but I cannot configure two finger scrolling / right click support on 8.10 beta. Should I open a new Bug?

Revision history for this message
Harvey Muller (hlmuller) wrote :

William,

hmuller@mlab-1420:~$ xinput list-props "AlpsPS/2 ALPS GlidePoint"
Device 'AlpsPS/2 ALPS GlidePoint':
X Error of failed request: BadDevice, invalid or uninitialized input device
  Major opcode of failed request: 145 (XInputExtension)
  Minor opcode of failed request: 37 ()
  Serial number of failed request: 13
  Current serial number in output stream: 13

Revision history for this message
Alex Wauck (awauck) wrote :

bodom_lx, I think your problem is the same one described here. It looks like the touchpad is properly detected on all systems, but something about XInput device properties is broken. In fact, it seems that xinput list-props is broken on all systems, even ones that don't have touchpads.

Revision history for this message
Alex Wauck (awauck) wrote :

bodom_lx, I may have misunderstood. Are you saying that you have the touchpad tab, but you can't make two-finger scrolling and right-click support? What happens if you run xinput list-props as described above?

Revision history for this message
William Grant (wgrant) wrote :

Alex Wauck wrote:
> bodom_lx, I think your problem is the same one described here. It looks
> like the touchpad is properly detected on all systems, but something
> about XInput device properties is broken. In fact, it seems that xinput
> list-props is broken on all systems, even ones that don't have
> touchpads.

It's actually not broken on all systems; it works on all of mine, and I
don't know of many other cases where it doesn't. It's likely a bug in
xserver, and we're hoping the the new XI property API backport will fix
it. We can expect to see it in not too long, since the beta was just
released.

--
William Grant

Revision history for this message
William Grant (wgrant) wrote :

bodom_lx wrote:
> I own a Macbook 3,1. Trackpad/Touchpad is recognized but I cannot
> configure two finger scrolling / right click support on 8.10 beta.
> Should I open a new Bug?

There are no widgets in the UI for those at the moment. You can,
however, set them using xinput and add them to your session startup.

I'll hopefully be able to expose all properties through the Touchpad tab
for Jaunty, but it's too late for Intrepid.

--
William Grant

Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

Ok, let's try to be more precise:
As you know, macbooks do have scrolling trackpads, with one single button.
I see the touchpad tab, I may also play with its options but I can't make two-finger scrolling and right-click.
I also tried to follow this Wiki page, even if it's written for 8.04: https://help.ubuntu.com/community/MacBook_Santa_Rosa#Fix%20Touchpad
Obviously, it did not work..
Attac

Revision history for this message
techieMoe (techiemoe) wrote :

I have a Dell Inspiron 1520 and I clean-installed Beta 1 this morning. I've downloaded all the latest updates. My touchpad works fine for the most part (vertical scrolling but no horizontal, tap-to-click works), however I have no entries at all for the touchpad in my xorg.conf nor do I see the "Touchpad" tab in my Mouse control panel.

I'm using Intrepid kernel 2.6.27-4-generic 64-bit and Gnome 2.24.0.

In Hardy 64-bit I had both an entry in xorg.conf and a Touchpad tab. These have disappeared in Intrepid. I have run dpkg-reconfigure and nothing changed.

Revision history for this message
William Grant (wgrant) wrote :

techieMoe wrote:
> I have a Dell Inspiron 1520 and I clean-installed Beta 1 this morning.
> I've downloaded all the latest updates. My touchpad works fine for the
> most part (vertical scrolling but no horizontal, tap-to-click works),
> however I have no entries at all for the touchpad in my xorg.conf nor do
> I see the "Touchpad" tab in my Mouse control panel.
>
> I'm using Intrepid kernel 2.6.27-4-generic 64-bit and Gnome 2.24.0.
>
> In Hardy 64-bit I had both an entry in xorg.conf and a Touchpad tab.
> These have disappeared in Intrepid. I have run dpkg-reconfigure and
> nothing changed.

The xorg.conf issue isn't an issue - it's quite intentional. Input
devices are now autodetected through hal. The lack of Touchpad tab seems
to only affect some hardware, and is being worked on.

--
William Grant

Revision history for this message
Daniel Graziotin (dgraziotin) wrote :

Is this valid for macbooks,too? So there is not the needing to open a new bug, am I right?

Revision history for this message
®om (rom1v) wrote :

I have the same problem : https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/278736
in intrepid beta, kernel 2.6.27-5-generic

$ xinput list-props "SynPS/2 Synaptics TouchPad"
Device 'SynPS/2 Synaptics TouchPad':
X Error of failed request: BadDevice, invalid or uninitialized input device
  Major opcode of failed request: 148 (XInputExtension)
  Minor opcode of failed request: 37 ()
  Serial number of failed request: 13
  Current serial number in output stream: 13

My computer is ASUS F3SV-AK143C.
It worked in hardy.

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

slightly different behaviour with the latest xorg updates, now i'm getting:

nyall@bollo:~$ xinput --list-props "SynPS/2 Synaptics TouchPad"
Device 'SynPS/2 Synaptics TouchPad':
 Device Enabled: Fetch failure
 Synaptics Edges:
 Synaptics Finger:
 Synaptics Tap Time:
 Synaptics Tap Move:
 Synaptics Tap Durations:
 Synaptics Tap FastTap:
 Synaptics Middle Button Timeout:
 Synaptics Two-Finger Pressure:
 Synaptics Scrolling Distance:
 Synaptics Edge Scrolling:
 Synaptics Two-Finger Scrolling:
 Synaptics Edge Motion Pressure:
 Synaptics Edge Motion Speed:
 Synaptics Edge Motion Always:
 Synaptics Button Scrolling:
 Synaptics Button Scrolling Repeat:
 Synaptics Button Scrolling Time:
 Synaptics Off:
 Synaptics Guestmouse Off:
 Synaptics Locked Drags:
 Synaptics Locked Drags Timeout:
 Synaptics Tap Action:
 Synaptics Click Action:
 Synaptics Circular Scrolling:
 Synaptics Circular Scrolling Trigger:
 Synaptics Circular Pad:
 Synaptics Palm Detection:
 Synaptics Palm Dimensions:
 Synaptics Pressure Motion:
 Synaptics Grab Event Device:

Revision history for this message
William Grant (wgrant) wrote :

For everyone who has been having issues: upgrade (ensure you have the latest updates from the main mirror, not just your local one which might be days out of date!), reboot, and try again.

zombiepig: You need to reboot (or at least restart X).

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

William,

I just upgraded from the main mirrors and restarted. Now xinput gives me something similar to what zombiepig is reporting (Fetch failure), as opposed to an error as before. Setting any option doesn't have any effect.

What info should I provide? Thanks.

Revision history for this message
William Grant (wgrant) wrote :

Paulo: `dpkg -l | grep xorg | grep -v video`

Do you have the Touchpad tab visible in System->Preferences->Mouse?

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

Same as Paulo, I've updated from main, restarted and still get Fetch failure. No touchpad tab visible. Here's the xorg versions:

:~$ dpkg -l | grep xorg | grep -v video
ii python-xkit 0.3.6 library for the manipulation of the xorg.con
ii xorg 1:7.4~2ubuntu7 X.Org X Window System
ii xserver-xorg 1:7.4~2ubuntu7 the X.Org X server
ii xserver-xorg-core 2:1.5.1-1ubuntu3 Xorg X server - core server
ii xserver-xorg-input-all 1:7.4~2ubuntu7 the X.Org X server -- input driver metapacka
ii xserver-xorg-input-evdev 1:2.0.99+git20080912-0ubuntu3 X.Org X server -- evdev input driver
ii xserver-xorg-input-kbd 1:1.3.1-1ubuntu2 X.Org X server -- keyboard input driver
ii xserver-xorg-input-mouse 1:1.3.0-1build1 X.Org X server -- mouse input driver
ii xserver-xorg-input-synaptics 0.15.2-0ubuntu4 Synaptics TouchPad driver for X.Org/XFree86
ii xserver-xorg-input-vmmouse 1:12.5.1-1ubuntu3 X.Org X server -- VMMouse input driver to us
ii xserver-xorg-input-wacom 1:0.8.1.4-0ubuntu2 X.Org X server -- Wacom input driver

Revision history for this message
William Grant (wgrant) wrote :

Which versions of libxi6 and xinput do you have installed? This has got me very confused.

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

I apologize, my problem is not with a touchpad -- I didn't pay attention to the bug description. I just have the same issues with xinput. Not sure if I should open a new bug report just about xinput.

$ dpkg -l | grep xorg | grep -v video
ii python-xkit 0.3.6 library for the manipulation of the xorg.con
ii xorg 1:7.4~2ubuntu7 X.Org X Window System
ii xserver-xorg 1:7.4~2ubuntu7 the X.Org X server
ii xserver-xorg-core 2:1.5.1-1ubuntu3 Xorg X server - core server
ii xserver-xorg-input-all 1:7.4~2ubuntu7 the X.Org X server -- input driver metapacka
ii xserver-xorg-input-evdev 1:2.0.99+git20080912-0ubuntu3 X.Org X server -- evdev input driver
ii xserver-xorg-input-kbd 1:1.3.1-1ubuntu2 X.Org X server -- keyboard input driver
ii xserver-xorg-input-mouse 1:1.3.0-1build1 X.Org X server -- mouse input driver
ii xserver-xorg-input-synaptics 0.15.2-0ubuntu4 Synaptics TouchPad driver for X.Org/XFree86
ii xserver-xorg-input-vmmouse 1:12.5.1-1ubuntu3 X.Org X server -- VMMouse input driver to us
ii xserver-xorg-input-wacom 1:0.8.1.4-0ubuntu2 X.Org X server -- Wacom input driver

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

$ dpkg -l |grep libxi6
ii libxi6 2:1.1.3-1ubuntu4 X11 Input extension library

$ dpkg -l |grep xinput
ii xinput 1.3.0-1ubuntu3 Runtime configuration and test of XInput dev

Revision history for this message
William Grant (wgrant) wrote :

Is anybody experiencing this bug *not* using amd64?

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

i AM using amd64 here

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

I'm on 64bit too. If it really helps to have this tested on i386, I can install it on a spare partition and report back.

Revision history for this message
William Grant (wgrant) wrote :

If you can test the beta i386 live CD on identical hardware, that would be excellent.

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

Sure! Just keep in mind that all I can test is xinput, since I don't have a laptop. I'll test the live cd and then install, so I can test the new packages as well. Will report back in about an hour.

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

William,

First result: xinput works directly from the live CD. I can list and change properties just like I wanted in the first place. Would you like me to install and test the new packages as well?

$ xinput list-props "Logitech USB Trackball"
Device 'Logitech USB Trackball':
 Device Enabled: 1
 Middle Button Emulation: 2
  valid values: 0 1 2
 Middle Button Timeout: 50
 Wheel Emulation: 1
  valid values: 1 0
 Wheel Emulation X Axis: 0, 0
 Wheel Emulation Y Axis: 4, 5
 Wheel Emulation Inertia: 10
 Wheel Emulation Timeout: 200
 Wheel Emulation Button: 4
 Drag Lock Buttons: 0

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

OK -- I installed the i386 image and upgraded from the latest packages from the main servers. xinput still works like it did on the live CD. So it seems that, at least in my case, the issue has to do with x86_64.

What information can I supply from both installations that would be helpful? Also, if you have other bugs that you suspect are platform-dependent, feel free to ask me for a test. Before I wipe out the 32bit installation. : )

Revision history for this message
William Grant (wgrant) wrote :

After extensive testing on IRC, I'm fairly sure that it's amd64-specific. At least it seems to never affect i386 machines - other archs I'm not sure about. We're working on debugging it thanks to this new info.

Revision history for this message
William Grant (wgrant) wrote :

It seems that libxi or similar is playing up on amd64. GetWindowProperty works fine, but GetDeviceProperty sends something like this to the X server:

  92 27 06 00 04 00 00 00 6d 00 00 00 00 00 00 00 13 00 00 00 00 00 00 00

That and its response decode (with my modified xtrace) to:

  000:<:000b: 24: XInputExtension-Request(146,39): XIGetDeviceProperty property=0x4("ATOM") type=0x6d("Device Enabled") longOffset=0 longLength=19 deviceid=0 delete=false(0x00)
  000:>:0x000b:32: Reply to XIGetDeviceProperty: propertyType=0x0(unrecognized atom) bytesAfter=0 nItems=0 format=0 deviceid=0

The X server's response seems correct, given the bogus data the client gave it.

On i386, it sends:

  92 27 06 00 81 00 00 00 13 00 00 00 00 00 00 00 01 00 00 00 04 00 f5 05

Decoding to:

  000:<:000b: 24: XInputExtension-Request(146,39): XIGetDeviceProperty property=0x81("Device Enabled") type=0x13("INTEGER") longOffset=0 longLength=1 deviceid=4 delete=false(0x00)
  000:>:0x000b:36: Reply to XIGetDeviceProperty: propertyType=0x13("INTEGER") bytesAfter=0 nItems=1 format=8 deviceid=4

Changed in xserver-xorg-input-synaptics:
assignee: nobody → wgrant
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
oupablo (oupablo) wrote :

The original beta for Intrepid with the .5 headers recognized the touchpad fine. With the install of the .6 and .7 headers the touchpad, xserver-xorg-input-synaptics wasn't installed. After installation the touchpad worked fine. I'm not sure why the update for xserver didn't find the touchpad though.

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

William,

Very strange, could it be that the x86_64 version is using incompatible variable types? So the issue is more low level than what I had thought, since you found this behavior with libxi. Does hal rely on it too to change settings? I ask that because in my case making changes through hal seems to work.

Revision history for this message
William Grant (wgrant) wrote :

Paulo,

hal's option setting is just like xorg.conf's; it's done only upon device initialisation, and without the usual client/server model that X uses. xinput and the Touchpad tab in gnome-mouse-properties use XInput device properties, which are settable at runtime through the X11 protocol stream itself. libxi handles the client side of the required X11 extensions. It looks like some parts are being swapped - compare the incorrect data sent and what I believe should be sent:

Bad: 92 27 06 00 04 00 00 00 6d 00 00 00 00 00 00 00 13 00 00 00 00 00 00 00
Good: 92 27 06 00 6d 00 00 00 13 00 00 00 00 00 00 00 01 00 00 00 04 00 00 00

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

Ah, now I see, thanks for the explanation.

Wow, good eyes. I had only noticed that the first four values were the same, then thought there was corruption. So basically 04 00 00 00 is being inserted in the middle, when it should come at the end. Unfortunately, I don't know what to make out of this. If you have any suspicion of which source code I should look at, please don't hesitate to give me directions.

Revision history for this message
William Grant (wgrant) wrote :

gcc appears to feel it necessary to reorder those particular request and reply structs on the client side.

Revision history for this message
William Grant (wgrant) wrote :

jcristau worked it out - sizeof(Atom) is 8 on amd64, as it's defined as a long. Making it a CARD32 instead works.

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

Nice, this is great news! Thanks for staying on top of it, William!

Revision history for this message
William Grant (wgrant) wrote :
Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

William,

I downloaded the patches, applied them, and rebuilt the packages. It works! So my particular problem is solved. I hope this also solves the issue that other people were seeing. Thanks again.

Revision history for this message
zombiepig (nyall-zombiepigs) wrote :

I can also confirm the proposed patches fix the problem for me. I get correct output from xinput, and more importantly, the touchpad tab is reappearing in mouse configuration!

Nice work :)

Revision history for this message
William Grant (wgrant) wrote :

This x11proto-input debdiff is somewhat cleaner.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package x11proto-input - 1.4.3-2ubuntu4

---------------
x11proto-input (1.4.3-2ubuntu4) intrepid; urgency=low

  * 100-Add-Device-Properties-X-Input-1.5.patch: Define Atom as CARD32 in
    XIproto.h, as otherwise the protocol structs come out completely wrong on
    amd64. Thanks to Julien Cristau for working this out. (LP: #267611)

 -- William Grant <email address hidden> Wed, 15 Oct 2008 12:24:13 +1100

Changed in x11proto-input:
status: In Progress → Fix Released
Revision history for this message
alecwh (alecwh) wrote :

How can I apply this patch to my system? I'm on Ubuntu 8.10, and I believe this patch will fix my problem.

Revision history for this message
William Grant (wgrant) wrote :

The patch is already in Ubuntu 8.10. What is this problem that you are having?

Revision history for this message
alecwh (alecwh) wrote :

The problem is solved, it was something unrelated. I was unaware that 8.10 now uses "FDI" files for configuration.

Revision history for this message
Romain1101 (romainmadala) wrote :

I am having some problem with my synaptics touchpad using updated packages since yesterday :

https://bugs.launchpad.net/bugs/320804

I'm posting mine thinking that maybe someone will be able to help me !

Revision history for this message
Bryce Harrington (bryce) wrote :

I notice this is marked fixed for -input, however it still has an open task for -synaptics. Is there still something needing to be done for -synaptics or can this task be closed as well?

William Grant (wgrant)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.