registry team mailing list archive

[Bug Watch Updater <374459@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 17 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=21766.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2009-05-16T06:42:00+00:00 Bmhm-nurfuerspam wrote:

Created an attachment (id=25905)
Xorg full configuration.

Overview:
On the acer aspire xxxx, there is a new button next to the touchpad. If you press it, the touchpad is switched off, and the button's LED is switched on. After that, you cannot switch the touchpad on again.

i.e.: There is no touchpad switch on FN+F5 anymore. It has moved.
Notebook (incl. Picture): https://wiki.ubuntu.com/LaptopTestingTeam/AcerAspire5738

Steps to Reproduce:
(1) Press the button - the touchpad is off, as expected
(2) Press the button again, so the button's LED is off
(3) Repeat as often as you like.

Actual Results:
Touchpad is still switched off.

Expected Results:
Touchpad switched on. 

Build Date & Platform:
Ubuntu 9.04 amd64

Additional Builds and Platforms:
Not really sure. I didn't test it on Vista, I removed it directly after buying. But it should work - explanation follows.

Additional Information:
Ok, now it gets a little complicated, or lets say, wired. "modprobe -r psmouse; modprobe psmouse" actually fixes it. 
If it is on and you run this command, the touchpad will work.
If it is off and you run this command, the touchpad is still switched off, but - tada - can be switched on. But if you switch it off again afterwards, the bug occurs again.

Conclusion: 
Switching on/off works until you switch it off for the first time.

Logs:
* dmesg - no output
* /var/log/messages - as above
* Button has keycode 200
* xmodmap -pk (attached)
* Xorg.0.log relevant excerpt

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: xserver-xorg-input-synaptics 0.99.3-2ubuntu4
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
SourcePackage: xfree86-driver-synaptics
Uname: Linux 2.6.28-11-generic x86_64

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/14

------------------------------------------------------------------------
On 2009-05-16T06:42:37+00:00 Bmhm-nurfuerspam wrote:

Created an attachment (id=25906)
excerpt of Xorg.0.log

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/15

------------------------------------------------------------------------
On 2009-05-16T06:43:13+00:00 Bmhm-nurfuerspam wrote:

Created an attachment (id=25907)
output of 'xmodmap -pk

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/16

------------------------------------------------------------------------
On 2009-05-16T06:43:41+00:00 Bmhm-nurfuerspam wrote:

Created an attachment (id=25908)
system specs as from ubuntu-bug

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/17

------------------------------------------------------------------------
On 2009-05-16T06:44:21+00:00 Bmhm-nurfuerspam wrote:

Created an attachment (id=25909)
setxkbmap

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/18

------------------------------------------------------------------------
On 2009-05-16T06:48:07+00:00 Bmhm-nurfuerspam wrote:

Bug entry in Launchpad:
https://bugs.launchpad.net/xorg-driver-synaptics/+bug/374459

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/19

------------------------------------------------------------------------
On 2009-05-18T02:58:16+00:00 Peter Hutterer wrote:

Please download http://people.freedesktop.org/~whot/evtest.c, compile it
with "gcc -o evtest evtest.c" and then run it as root with "./evtest
/dev/input/eventX" where X is the number for the device. You can get the
number by looking at /proc/bus/input/devices.

When the touchpad works,you should get the events as you use it. When
the touchpad does not work, do you still see events?

(btw. please do not attach excerpts of a log. In most cases, these
excerpts are missing vital information)

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/21

------------------------------------------------------------------------
On 2009-05-19T11:03:51+00:00 Bmhm-nurfuerspam wrote:

Created an attachment (id=26007)
full output of evtest

> When the touchpad works,you should get the events as you use it. 
I'm afraid not. I found out that my touchpad uses event9. But I get an error  just when the events should be comming.

> When the touchpad does not work, do you still see events?
Same as above, so just one file.

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/22

------------------------------------------------------------------------
On 2009-05-19T15:03:10+00:00 Peter Hutterer wrote:

> > When the touchpad works,you should get the events as you use it. 
> I'm afraid not. I found out that my touchpad uses event9. But I get an error 
> just when the events should be comming.

Oh sorry. I forgot that synaptics grabs the device. You need to VT switch
away and then run evtest from the tty. While X is running you'll get the
device information but not the events.

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/23

------------------------------------------------------------------------
On 2009-05-20T08:38:31+00:00 Bmhm-nurfuerspam wrote:

Hi,

well it's very confusing to me what actually has happened.
-------------------
TP=Touchpad
TPL= Touchpadbutton's LED aka Touchpad lock

1.)
TPbutton working, TPL off
output: events 

