Touchpad freezes with natty after some use

Bug #775675 reported by Sergio Callegari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

On an ASUS EEPC 1000h with a just installed ubuntu natty (32bit - hardware does not support a 64bit os).

After some use (a few minutes) the touchpad stops working. Plugging in an external mouse is the only way to proceed.

Differently from 151248, the touchpad does not seem to restart after some more time.

Touchpad was working perfectly with maverick, so this is definitely a serious rergression.

Evtest gives
evtest gives

sudo evtest /dev/input/event8

Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0xe version 0x0
Input device name: "ETPS/2 Elantech Touchpad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
    Event code 333 (Tool Doubletap)
    Event code 334 (Tool Tripletap)
    Event code 335 (?)

  Event type 3 (Absolute)
    Event code 0 (X)
      Value 480
      Min 8
      Max 1144
    Event code 1 (Y)
      Value 452
      Min 8
      Max 760
    Event code 16 (Hat0X)
      Value 120
      Min 4
      Max 284
    Event code 17 (Hat0Y)
      Value 113
      Min 4
      Max 188
    Event code 18 (Hat1X)
      Value 217
      Min 4
      Max 284
    Event code 19 (Hat1Y)
      Value 113
      Min 4
      Max 188
Testing ... (interrupt to exit)

Revision history for this message
Sergio Callegari (callegar) wrote :

Maybe solved.

For some reason after the update to natty I was getting two instances of syndaemon running simultaneously. Now I have made sure that only one is started and the issue appears to be gone.

Revision history for this message
IKT (ikt) wrote :

Glad to see it is working ok.

I'm going to close this bug for the time being, if the issue pops up again, please feel free to re-open. :)

Changed in ubuntu:
status: New → Invalid
Revision history for this message
Sergio Callegari (callegar) wrote :

It is about 3 days that the laptop works fine. So yes, I think it is ok to close the bug.
Sorry for the noise.

I wonder if it could be the case to express a "wish", to have checks in syndaemon to prevent it from starting twice and how.
Advice would be welcome. Better here or to mainstream?

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.