Hide Forgot
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20110103 Fedora/3.6.13-1.fc14 Firefox/3.6.13 Lenovo S10-3s Ideapad - Integrated touchpad buttons do not work. Buttons do not work after fresh installation. However touchpad taps works well after enabled in GNOME Mouse settings. Reproducible: Always Steps to Reproduce: 1. Install Fedora 14 (also tested on F13) 2. Try to use integrated touchpad buttons Actual Results: Touchpad buttons do not work. As the touchpad taps are disabled by default, the system can not be controlled without external mouse. Expected Results: The integrated buttons should work. Even though the left button click can be in most cases successfully workarounded by touchpad taping, the right button has no useful workaround. Without right button click the GUI is very hard to control. There is one trick with two finger tapping what can emulate the right button click, but this is very unnatural and totally unfriendy. Also very hard to understand & explain to the end-user.
Created attachment 475750 [details] lspci output - just to identify the laptop There is nothing to fin here. Attached as convinience to others who suffer of this bug to identify if they match the laptop's hardware.
Could you go please through https://fedoraproject.org/wiki/Xorg/Input_Triage_Algorithm and attach all Log files mentioned there, please? Thank you
Created attachment 477309 [details] Xorg logfile
Created attachment 477310 [details] Customized touchpad configuration Although this file is customized config, it has no influence to required functionality.
Created attachment 477311 [details] evtest output
I've just installed Fedora 14 on one of these. The touch pad buttons didn't work during or immediately after the install. However I think updating the kernel to 2.6.35.11 from updates did the trick. It was either that or xorg, which where the two things I first updated, but I logged out of GNOME and back in again and the buttons didn't work. Only when I rebooted to get the updated kernel did they start working. Andrew
Thank you for notification Andrew. With the new kernel you mentioned it works now. So from my point of view the bug can be closed.
Works with update what brings kernel 2.6.35.11 & friends.