ubuntu-x-swat team mailing list archive

[David Cramer <550625@xxxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Update: when I log in using KDE, the touchpad continues to work and
two-finger scrolling works. If I log in using Gnome, however, even in
Safe Mode or with "No Effects", the touchpad to stop working.

Any idea what in Gnome could be causing the problem or how to figure
that out?

Thanks,
David

On 09/22/2011 07:02 PM, David Cramer wrote:
> On 09/22/2011 04:13 PM, Seth Forshee wrote:
>> On Thu, Sep 22, 2011 at 07:57:42PM -0000, David Cramer wrote:
>>> Hi Seth,
>>>
>>> I'll be very happy to have multi-touch. Thank you for working on this.
> 
>> Note that "multi-touch" for this device is basically going to be
>> two-fingered scrolling. The data isn't good enough to do much more with
>> it.
> 
> That's fine. Two-fingered scrolling is all I really care about.
> 
> 
>>> 2. After rebooting and before logging in, the touchpad works as before.
>>> 3. After logging in, the touchpad stops working completely, but:
>>>     a. The pointer still works.
>>>     b. I now see a Touchpad tab in the mouse preferences, but changing settings had no effect on the non working touchpad.
> 
>> If it works in the window manager but not on the desktop, I don't think
>> the driver is to blame. You can prove this by switching to a virtual
>> console (e.g. Ctrl-Alt-F1) and running 'sudo lsinput', finding the Alps
>> touchpad device, and then running 'sudo input-events' with the device
>> number of the touchpad. If you see output spewing on the screen then you
>> move your finger on the touchpad, the driver is probably working
>> correctly.
> 
> Yes, that test indicates that the driver is working.
> 
>> If it is working correctly, the problem would seem to be elsewhere. I'm
>> not very familiar with debugging problems in those areas, but I'll share
>> what I do know. Return to the desktop (Ctrl-Alt-F7), open a terminal,
>> and run 'xinput list'. You should see an "ALPS DualPoint Touchpad"
>> device listed, followed by an id number. Run 'xinput --list-props <id>'
>> using the id for the touchpad. At the top there should be a line labeled
>> "Device Enabled", and the value should be 1. If it's not, run 'xinput
>> --set-prop <id> "Device Enabled" 1' and see if your touchpad works.
> 
> Ok. When I do that, I see:
> 
> dcramer@anatine ~
> $ xinput --list-props 13
> Device 'AlpsPS/2 ALPS DualPoint TouchPad':
> 	Device Enabled (121):	0
> ...
> 
> When I run:
> 
> dcramer@anatine ~
> $ xinput --set-prop 13 "Device Enabled" 1
> 
> The command completes without any error or output, but the touchpad
> doesn't start working and when I run --list-props again, "Device Enable"
> is still set to 0. If I do --set-prop while tailing /var/log/Xorg.0.log,
> I see:
> 
> [  9830.351] (--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
> 
> Let me know if there are any other things I can try or if there's any
> other information I can provide.
> 
> Thanks,
> David
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOffhtAAoJEMHeSXG7afUhOhQH/jVwXRg478joizLVgOqMVGJM
OP6cYb7+1WVd7gr2or6+Y1EYabb59/3hoxRt6FLe12gq6qE1onbgNimKQUoSJnQ2
vR34xIzVL++8O+411c5glNatM+5y62lMQ7UhiNf70Gz/7TCvqSRAw8CwIzgI+IHb
J7foVoedgyig8/B70fgvMYrKAnC//QVRb9jpgGIZKFNYM3Ze2TS+V2rvJUUdGILm
wiNjq0/+mnvHxq4j2i0kHeHdzkaGQSIOheyT/PrETa2ztPU04xUylD4SUUYHzJOv
s31cogJ5ckVjDudGy+rF//Kja06qynbowMH4jNGP4g7+iPmo4Frw+bSWzFc0ZW4=
=TLIM
-----END PGP SIGNATURE-----

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/550625

Title:
  Alps touchpad is recognized but synaptics clients and scrolling do not
  work

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/550625/+subscriptions