kernel-packages team mailing list archive
Mailing list archive
[Bug 1582678] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ELAN Clickpad not fully working
Status in linux package in Ubuntu:
I've got a Medion Akoya P2214T, which is a 2-in-1-device with a
touchscreen (eGalax, working fine with driver manually installed) and
The touchpad is detected as "ITE Tech. Inc. ITE Device(8910)" but
seems to be some kind of ELAN Clickpad, as it only has one physical
button, shows as "Elan Microelectronics" in lsusb and is detected as
"ELAN Clickpad" by Windows (and uses that driver).
Ubuntu seems to just use it as a generic mouse, as two-finger
scrolling and other multitouch functions are not working and there is
no touchpad configuration in Gnome's system settings.
The touchpad is connected using USB.
I: Bus=0003 Vendor=04f3 Product=0400 Version=0110
N: Name="ITE Tech. Inc. ITE Device(8910)"
H: Handlers=mouse0 event7
B: KEY=30000 0 0 0 0
Bus 001 Device 005: ID 04f3:0400 Elan Microelectronics Corp.
it does not show up in lshw at all, it seems it belongs with the keyboard:
product: ITE Device(8910)
vendor: ITE Tech. Inc.
physical id: 1
bus info: usb@1:3.1
configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
it is a fresh ubuntu gnome 16.04 installation, nothing modified but the eGalax driver and a "apt upgrade". I use a "4.4.0-22-generic" linux kernel.
I've already found similar problems, but they were marked as fixed in 3.x kernels / ubuntu 14.04.
To manage notifications about this bug go to: