Lower touchpad button failing

My left touchpad button, the one down at the lower edge of the pad, is now only working when I press at the right 40% of the bar, pushing it anywhere else does nothing. How do I get access to this area?

LOL I tried to clean the dust out of a massive 17" SONY laptop my aunt had. I had to take off, like, 30 screws, the baseplate, the HDD assembly (???) and the optical drive.
Yeah, I had some trouble figuring out how to word "Average Battery Life". It's what it predicts you while you're doing basic word processing-like tasks. A rough range would work.
And the little tidbit on calculating works like: 80% predicts you 4 hours, then 4/0.80 (the decimal equivalent for a percent) gets you 5 hours. That extrapolation suggests that at 100% it would predict 5 hours.
I know my survey is a bit complex, but so far it seems that OS architecture, HDD manufacturer, and browser seem to have an effect on battery life.
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Similar Messages

Left touchpad button delay in web browsers

I'm at a loss to figure out what could be causing my left button on my touchpad to delay intermittently. On both Google Chrome (whether stable, beta or dev) and Firefox, the left button when pressed may not respond for up to a few seconds. This is most noticeable when using Google Street View and Google Maps, which refuse to change viewpoint when holding down the left button. It isn't a Flash fault because there is also a delay when highlighting text.
I can rule out the possibility of any hardware fault as the left button on the touchpad works fine elsewhere, within KDE (ie. drag and dropping works without delay or fault) and other applications.
Output of my X log:
[ 5.365]
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 5.365] X Protocol Version 11, Revision 0
[ 5.365] Build Operating System: Linux 3.8.7-1-ARCH x86_64
[ 5.365] Current Operating System: Linux TGHE 3.8.10-1-ARCH #1 SMP PREEMPT Sat Apr 27 12:36:59 CEST 2013 x86_64
[ 5.365] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=99d5896f-0144-4c5c-8c54-c11229ef01eb ro quiet
[ 5.365] Build Date: 17 April 2013 02:37:06PM
[ 5.365]
[ 5.365] Current version of pixman: 0.28.2
[ 5.365] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 5.365] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 5.365] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 28 21:34:03 2013
[ 5.367] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 5.368] (==) No Layout section. Using the first Screen section.
[ 5.368] (==) No screen section available. Using defaults.
[ 5.368] (**) |-->Screen "Default Screen Section" (0)
[ 5.368] (**) | |-->Monitor "<default monitor>"
[ 5.368] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 5.368] (==) Automatically adding devices
[ 5.368] (==) Automatically enabling devices
[ 5.368] (==) Automatically adding GPU devices
[ 5.369] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 5.369] Entry deleted from font path.
[ 5.370] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 5.371] Entry deleted from font path.
[ 5.371] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 5.371] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 5.371] Entry deleted from font path.
[ 5.371] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 5.371] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 5.371] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 5.371] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 5.371] (II) Loader magic: 0x7fcc20
[ 5.371] (II) Module ABI versions:
[ 5.371] X.Org ANSI C Emulation: 0.4
[ 5.371] X.Org Video Driver: 14.1
[ 5.371] X.Org XInput driver : 19.1
[ 5.371] X.Org Server Extension : 7.0
[ 5.373] (--) PCI:*(0:1:0:0) 10de:0dcd:1028:04b7 rev 161, Mem @ 0xd4000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[ 5.498] Initializing built-in extension Generic Event Extension
[ 5.498] Initializing built-in extension SHAPE
[ 5.498] Initializing built-in extension MIT-SHM
[ 5.498] Initializing built-in extension XInputExtension
[ 5.498] Initializing built-in extension XTEST
[ 5.498] Initializing built-in extension BIG-REQUESTS
[ 5.498] Initializing built-in extension SYNC
[ 5.498] Initializing built-in extension XKEYBOARD
[ 5.498] Initializing built-in extension XC-MISC
[ 5.498] Initializing built-in extension SECURITY
[ 5.498] Initializing built-in extension XINERAMA
[ 5.498] Initializing built-in extension XFIXES
[ 5.498] Initializing built-in extension RENDER
[ 5.498] Initializing built-in extension RANDR
[ 5.498] Initializing built-in extension COMPOSITE
[ 5.498] Initializing built-in extension DAMAGE
[ 5.498] Initializing built-in extension MIT-SCREEN-SAVER
[ 5.498] Initializing built-in extension DOUBLE-BUFFER
[ 5.498] Initializing built-in extension RECORD
[ 5.498] Initializing built-in extension DPMS
[ 5.498] Initializing built-in extension X-Resource
[ 5.498] Initializing built-in extension XVideo
[ 5.498] Initializing built-in extension XVideo-MotionCompensation
[ 5.498] Initializing built-in extension XFree86-VidModeExtension
[ 5.498] Initializing built-in extension XFree86-DGA
[ 5.498] Initializing built-in extension XFree86-DRI
[ 5.498] Initializing built-in extension DRI2
[ 5.498] (II) LoadModule: "glx"
[ 5.499] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 5.560] (II) Module glx: vendor="NVIDIA Corporation"
[ 5.560] compiled for 4.0.2, module version = 1.0.0
[ 5.560] Module class: X.Org Server Extension
[ 5.560] (II) NVIDIA GLX Module 313.30 Wed Mar 27 15:51:21 PDT 2013
[ 5.560] Loading extension GLX
[ 5.560] (==) Matched nouveau as autoconfigured driver 0
[ 5.560] (==) Matched nvidia as autoconfigured driver 1
[ 5.560] (==) Matched nv as autoconfigured driver 2
[ 5.560] (==) Matched vesa as autoconfigured driver 3
[ 5.560] (==) Matched modesetting as autoconfigured driver 4
[ 5.560] (==) Matched fbdev as autoconfigured driver 5
[ 5.560] (==) Assigned the driver to the xf86ConfigLayout
[ 5.560] (II) LoadModule: "nouveau"
[ 5.562] (WW) Warning, couldn't open module nouveau
[ 5.562] (II) UnloadModule: "nouveau"
[ 5.562] (II) Unloading nouveau
[ 5.562] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 5.562] (II) LoadModule: "nvidia"
[ 5.563] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 5.569] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 5.569] compiled for 4.0.2, module version = 1.0.0
[ 5.569] Module class: X.Org Video Driver
[ 5.570] (II) LoadModule: "nv"
[ 5.571] (WW) Warning, couldn't open module nv
[ 5.571] (II) UnloadModule: "nv"
[ 5.571] (II) Unloading nv
[ 5.571] (EE) Failed to load module "nv" (module does not exist, 0)
[ 5.571] (II) LoadModule: "vesa"
[ 5.571] (WW) Warning, couldn't open module vesa
[ 5.571] (II) UnloadModule: "vesa"
[ 5.571] (II) Unloading vesa
[ 5.571] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 5.571] (II) LoadModule: "modesetting"
[ 5.571] (WW) Warning, couldn't open module modesetting
[ 5.571] (II) UnloadModule: "modesetting"
[ 5.571] (II) Unloading modesetting
[ 5.571] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 5.571] (II) LoadModule: "fbdev"
[ 5.571] (WW) Warning, couldn't open module fbdev
[ 5.571] (II) UnloadModule: "fbdev"
[ 5.571] (II) Unloading fbdev
[ 5.571] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 5.571] (II) NVIDIA dlloader X Driver 313.30 Wed Mar 27 15:33:21 PDT 2013
[ 5.571] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 5.572] (++) using VT number 7
[ 5.596] (II) Loading sub module "wfb"
[ 5.596] (II) LoadModule: "wfb"
[ 5.596] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 5.597] (II) Module wfb: vendor="X.Org Foundation"
[ 5.597] compiled for 1.14.1, module version = 1.0.0
[ 5.597] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.597] (II) Loading sub module "ramdac"
[ 5.597] (II) LoadModule: "ramdac"
[ 5.597] (II) Module "ramdac" already built-in
[ 5.598] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 5.598] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 5.598] (==) NVIDIA(0): RGB weight 888
[ 5.598] (==) NVIDIA(0): Default visual is TrueColor
[ 5.598] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 5.599] (**) NVIDIA(0): Enabling 2D acceleration
[ 6.276] (WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-2
[ 6.283] (II) NVIDIA(0): NVIDIA GPU GeForce GT 555M (GF106) at PCI:1:0:0 (GPU-0)
[ 6.283] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 6.283] (--) NVIDIA(0): VideoBIOS: 70.06.32.00.03
[ 6.283] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 6.521] (--) NVIDIA(0): Valid display device(s) on GeForce GT 555M at PCI:1:0:0
[ 6.521] (--) NVIDIA(0): DFP-0
[ 6.521] (--) NVIDIA(0): DFP-1
[ 6.521] (--) NVIDIA(0): LGD (DFP-2) (connected)
[ 6.521] (--) NVIDIA(0): DFP-3
[ 6.521] (--) NVIDIA(0): DFP-0: 165.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
[ 6.521] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 6.521] (--) NVIDIA(0): LGD (DFP-2): 480.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): LGD (DFP-2): Internal DisplayPort
[ 6.521] (--) NVIDIA(0): DFP-3: 480.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[ 6.521] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 6.521] (**) NVIDIA(0): device LGD (DFP-2) (Using EDID frequencies has been
[ 6.521] (**) NVIDIA(0): enabled on all display devices.)
[ 6.530] (==) NVIDIA(0):
[ 6.530] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 6.530] (==) NVIDIA(0): will be used as the requested mode.
[ 6.530] (==) NVIDIA(0):
[ 6.530] (II) NVIDIA(0): Validated MetaModes:
[ 6.530] (II) NVIDIA(0): "DFP-2:nvidia-auto-select"
[ 6.530] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 6.534] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
[ 6.535] (--) NVIDIA(0): option
[ 6.535] (--) Depth 24 pixmap format is 32 bpp
[ 6.535] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 6.535] (II) NVIDIA: access.
[ 6.637] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 6.637] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 6.637] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 6.637] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 6.637] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 6.637] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 6.637] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 6.637] (II) NVIDIA(0): Config Options in the README.
[ 6.657] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
[ 6.747] Loading extension NV-GLX
[ 6.788] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 6.788] (==) NVIDIA(0): Backing store disabled
[ 6.788] (==) NVIDIA(0): Silken mouse enabled
[ 6.789] (==) NVIDIA(0): DPMS enabled
[ 6.789] Loading extension NV-CONTROL
[ 6.789] Loading extension XINERAMA
[ 6.789] (II) Loading sub module "dri2"
[ 6.789] (II) LoadModule: "dri2"
[ 6.789] (II) Module "dri2" already built-in
[ 6.789] (II) NVIDIA(0): [DRI2] Setup complete
[ 6.789] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 6.789] (--) RandR disabled
[ 6.794] (II) Initializing extension GLX
[ 6.891] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 6.891] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.891] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 6.891] (II) LoadModule: "evdev"
[ 6.891] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6.892] (II) Module evdev: vendor="X.Org Foundation"
[ 6.892] compiled for 1.14.0, module version = 2.8.0
[ 6.892] Module class: X.Org XInput Driver
[ 6.892] ABI class: X.Org XInput driver, version 19.1
[ 6.892] (II) Using input driver 'evdev' for 'Power Button'
[ 6.892] (**) Power Button: always reports core events
[ 6.892] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 6.892] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.892] (--) evdev: Power Button: Found keys
[ 6.892] (II) evdev: Power Button: Configuring as keyboard
[ 6.892] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 6.892] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 6.893] (**) Option "xkb_rules" "evdev"
[ 6.893] (**) Option "xkb_model" "evdev"
[ 6.893] (**) Option "xkb_layout" "gb"
[ 6.936] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
[ 6.936] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 6.936] (**) Video Bus: Applying InputClass "Keyboard Defaults"
[ 6.936] (II) Using input driver 'evdev' for 'Video Bus'
[ 6.936] (**) Video Bus: always reports core events
[ 6.936] (**) evdev: Video Bus: Device: "/dev/input/event7"
[ 6.936] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 6.936] (--) evdev: Video Bus: Found keys
[ 6.936] (II) evdev: Video Bus: Configuring as keyboard
[ 6.936] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2b/LNXVIDEO:00/input/input7/event7"
[ 6.936] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 6.936] (**) Option "xkb_rules" "evdev"
[ 6.936] (**) Option "xkb_model" "evdev"
[ 6.936] (**) Option "xkb_layout" "gb"
[ 6.937] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 6.937] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.937] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 6.937] (II) Using input driver 'evdev' for 'Power Button'
[ 6.937] (**) Power Button: always reports core events
[ 6.937] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 6.937] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.937] (--) evdev: Power Button: Found keys
[ 6.937] (II) evdev: Power Button: Configuring as keyboard
[ 6.937] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[ 6.937] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 6.937] (**) Option "xkb_rules" "evdev"
[ 6.937] (**) Option "xkb_model" "evdev"
[ 6.938] (**) Option "xkb_layout" "gb"
[ 6.939] (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
[ 6.939] (II) No input driver specified, ignoring this device.
[ 6.939] (II) This device may have been added with another device file.
[ 6.939] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 6.939] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 6.939] (**) Sleep Button: Applying InputClass "Keyboard Defaults"
[ 6.939] (II) Using input driver 'evdev' for 'Sleep Button'
[ 6.939] (**) Sleep Button: always reports core events
[ 6.939] (**) evdev: Sleep Button: Device: "/dev/input/event2"
[ 6.939] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 6.939] (--) evdev: Sleep Button: Found keys
[ 6.939] (II) evdev: Sleep Button: Configuring as keyboard
[ 6.939] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2/event2"
[ 6.939] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 6.939] (**) Option "xkb_rules" "evdev"
[ 6.939] (**) Option "xkb_model" "evdev"
[ 6.939] (**) Option "xkb_layout" "gb"
[ 6.941] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event14)
[ 6.941] (II) No input driver specified, ignoring this device.
[ 6.941] (II) This device may have been added with another device file.
[ 6.941] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
[ 6.941] (II) No input driver specified, ignoring this device.
[ 6.941] (II) This device may have been added with another device file.
[ 6.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
[ 6.942] (II) No input driver specified, ignoring this device.
[ 6.942] (II) This device may have been added with another device file.
[ 6.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event17)
[ 6.942] (II) No input driver specified, ignoring this device.
[ 6.942] (II) This device may have been added with another device file.
[ 6.943] (II) config/udev: Adding input device Laptop_Integrated_Webcam_2HDM (/dev/input/event6)
[ 6.943] (**) Laptop_Integrated_Webcam_2HDM: Applying InputClass "evdev keyboard catchall"
[ 6.943] (**) Laptop_Integrated_Webcam_2HDM: Applying InputClass "Keyboard Defaults"
[ 6.943] (II) Using input driver 'evdev' for 'Laptop_Integrated_Webcam_2HDM'
[ 6.943] (**) Laptop_Integrated_Webcam_2HDM: always reports core events
[ 6.943] (**) evdev: Laptop_Integrated_Webcam_2HDM: Device: "/dev/input/event6"
[ 6.943] (--) evdev: Laptop_Integrated_Webcam_2HDM: Vendor 0x408 Product 0x2fb1
[ 6.943] (--) evdev: Laptop_Integrated_Webcam_2HDM: Found keys
[ 6.943] (II) evdev: Laptop_Integrated_Webcam_2HDM: Configuring as keyboard
[ 6.943] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input6/event6"
[ 6.943] (II) XINPUT: Adding extended input device "Laptop_Integrated_Webcam_2HDM" (type: KEYBOARD, id 10)
[ 6.943] (**) Option "xkb_rules" "evdev"
[ 6.943] (**) Option "xkb_model" "evdev"
[ 6.943] (**) Option "xkb_layout" "gb"
[ 6.944] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
[ 6.944] (II) No input driver specified, ignoring this device.
[ 6.944] (II) This device may have been added with another device file.
[ 6.945] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
[ 6.945] (II) No input driver specified, ignoring this device.
[ 6.945] (II) This device may have been added with another device file.
[ 6.945] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
[ 6.945] (II) No input driver specified, ignoring this device.
[ 6.945] (II) This device may have been added with another device file.
[ 6.946] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event13)
[ 6.946] (II) No input driver specified, ignoring this device.
[ 6.946] (II) This device may have been added with another device file.
[ 6.946] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 6.946] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 6.946] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
[ 6.946] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 6.946] (**) AT Translated Set 2 keyboard: always reports core events
[ 6.946] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 6.946] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 6.946] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 6.946] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 6.946] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 6.946] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 6.946] (**) Option "xkb_rules" "evdev"
[ 6.946] (**) Option "xkb_model" "evdev"
[ 6.946] (**) Option "xkb_layout" "gb"
[ 6.947] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
[ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 6.947] (II) LoadModule: "synaptics"
[ 6.947] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 6.948] (II) Module synaptics: vendor="X.Org Foundation"
[ 6.948] compiled for 1.14.0, module version = 1.7.0
[ 6.948] Module class: X.Org XInput Driver
[ 6.948] ABI class: X.Org XInput driver, version 19.1
[ 6.948] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 6.948] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6.948] (**) Option "Device" "/dev/input/event9"
[ 6.967] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5398 (res 42)
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4728 (res 70)
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 6.967] (**) Option "VertEdgeScroll" "on"
[ 6.967] (**) Option "TapButton1" "1"
[ 6.967] (**) Option "TapButton2" "2"
[ 6.967] (**) Option "TapButton3" "3"
[ 6.967] (**) Option "CoastingSpeed" "0"
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6.967] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6.986] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event9"
[ 6.997] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
[ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.039
[ 6.997] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 6.998] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6.998] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 6.998] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 6.999] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 6.999] (II) No input driver specified, ignoring this device.
[ 6.999] (II) This device may have been added with another device file.
[ 7.000] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event8)
[ 7.000] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 7.000] (**) Dell WMI hotkeys: Applying InputClass "Keyboard Defaults"
[ 7.000] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
[ 7.000] (**) Dell WMI hotkeys: always reports core events
[ 7.000] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event8"
[ 7.000] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
[ 7.000] (--) evdev: Dell WMI hotkeys: Found keys
[ 7.000] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
[ 7.000] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event8"
[ 7.000] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 13)
[ 7.000] (**) Option "xkb_rules" "evdev"
[ 7.000] (**) Option "xkb_model" "evdev"
[ 7.000] (**) Option "xkb_layout" "gb"
[ 24.896] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 24.896] (**) NVIDIA(0): device LGD (DFP-2) (Using EDID frequencies has been
[ 24.896] (**) NVIDIA(0): enabled on all display devices.)
And my 50-synaptics.conf file (ignore the do not edit this file warning, it's been copied and pasted into the /etc/X11/xorg.conf.d/ directory):
# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
# Option "OptionName" "value"
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "VertEdgeScroll" "on"
Option "CoastingSpeed" "0"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
MatchDevicePath "/dev/input/event*"
EndSection
Section "InputClass"
Identifier "touchpad ignore duplicates"
MatchIsTouchpad "on"
MatchOS "Linux"
MatchDevicePath "/dev/input/mouse*"
Option "Ignore" "on"
EndSection
# This option enables the bottom right corner to be a right button on
# non-synaptics clickpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Default clickpad buttons"
MatchDriver "synaptics"
Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
# To disable the bottom edge area so the buttons only work as buttons,
# not for movement, set the AreaBottomEdge
# Option "AreaBottomEdge" "82%"
EndSection
# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Disable clickpad buttons on Apple touchpads"
MatchProduct "Apple|bcm5974"
MatchDriver "synaptics"
Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection
Thanks in advance

Hello kal33,
Welcome to the HP Forums!
I understand the left part of the clickpad is not working. To assist you, please try all of the steps in this HP document: Using and Troubleshooting the TouchPad or ClickPad (Windows 8)
If these steps do not help, then there could be a hardware issue. Since the computer is in warranty, I would contact HP phone support for hardware assistance. You can utilize this website to learn how to contact HP appropriately, based on your region: Contact HP Worldwide
Please let me know if you have any other questions or concerns. Thanks for bringing this issue to the HP Forums. Have a great day!
Mario
I worked on behalf of HP.

Touchpad buttons registered as two mouse devices

I have a Lenovo R500 which has two buttons below the touchpad and 3 buttons on top of it.
All buttons works as expected, except that if using top left mouse button then I cannot drag windows using the touchpad.
I played with xinput because I thought that it was just a question of remapping the buttons, but realized that the problem is more complicated. It turns out that the lower buttons are attached to device 12 (which is the touchpad) and the top buttons are attached to device 11 (which belongs to the famous red stick mouse). So dragging a window only works when using top left button and the red stick or lower left button and touchpad.
In Windows it is possible to use the top buttons with the touchpad, the question is, can I bind the two devices together in Ubuntu as well?
Using Ubuntu 13.10

Hi all,
with my XPS 13 I had the known problem with the synaptics drivers. I solved compiling and upgrating the kernel to the last 3.16rc7 with "<M> Synaptics RMI4 device support" option. Touchpad is now completely functional but the touchscreen works just as a pointer without recognizing taps or gestures. Do you have the same problem or there is something wrong with my config?
[fabio@elizaveta ~]$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ DLL060A:00 06CB:2734 id=9 [slave pointer (2)]
⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=12 [slave pointer (2)]
[fabio@elizaveta ~]$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=06cb Product=0af8 Version=0111
N: Name="SYNAPTICS Synaptics Large Touch Screen"
P: Phys=usb-0000:00:14.0-3/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:06CB:0AF8.0002/input/input15
U: Uniq=
H: Handlers=event13 mouse1
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=260800000000003
[fabio@elizaveta ~]$ lsmod | grep hid
hid_multitouch 9721 0
usbhid 41251 0
hid_rmi 8694 0
i2c_hid 11163 0
hid 97340 4 i2c_hid,hid_multitouch,hid_rmi,usbhid
mac_hid 3273 0
usbcore 192792 6 btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd
i2c_core 41648 9 drm,i915,i2c_i801,i2c_hid,i2c_designware_platform,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
Thank you very much guys!
Fabio
Edit:
Forget me. The problem is that I was testing the touch screen in Chromium and, in this case, it works properly just setting the device as "floating slave" in xinput (command: xinput float #id).
Last edited by pexino (2014-07-31 22:14:29)

Random shut down and wonky touchpad/button

Hello!
I've noticed that for the past few months, when I begin to type something, I often have problems with the text highlighting unexpectedly. Sometimes what I've been typing gets deleted, other times I'm taken back to a few pages prior. I have problems clicking on links at times. Either the button wants to click on 12 different things at once, or it doesn't seem to want to click at all, just highlighting. It's a constant struggle with the touchpad button.
About a week ago my mac also started to spontaneously shut down. Possibly when it gets too hot? I can't seem to find a pattern to it, and it's shut down on its own both plugged in and on battery power.
My hard drive is about 2 years old now, but the computer is 3. Is this the result of too much use or can something be done to troubleshoot?

I've had that random shut-down problem for a week now. It did it again a few minutes ago. I thought it might have been a heat-related problem, but I have the back of the computer propped up to increase the ventilation on the rear.
I've had that sticky mouse problem several months now, ever since the local shop replaced the trackpad-plate. I didn't ask the shop to replace; I took the computer in to replace the failed hard drive. But the plate had been chipping around the edges, and apparently Apple had a secret warranty on the plate, so the shop replaced the chipped cover for free. Shortly afterward the mouse started sticking and acting weird. I think I have found a work-around by not placing my thumbs on the mouse. The mouse seems to be elevated now; when I close the lid while the computer is on, the pressure on the mouse causes the computer to activate whatever the cursor is on.

How to deal with those pesky touchpad buttons

The Pavilion series laptops are really well made in a lot of respects. I have owned my DV5t for almost 4 years now and I've been quite happy with it (except for rather anemic battery life). There is one thing that became a nasty problem for me, that being the left touchpad button. It is the most commonly used touchpad button and unfortunately these buttons were not well designed. They can easily break after a certain number of hits, whereby there's no longer any spring to it. Pressing the button ends up getting double-taps like mad. Also, the silver coating on them tends to wear away, looking rather unsightly over time. Once you start seeing the black plastic beneath, it won't be long before the button breaks. It's really a shame, because these tactile feel buttons work well--they just don't last. The newer HP laptops have those "lite touch" buttons which I do not like. The tactile feel is so much better. Unfortunately, it seems like most laptop makers are going with those solid state buttons to avoid another component that might go wrong. It's a shame, because with just a little more effort they could have been designed to last a very long time.
As of this writing, I have now gone through TWO of these touchpads. How did I manage to get another two chances? Well, they can be replaced but unfortunately they require you to disassemble more than half of the laptop. You see, the touchpad is integrated into the palm bezel, and the palm bezel is a piece of plastic coated metal that runs all the way to the back of the laptop. To get at it requires about an hour of taking the laptop apart. It's not for the faint of heart either. However, there is a service manual available that shows you what to do and I was able to follow it... thrice. Yes, the first button wore out after just under 2 years. The second one held up about as long. I use the touchpad buttons frequently, so... well, needless to say, now that I've got the 3rd bezel in place, I am going to rely mostly on an external mouse. And when I have to use the touchpad, I am going to use it very carefully, not exerting too much pressure (note that you can also tap the touchpad itself for a single click, something good to get into the habit of doing). Additionally, I'm going to put a sheet of protector plastic on the left mouse button to help avoid wearing out the surface.
So... one hour to disassemble it and a little more than an hour to reassemble it. It looked daunting to do at first, but believe me if you're patient and can follow instructions it is definitely doable. You don't need to be an HP tech to do it.
As for the parts, I obtained them from eBay. Apparently there are a lot of excellent condition used parts available from a variety of sources. I got the bezel for just under $30 shipped. Also, the speaker grille part is metal and tends to dent, so this time around I replaced it as well as the keyboard (the original was fine, but just a little touchy on one or two keys). With all 3 of these parts replaced, my laptop feels like new all over again. As for obtaining parts, you'll need to do your homework with the HP parts finder. There are many variants of the Pavilion laptop models with many parts in common, so the part you need can vary by number. The parts catalog can help you find them.
Anyway, that's about it. After having done this for the 3rd time, I figured there might be others out there with this problem on the brink of tossing out the laptop or selling it for parts on the cheap. It's salvageable!
"If you keep an open mind, life will give you more possibilities."

Thank you for your information and support. I may have to replace my touch pad and keyboard and you have given me hope and confidence. Thank you again,
Jackson Gal

My low volume button doesn't work on my Iphone 4, how can I fix it?

Okay so I dropped my iphone in the parking lot garages of my apartment complex and the ground was cement, when i picked it up the screen wasn't cracked or anything so i thought it was okay but once i started listening to music and I wanted to lower the volume and so I pushed the low volume button but nothing happen....The high volume button works fine but now the low volume button so if you want to lower the volume on my phone now you have to do it manually....Also after the drop i turned off silent mode on the side and the clicking sound wasn't there and I checked in the settings, it said it was on and the volume was on but I heard no clicking sound!!! How can I solve these two problems? Can I go to an Apple Store and let them fix my iphone if I don't have AppleCare?

Hi there Jaz94,
I would recommend taking a look at the troubleshooting steps found in the article below.
iPhone: No sound or distorted sound from speaker
http://support.apple.com/kb/ts5180
-Griff W.

Lower volume button not working

Lower volume button not working

Take it to the Genius Bar while you are still under warranty and they should be able to fix it. I went, one day after my warranty expired. While they confirmed the problem in my iPhone 5, they said it would be $269 to fix. The tech did helpfully show me how there's a much less convenient softkey workaround using General >Accessibility > AssistiveTouch. Not happy about it.

Power button fails to work about 95% of the time

Hello,
I have a Toshiba P205-S6267 that is having a strange issue.
About 95% of the time the power button fails to work when on battery, and it fails 100% of the time when the AC adapter is plugged in.
I am getting pretty stumped on this one and starting to think I may need to replace the 7-button circuit under the power button. Before I spend the $55 to do that, I wanted to see if anyone had any advice for me.
Here are the things I have tried.
- the standard unplug the power / battery and wait a few minutes then plug it back in.
- tried this only on battery, same issue
- tried only on AC, won't power up at all
- checked AC adapter with multimeter and it was outputting the correct voltage (also it keeps the battery charged still)
- removed the keyboard and speaker cover then reseated the 7-button circuit
- cleaned the ribbon cable contacts and reseated the ribbon cable for the circuit
- removed RAM and tried each stick by itself, no change.
I'm kind of lost here. Again, I am probably at a point where I need to replace hardware but I don't want to drop the cash without some kind of verification that I'm not retarded.
Any assistance or advice is welcome. Thank you.

Ah, I've been playing around with this and it seems I was mistaken about the nature of the problem.
It is deterministic, for one. It seemed nondeterministic because the action that makes the glasspane paint() fail is the act of giving focus to the JInternalFrame that the glasspane belongs to.
Why does giving focus to a JInternalFrame disable that frame's GlassPane? I can take focus away from it, and the repaint() method starts working again.

CP3 Buttons fail to pause?

I have a captivate 3 project where I have 5 buttons on the time line. All five start at the beginning of the slide, all pause at the same time, all end at the same time. (slide is 2 sec long, buttons pause at 1 sec) If you click on a button all jump to a different slide in the same project. I have about 20 slides set up like this. Problem: random people in my organization have told me that when they get to some of these slides, the project does not pause and just goes to the next slide.
I did a project last year and had no issues like this. I am publishing to use Flash player 9. It seems that people who are using Flash player 9 have more problems that people using Flash player 10. I have replaced every button in the project... I still have failures.
In the past I have had major issues when I have cut and pasted buttons and have stop using that practice.
The project fails when running in our LMS (Pathlore 6.6) but also if I run it outside of the LMS. I as the developer can not get it to fail.
Anyone have any insites?
Thank you.

I hope this may help others.
I still do not know what caused by buttons to fail.
After testing people using Flash player 9 had buttons fail. If they updated to Flash player 10 no failures.
What I did was open a new project and import the one one into the new one and now it works with both Player 9 and 10.
Go figure.

Touchpad button problem

Hi all,
A few weeks ago my MacBook (original Core Duo model) started detecting clicks on the touchpad button as double-clicks in the OS. This doesn't happen all the time, and seems much more likely to occur when I press on the left side of the button than the right, so I'm assuming it's a hardware issue.
Does anyone have a rough idea of how much it'd cost to get repaired at a UK Apple store? It's been out of warranty for a while unfortunately.
Thanks
J

I have two MB's one has a crisp trackpad button while the other had a mushy button. I fixed the mushy button quite easily. Take out the battery and look at the metal panel directly underneath the trackpad button. You'll see a circular indention in the metal. If you press lightly on the indention and at the same time press on the trackpad button you'll notice that the trackpad button's response is more crisp (at least mine was). I just pressed on the spot a few times to force the metal to bow every so slightly (not perceptible to the eye). Now my button clicks quite nicely across the entire button.

[SOLVED] Slow/sluggish touchpad buttons response (sometimes)

Hi all,
I have had this problem for some months now but have never looked into it, even if it is pretty annoying.
Sometimes (say one boot every three) the touchpad buttons of my laptop (see sig) behave strangely. Their response time is very long, I have to keep them pressed for ~half a second to make them trigger correctly.
This is very annoying when editing texts (selection a section of text with the touchpad) and using any click intensive application (ie editing a presentation with Prezi).
I use KDE and the only touchpad configuration I've ever done has been done via synaptiks.
I cannot tell after what update this started, it was too long ago unfortunately.
Since this happens only sometimes I don't even know where to start looking!
EDIT: I stress the fact that this happens with buttons, not with tapping
Last edited by OdinEidolon (2014-06-29 09:19:30)

Just FYI,
this one solved itself some months ago after some kind of update.

Lower volume button control not working help?

Lower volume button control not working help?

If you only restored from backup, restore to factory defaults/new iPod. If you then still have the problem it is likely a hardware problem and an appointment at the Genius Bar of an Apple store is in order.

The lower volume button just quit on my Iphone 5

My lower volume button is not working on iphone 5.

Yes, if the screen is not cracked, this will be handled by Warranty. Cracked screen is Out of Warranty repair, and for iPhone 5 this will cost $229. For either, make Genius reservation or set up Service and take or send to Apple for resolution.

Has anyone experienced the on/off touch button and the brightness touch buttons failing on a 30" cinema screen?

I have a 30" cinema display which is about 3 years old. Everything was working fine yesterday but on reboot today the screen went dim and the brightness buttons did not work. I used the key board and increased the brightness but it went dim again on release. The on/off touch button also did not work.
I have set to disable both of these in the preferences and all is working now but I wondered if anyone else has experience of both of these touch buttons failing. The monitor has been switched off when booting up on a morning but I had not switched it off manually before shut down or set it to do so which I thought was odd. Now I wonder if it was the first signs of a breakdown of the switches on the monitor.
Thanks for any imput in advance.
sas44

Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try another cable
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar

Buy button fails

When converting from trial version to full teh BUY button fails and reports "Aperture already installed". Must I uninstall and loose the trial library?

Just remove Aperture the application from your Applications folder. Leave the library alone. You will be able to use the library made during the trial period with the purchased app.

Lower touchpad button failing

Similar Messages

Maybe you are looking for