2.) 
TPbutton pressed. TPL on.
output: none

3.)
TPbutton pressed. TPL off.
output: none

4.)
TPbutton pressed. TPL on
modprobe -r psmouse; modprobe psmouse
output: events - on x the TP wouldn't work now

5.)
TPbutton pressed. TPL off.
output: events - on x the TP starts operating as the lock is gone

6.)
TPbutton pressed. TPL on.
output: none. 

7.) 
TPbutton pressed. TPL off.
modprobe...
output: events

8.) 
TPbutton pressed. TPL on
output: none

Seems pretty much like a hardware lock to me, but why do I see events
after reloading psmouse when the TP should be locked (#4)? On the other
hand, if it were a software issue, why does it handle it correctly on
step 4 to 5 in X?

Hope I got all combinations.

If you need more info, just tell me. Also, there is a full Xorg.0.log on
launchpad.

Regards and thanks for helping.

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/24

------------------------------------------------------------------------
On 2009-05-20T22:22:24+00:00 Peter Hutterer wrote:

Not an X bug, needs to be fixed in the kernel.

On a guess, I'd say that it's only a hardware lock for the LED, not for the touchpad itself. And the kernel doesn't (or can't?) query the state of the lock.
And it seems the kernel may not get the "on" event, only the "off" event. Hence this weird sequence of events. Only guessing here though.

Either way, there's nothing we can do in the X drivers until we get the
right sequence of events.

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/25

------------------------------------------------------------------------
On 2009-05-22T06:33:57+00:00 Bmhm-nurfuerspam wrote:

Allright, filed at kernel's bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=13363

What's confusing to me is, that I always get an keycode.

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/27

------------------------------------------------------------------------
On 2009-05-22T07:00:04+00:00 Bmhm-nurfuerspam wrote:

I just found out that the touchpad started working again after a while.
I'm not sure how to reproduce, but this means it might not be a harware
issue. Or maybe it resuming late.

I got this message when switching off again:
kernel: [ 6499.100541] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/28

------------------------------------------------------------------------
On 2009-05-22T07:00:37+00:00 Bmhm-nurfuerspam wrote:

Created an attachment (id=26112)
new messages and working touchpad

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/29

------------------------------------------------------------------------
On 2009-05-24T16:03:57+00:00 Peter Hutterer wrote:

ok, I'd need to you to do the following:
tail -f /var/log/Xorg.0.log (assuming this is your running X.log)
tail -f /var/log/messages

then switch the touchpad off and on again. wait until you see something
in messages about the device being there again, at this point the X log
should print a message too ("touchpad found"). Once this message is
printed, does the touchpad work? unfortunately, the touchpad driver
isn't very chatty and doesn't print much when the connection is lost.

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/30

------------------------------------------------------------------------
On 2009-10-08T19:34:33+00:00 Peter Hutterer wrote:

ping? any update on this?

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/32

------------------------------------------------------------------------
On 2009-11-10T11:35:01+00:00 Bmhm-nurfuerspam wrote:

Yes,

on linux kernel bugs, they said it's been fixed.
However, wasn't able to test it yet.

see here
https://bugs.launchpad.net/ubuntu/+source/xfree86-driver-synaptics/+bug/374459
and here
http://bugzilla.kernel.org/show_bug.cgi?id=13363

Vielen Dank!
Thanks for helping!

(Setting to invalid, since this is not a xorg-bug).

Reply at: https://bugs.launchpad.net/linux/+bug/374459/comments/37


** Changed in: xorg-driver-synaptics
   Importance: Unknown => Medium

-- 
Acer Aspire 5738G: touchpad can be switched off, but not on again
https://bugs.launchpad.net/bugs/374459
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for XOrg-Driver-Synaptics.