Bug 16327 - ETPS/2 Elantech Touchpad issue on Aspire One 725
Summary: ETPS/2 Elantech Touchpad issue on Aspire One 725
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-08 23:16 CEST by alain thomas
Modified: 2018-10-07 16:32 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description alain thomas 2015-07-08 23:16:58 CEST
Description of problem: ETPS/2 Elantech Touchpad not active on a fresh Mageia 5 install on a Aspire One 725


Version-Release number of selected component (if applicable):
Fonctionnalités
Molette émulée: âNon

Connexion
Bus: âisa

Identifiant du fabricant: â0x0002

Identifiant du périphérique: â0x000e

Divers
Fabricant: â

Description: âETPS/2 Elantech Touchpad

Module: âmouse0


(USB Microsoft Wheel mouse optical Ok)


Reproducible: 

Steps to Reproduce:
Comment 1 alain thomas 2015-07-09 21:25:48 CEST
found that Fn+F7 enable touchpad, and that acer-wmi should be blacklisted to keep the touchpad over reboot. Is this a right way ?
Comment 2 Samuel Verschelde 2016-11-01 13:37:20 CET
Sorry for the late triaging of this bug report. Assigning to kernel and drivers maintainer group for advice.

Component: Release (media or process) => RPM Packages
Assignee: bugsquad => kernel

Comment 3 Marja Van Waes 2018-05-03 08:14:07 CEST
Hi Alain,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 4 Marja Van Waes 2018-10-07 16:32:35 CEST
@ Alain:

No reply, so closing as OLD since Mageia 5 is no longer maintained.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

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


Note You need to log in before you can comment on or make changes to this bug.