Bug 18693

Summary: ALPS touchpad in Dell Latitude E6510 unusable under Plasma5
Product: Mageia Reporter: Frank Griffin <ftg>
Component: RPM PackagesAssignee: Nicolas Lécureuil <mageia>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: plasma5 CVE:
Status comment:

Description Frank Griffin 2016-06-12 21:17:01 CEST
A fresh install on the machine mentioned results in the touchpad either being completely unresponsive or very spotty in Plasma.  This touchpad has worked under previous MGA versions, so I looked around for configuration options, but enabling the touchpad in System Settings and enabling tap-to-click had no effect.

I was about to conclude that the touchpad had become damaged (this machine hasn't been used in a year or more), but on a whim I logged into GNOME.  Initially, the bahavior was the same, but within minutes the touchpad was functioning normally.  I logged out and back into Plasma, and the touchpad was now fine.

KDE used to have a kcmtouchpadrc file that had all sorts of configuration stuff in it.  The nearest I can find in Plasma is touchpadrc, which has about 4 lines none of which pertain to configuration.  Whatever's going on, GNOME appears to be able to autoconfigure the touchpad, Plasma can't, but once GNOME has, Plasma can piggyback on GNOME's work.

The only out-of-the ordinary thing is that the Dell has a mouse button embedded in the keyboard as well.  That works very well.

The spotty or unresponsive touchpad behavior also occurs in the installer and sddm, if that helps.
Marja Van Waes 2016-06-13 11:22:46 CEST

CC: (none) => marja11
Assignee: bugsquad => mageia

Comment 1 Frank Griffin 2016-06-13 14:23:45 CEST
This has turned out to be a hardware problem unlike any I have seen.  When the AC power cord is unplugged, the touchpad behaves normally in both Plasma5 and GNOME.  When it is plugged in, it misbehaves in both.

Status: NEW => RESOLVED
Resolution: (none) => INVALID