Ubuntu
linux package

Elantech touchpad moves and clicks by itself

Bug #1216186 reported by Kemel Zaidan aka Legendario
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I am facing a very annoying hardware problem. It's so bad tha it makes hard even to report it: the mouse (touchpad in this case) keeps moving to the left side of the screen and clicking by itself. So all the programs on the Unity sidebar are keept being opened until the system gets without memory and very slow.

Since the hardware is a relatively new ultrabook, I tought a newer kernel could had solve this issue, so I upgrade to saucy. Everything worked well after the first boot which followed the upgrade but after rebooting again the same thing started to happen.

That's the device ID given by lsusb command:

Bus 003 Device 003: ID 04f3:0035 Elan Microelectronics Corp.

I also thought it could be a problem with the touchscreen, but dmesg gives me a lot of error messages for the touchpad, with seems to be recognized as a psmouse. Installing gpointing-device-settings package and openning the config tool shows no touchpad related options.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-generic 3.11.0.3.4
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kemel 1825 F.... pulseaudio
                      kemel 3109 F.... pulseaudio
Date: Fri Aug 23 23:35:13 2013
HibernationDevice: RESUME=UUID=45d838ad-e4f4-4fb6-a6d5-e0cc1be17b2a
InstallationDate: Installed on 2013-05-12 (103 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: TSINGHUA TONGFANG CO.,LTD X46F
MarkForUpload: True
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=7b9ffde6-ffed-440e-935e-454db7cdb1ba ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-2-generic N/A
 linux-backports-modules-3.11.0-2-generic N/A
 linux-firmware 1.113
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-08-19 (5 days ago)
dmi.bios.date: 07/03/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 65C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: X46F
dmi.board.vendor: TSINGHUA TONGFANG CO.,LTD
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr65C:bd07/03/2012:svnTSINGHUATONGFANGCO.,LTD:pnX46F:pvr0.1:rvnTSINGHUATONGFANGCO.,LTD:rnX46F:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:
dmi.product.name: X46F
dmi.product.version: 0.1
dmi.sys.vendor: TSINGHUA TONGFANG CO.,LTD

Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :
Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :
Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=11 [slave pointer (2)]
⎜ ↳ PS/2 Elantech Touchpad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ Integrated Camera id=10 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Kemel Zaidan aka Legendario (kemelzaidan)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

It's not a regression since it has always happened. This has happened since the begining on the first instalation with Ubuntu 13.04 and still persists on 13.10. I recently realized a very strange behavior which made me more confused than ever:

If I reboot the system, it suddenly start's to work properly. But the first cold boot always shows the problem. Usually I'd say it's a hardware problem, but I discarted that since the machine is in dual boot with Windows and everything works fine under it.

I'm clueless.

Revision history for this message
Brad Figg (brad-figg) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Please test latest development kernel (3.11.0-7.14)

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.11.0-7.14
Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

Unfortunately, it still exists. :-(

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc3-saucy/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Kemel Zaidan aka Legendario (kemelzaidan)
Changed in linux (Ubuntu):
status: Expired → Incomplete
Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

Sorry to take so long to test it, but this hardware was my mom's one, and she just can't test that to me. Besides that, I don't live close to her.

The latestest mainline kernel offered by jsalisbury seems to fix it. Will it be available on the next ubuntu releases??

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-fixed-upstream
Revision history for this message
rogergoll (rogergoll) wrote :

i'm using ubuntu 13.10 and have same problem .
In just a few moments after booting the system. The problem happens: The mouse moves alone and squeezes some error message appears on the console, but I could not paste it here or find the record of this error log.

--
if the problem occurs, I restart the computer again and the problem does not happen again in the same session.
This touchpad has several fuções at the time in ubuntu are disabled.
The ultrabook also has a touchscreen device of the same manufacturer.

Device 003: ID 04f3:0035 Elan Microelectronics Corp.

Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

Hi rogergoll,

try following what jsalisbury proposed, and install the mainline kernel. It fixed the problem for me.

Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

It seems I have been too positive. The problem still remains in the 14.04. The most strange thing is that everything works well if you can reboot the system

Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

It really seems a linux driver bug, since it happens also with Fedora 21 running on the same hardware with the exactly the same behavior: if you reboot system, the touchpad pointer behaves as it should.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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