Pinch zoom on Synaptics touchpad?

I have a Synaptics touchpad that supports nearly everything, according to this, and I would like to configure it to get pinch zoom working. In Windows pinch zooming works, so it's not a hardware issue. How would I go about doing this? Ideally, I would like it to emulate Ctrl+scrolling, so it could work on Chromium and Gimp.

WonderWoofy wrote:I have never heard of this "touchegg" before, so I am unsure of what it does. But this is probably what you are looking for https://aur.archlinux.org/packages.php?ID=41592 . There is also xf86-input-multitouch-git as well as xf86-input-mtrack-git. Do a search in the AUR for xf86-input
Those are the X (low-level) touchpad drivers, but an application (window manager or standalone) is also needed to translate gestures to actions/commands.
- Touchegg is a QT program
- Easystroke is a GTK-program
Both pull in huge amounts of dependencies (100-200MB) to do something quite simple, so they are generally not what you want when using DWM.
The most simple solution i have come across is this Perl approach:
http://www.ibm.com/developerworks/opens … index.html
Which is more or less a proof-of-concept, it uses a high-res timer module from CPAN for accuracy. I haven't tried it myself so i don't know how well it works, but it probably requires more work since it doesn't have a spiffy UI with settings but is a hardcoded script.
Ideally you'd want a really simple/small utility that lets you map context-aware gestures to commands. For instance:
[Window: Chromium] 2-finger swipe-left == Mod1-arrowleft
[Window: generic] 3-finger swipe-up == exec dmenu_run
Last edited by litemotiv (2012-10-03 09:03:39)

Similar Messages

Synaptics touchpad doesn't save scroll settings after Windows 10 upgrade

Since the Windows 10 upgrade (upgraded from 7), the Synaptics Touchpad does not save scroll settings. Every time I shut down and restart the machine the next day, I have to go into settings to re-enable touchpad scrolling. It's always unchecked on restart. Please advise on how to fix this!

My solution, copied from one of many threads regarding this problem - You have Synaptics Port Touchpad driver installed via Windows Update. Here's is a work around until a fully Win10 compatible driver is issued. Win+X/ Device Manager/ Mice and other pointing devices/ Synaptics PS/2 Port TouchPad. R click/ Update Driver Software/ Browse my computer for driver software / Let me pick from a list of device drivers on my computer. Select the top or latest version of Synaptics PS/2 Port Compatible Touchpad Version 19.0.12.95 (7/15/2015) / Next and driver will install automatically. Reboot to finish install. Go to Settings/ Mouse Properties/ Synaptics Device Settings to access Touchpad settings, adjust to your liking/ Apply/ OK. Advise to tick 'Static tray icon in taskbar' for easy access to the settings tab until you're completely happy. This 19.0.12.95 is the latest one on the HP site for my model (your # may vary) and it installs 2 versions. The one Windows Update uses is the same date Port Touchpad version but the 'Compatible' one is installed at the same time. You can tell the difference immediately because it allows you to create a profile. The old 8.1 version did not and neither does the 'Compatible' one. The touchpad setting screens look the same as before (you'll notice the new one looks different and 3 finger press opens Cortana). Why do I consider this a workaround ? Because the 3-finger press app setting, one finger EdgeMotion and demo vids do not work. But at least you can set the scrolling, pinch zoom, speed and sensitivity to your liking and if you reboot, you'll see the system tray icon and your preferences have stuck. Hope this helps somebody !

HP G62-347NR Multitouch pinch zoom

I just bought my G62 laptop, but I can't seem to use the zoom in/out function on the touch pad. I opened up Synaptics settings and it says that PInch Zoom is enabled (it is checked) but I can't zoom in/out in my web browser when I pinch the touchpad. Please help!

Right Click on Synaptic icon in system tray...It will give you below option, Uncheck 'Disable Gesture' and check....
Although I am an HP employee, I am speaking for myself and not for HP.
Make it easier for other people to find solutions, by marking my answer with 'Accept as Solution', if it solves your problem.
Click on the BLUE KUDOS button on the left to say "Thanks"

How to switch off scroll and zoom functions of touchpad on Satellite L

Hi.
Can anyone tell me how to switch off the scroll and zoom functions for the Synaptics Touchpad v7.2 .
Can't seem to do it via the Control Panel.
Any suggestions.

Hi buddy,
> Can't seem to do it via the Control Panel.
You can only disable the virtual scrolling function if the touchpad driver is installed properly. The driver provides extended functions and allows you to disable/enable special features. If you dont have installed the touchpad driver download it on official Toshiba page:
http://eu.computers.toshiba-europe.com > Support & Downloads > Download Drivers
Then navigate to control panel as the previous user wrote for disabling the scroll function.
Can you find it now?

Synaptics touchpad 64-bit enhancements has stopped working.

Hi guys,
I recently bought new HP 15-r022tx Notebook PC (Product Number: J6M27PA) which comes with free dos, have installed windows 7 x64 and updated all drivers from hp online, after all latest update i get a error message on startup 'synaptics touchpad 64-bit enhancements has stopped working'.
have tried to configure mouse setting but wen i try to access mouse setting i get a error message 'unable to connect to synaptics pointing device driver'
have uninstalled and re installed the driver from hp support still the same problem.
so after some online search and no luck in any of them i continued using lap by closing the program on the first error message on every startup without any synaptics touchpad functions like two touch scrolling, zooming etc... but some times the cursor jumps around erratically and moves on its own with no contact in the touchpad, click options are not working wen cursor strats to move on its own, after some observation i noticed mouse works fine on every startup(by closing the program on error message without touchpads some special functions) until i right click it (sometimes after first click some times after many clicks) until i right click using the touchpad the mouse seems to be working fine but after i right click the mouse it goes to its own way.
any suggestions guys
thanks you guys.....
This question was solved.
View Solution.

Hello Zman07,
Welcome to the HP Forums, I hope you enjoy your experience!
I have read your post on how the TouchPad on your notebook computer is behaving erratically, and I would be happy to assist you!
To restore the functions on your TouchPad, I recommend uninstalling the driver from Programs and Features and installing this specific Synaptics TouchPad Driver. This parcel of software should be compatible with your current system.
If the issue persists, I also suggest following this document on Using and Configuring the TouchPad (Windows 7 and Vista). This should help adjust the TouchPad to your preferences.
Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Faulty Synaptics Touchpad Driver on Split x2 13-m121sa Causing Freezing and Mouse Unresponsiveness

Edit: I found a solution, scroll further down. I have been having problems with my new Split x2 similar to those already explained in the forums by other users. The symptoms are as follows:
1. Unusual hanging or freezing of the mouse pointer on the screen and temperamental use of gestures (two finger scrolling, zooming, etc.)
2. Slowing down of computer generally; acting sluggish and freezing during only light use and/or after screen being closed.
The symptoms seems to change depending on the length of time the computer has been switched on, and are affected by disconnecting/reconnecting the screen from the dock.
Being quite good with these things I decided to investigate and have uncovered the following:
The root cause of both of these problems is the Synaptics Touchpad driver. While the newest version (17.0.10.9) available from the HP website seems to solve any unusual freezing of the pointer it has a significant memory leak. In other words, as you move the pointer around the touchpad uses up the computer's memory. This is normal, but the problem is that the driver for the touchpad does not give the memory back; it cannot be reallocated. This means after a couple of hours of using the computer (or having the screen closed) the memory reaches saturation point and the computer grinds to a halt. If you are having the same problem have a look for yourself: Open task manager and look at the performance tab. Under the Memory heading you will see a value for 'Non-paged pool'. With the computer idle this number shouldn't increase, but move the mouse around and you will see it gradually go up without returning. I have confirmed this to be the Synaptics driver by using the Windows tool poolmon.exe - the culprits are Irp and SynT. Regarding solutions, I have tried many - but there is no absolute fix.
You can uninstall the Synaptics Touchpad driver and the problem will go away - no more freezing or high memory usage. But without the driver the computer reverts to using the standard Windows driver - therefore there is no multitouch gestures like scrolling or zooming.
I have tried installing the generic Synaptics driver available from their website, and the computer won't allow it. Regardless of this, I forced the driver install but the generic driver does not work with this Touchpad anyway (Error code 10). I have tried the latest version (17.0.19) and an older one (16.2.21) with no success. Even earlier versions (e.g. 15.x.x) refuse to run on the grounds of incompatibility. HP Support suggest a system 'refresh' back to factory setting, but apart from the huge inconvenience of time and losing files - I know this won't work either. Apparently a clean install has worked for one user - but for this you need a Windows install disc or USB which I do not have - and I'm sceptical that it would work anyway.
So now I'm using the standard Windows touchpad driver without being able to scroll, zoom or use the swipe-in gestures of Windows 8.1.
If a HP representative is reading this, I would strongly suggest that this problem be escalated. A simple update from Synaptics could solve this problem which is causing people's computers to freeze up and wasting your support staff's time.
TL;DR: HP's Touchpad driver is faulty and causes a memory leak. Synaptics own generic drivers do not work. And Windows standard drivers are unsatisfactory.

SOLVED!
Through my own research I have found a solution. While the official newest driver listed under this model is 17.0.10.9 there is in fact a newer version which does not have this problem: version 17.0.10.16!
I am still disappointed that HP didn't suggest this solution themselves, considering this driver was published back in November 2013! HP if you're reading this: please allocate this driver to this model in your support pages. Anyway, the solution is as follows:
1. Open the Device Manager (Control Panel -> Hardware and Sound -> Device Manager)2. Under 'Mice and other pointing devices' open 'Synaptics HID TouchPad'3. In the 'Driver' tab click on 'Uninstall'4. The pointer will disappear - reboot the computer5. Download the new driver from here: http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?cc=uk&lc=en&softwareitem=ob-127354-1(if this link goes down try searching online for 'synaptics driver 17.0.10.16')6. Open and install the driver I hope this helps. HP, please send my consulation fee via PayPal(!)

ConfigMgr 2012 R2 Client Failes to Install on HP EliteBook laptops with Synaptics Touchpad drivers

I've come across a fairly frustrating issue that has been taking up way too much of my time that past week or so. The issue started a little after some of our larger sites were migrated from SCCM 2007 to SCCM 2012. I started getting complaints that one of
our technical workstations (HP 8770w) was not deploying properly. I started investigating the issue and the problem involved the removal of the old ConfigMgr 2007 client and install of the new SCCM 2012 R2 client.
The Windows 7 x64 OS WIM that I am using is one that was migrated from the 07 to 2012 environment and it has been working fine. During the Setup Windows and ConfigMgr step the old client is removed and the new one for the 2012 environment installs. There
has not been any issues with this, but I feel something has changed now that we are deploying the 2012 R2 client.
Back to the issue, what happens is that the ConfigMgr client fails to uninstall the old client. Looking in the client.msi_uninstall file you will see that it is unable to locate a couple of SCCM 2007 configmgr client patches that were installed so it can
uninstall it. I get the "Couldn't find local patch ''. Looking for it at its source." line in the uninstall file. When I look for that under HKEY_CLASSES_ROOT\Installer\Patches the ENTIRE directory structure is empty. There is not a single item
listed under patches.
Since the only thing that happens in between the pushing down of the WIM and installing the configmgr client is the drivers that is where I started to look. I started over with the basics (disk and network driver) and it was able to complete the OSD process
(like the other 30+ models we currently support). I added drivers one by one having the system re-image each time. When I got to the Synaptics TouchPad drivers the issue would return. I've tried around 5 different drivers offered from the vendor and they
all result in the same behavior.
I'm still actively troubleshooting how to FIX this issue, but I have no idea why this is going on. I thought I would share with the community on this issue and see if anyone else has observed this VERY odd behavior.
Here is a snippet from the client.msi_uninstall log:
=== Verbose logging started: 1/15/2014 22:59:34 Build type: SHIP UNICODE 5.00.7601.00 Calling process: D:\_SMSTaskSequence\OSD\GAS000EF\ccmsetup.exe ===
MSI (c) (6C:BC) [22:59:34:264]: Resetting cached policy values
MSI (c) (6C:BC) [22:59:34:264]: Machine policy value 'Debug' is 0
MSI (c) (6C:BC) [22:59:34:264]: ******* RunEngine:
           ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (6C:BC) [22:59:34:264]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (6C:BC) [22:59:34:264]: Grabbed execution mutex.
MSI (c) (6C:BC) [22:59:34:264]: Cloaking enabled.
MSI (c) (6C:BC) [22:59:34:264]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (6C:BC) [22:59:34:264]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:80) [22:59:34:264]: Running installation inside multi-package transaction {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
MSI (s) (00:80) [22:59:34:264]: Grabbed execution mutex.
MSI (s) (00:D4) [22:59:34:264]: Resetting cached policy values
MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'Debug' is 0
MSI (s) (00:D4) [22:59:34:264]: ******* RunEngine:
           ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (00:D4) [22:59:34:405]: SRSetRestorePoint skipped for this transaction.
MSI (s) (00:D4) [22:59:34:405]: End dialog not enabled
MSI (s) (00:D4) [22:59:34:405]: Original package ==> C:\Windows\Installer\b8ba.msi
MSI (s) (00:D4) [22:59:34:405]: Package we're running from ==> C:\Windows\Installer\b8ba.msi
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: looking for appcompat database entry with ProductCode '{2609EDF1-34C4-4B03-B634-55F3B3BC4931}'.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (00:D4) [22:59:34:420]: MSCOREE not loaded loading copy from system32
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (00:D4) [22:59:34:420]: User policy value 'DisableMedia' is 0
MSI (s) (00:D4) [22:59:34:420]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {D478B8EE-EE0A-4004-980B-4D55533EE3C2} 3:
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {D478B8EE-EE0A-4004-980B-4D55533EE3C2} -- orphaning this patch
MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} 3:
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} -- orphaning this patch
MSI (s) (00:D4) [22:59:34:420]: SequencePatches starts. Product code: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}, Product version: 4.00.6487.2000, Upgrade code: {252DA259-82CA-4177-B8D0-49C78937BA3E}, Product language 1033
MSI (s) (00:D4) [22:59:34:420]: SequencePatches returns success.
MSI (s) (00:D4) [22:59:34:420]: Final Patch Application Order:
MSI (s) (00:D4) [22:59:34:420]: Other Patches:
MSI (s) (00:D4) [22:59:34:420]: Internal Exception during install operation: 0xc0000005 at 0x000007FEFDBF35E1.
MSI (s) (00:D4) [22:59:34:420]: WER report disabled for silent install.
MSI (s) (00:D4) [22:59:34:420]: Internal MSI error. Installer terminated prematurely.
MSI (s) (00:D4) [22:59:34:420]: MainEngineThread is returning 1603
MSI (s) (00:80) [22:59:34:420]: No System Restore sequence number for this installation.
Unexpected Termination
MSI (s) (00:80) [22:59:34:420]: User policy value 'DisableRollback' is 0
MSI (s) (00:80) [22:59:34:420]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:80) [22:59:34:420]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (00:80) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (00:80) [22:59:34:420]: Restoring environment variables
MSI (c) (6C:BC) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (6C:BC) [22:59:34:420]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/15/2014 22:59:34 ===

@Narcoticoo
I've not used the tool. This issue has also expanded since the original title as I'm getting the same behavior with the driver package that does not include the Touchpad driver anymore. I'm currently going back to just the network and storage driver to see
if it works or not.
However, this is the bigger issue I have:
I have an older build called Build 5.7 internally. Using that WIM and the same driver package (original one that has the Touchpad driver included) it works without issue. Never had a problem.
The new build is called Build 6.0 internally. This WIM and the same driver package has not been working at all.
We support about 35 models with our current Windows 7 x64 image and I am having the same failure issue on four different HP models. They are the 8770w, ZBook 17, Z600 and Z820. The majority of the other systems are Dell devices. Just for transparency sakes,
nothing Dell specific is in the core WIM that is captured.
So, Build 5.7 can deploy just fine on all pieces of hardware with their old driver packages. The new Build 6.0 intalls on almost every platform fine with their old driver packages. These four HP systems are nothing but trouble though. I've opened a case
with HP to see if they have noticed anything internally. I'm not too hopeful, but at least it is something. Maybe there is some odd conflict with a newer Windows patch or some odd dependency on older HP drivers. The new image has .NET 4.5.1, IE 10 and so forth.

[Solved]Synaptics Touchpad not working at all on Fujitsu Siemens UH552

Hi,
I have just installed Arch on my Fujitsu Siemens UH552 laptop. Everything works except for the touchpad which seems to get loaded by Xorg, but when in X it doesn't work. I have tried both using /dev/input/event* and /dev/input/mouse0 as device paths, neither works.
xf86-input-evdev and xf86-input-synaptics are installed.
I have tried running both with the default 10-evdev.conf, with 10-synaptics.conf, with both, and without both.
TLDR SOLUTION: https://bbs.archlinux.org/viewtopic.php … 3#p1189603
My current 10-synaptics.conf:
Section "InputClass"
Identifier "Touchpad Catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "synaptics"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
EndSection
Xorg.0.log
[ 2275.127]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 2275.130] X Protocol Version 11, Revision 0
[ 2275.131] Build Operating System: Linux 3.4.8-1-ARCH x86_64
[ 2275.132] Current Operating System: Linux corvo 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64
[ 2275.132] Kernel command line: root=/dev/sda2 rootflags=subvol=__active ro initrd=/boot/initramfs-linux.img BOOT_IMAGE=/boot/vmlinuz-linux
[ 2275.134] Build Date: 27 August 2012 08:04:39AM
[ 2275.135]
[ 2275.136] Current version of pixman: 0.26.2
[ 2275.138] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2275.138] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2275.142] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 1 13:16:01 2012
[ 2275.143] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2275.144] (==) No Layout section. Using the first Screen section.
[ 2275.144] (==) No screen section available. Using defaults.
[ 2275.144] (**) |-->Screen "Default Screen Section" (0)
[ 2275.144] (**) | |-->Monitor "<default monitor>"
[ 2275.144] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 2275.144] (**) | |-->Device "Intel Graphics"
[ 2275.144] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2275.144] (==) Automatically adding devices
[ 2275.144] (==) Automatically enabling devices
[ 2275.144] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2275.144] Entry deleted from font path.
[ 2275.144] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2275.144] Entry deleted from font path.
[ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2275.144] Entry deleted from font path.
[ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2275.144] Entry deleted from font path.
[ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2275.144] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 2275.144] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2275.144] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2275.144] (II) Loader magic: 0x7c8b00
[ 2275.144] (II) Module ABI versions:
[ 2275.144] X.Org ANSI C Emulation: 0.4
[ 2275.144] X.Org Video Driver: 12.1
[ 2275.144] X.Org XInput driver : 16.0
[ 2275.144] X.Org Server Extension : 6.0
[ 2275.144] (--) PCI:*(0:0:2:0) 8086:0166:10cf:16c2 rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00002000/64
[ 2275.144] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2275.144] (II) LoadModule: "extmod"
[ 2275.144] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2275.145] (II) Module extmod: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] Module class: X.Org Server Extension
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension MIT-SCREEN-SAVER
[ 2275.145] (II) Loading extension XFree86-VidModeExtension
[ 2275.145] (II) Loading extension XFree86-DGA
[ 2275.145] (II) Loading extension DPMS
[ 2275.145] (II) Loading extension XVideo
[ 2275.145] (II) Loading extension XVideo-MotionCompensation
[ 2275.145] (II) Loading extension X-Resource
[ 2275.145] (II) LoadModule: "dbe"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2275.145] (II) Module dbe: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] Module class: X.Org Server Extension
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension DOUBLE-BUFFER
[ 2275.145] (II) LoadModule: "glx"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2275.145] (II) Module glx: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (==) AIGLX enabled
[ 2275.145] (II) Loading extension GLX
[ 2275.145] (II) LoadModule: "record"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2275.145] (II) Module record: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.13.0
[ 2275.145] Module class: X.Org Server Extension
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension RECORD
[ 2275.145] (II) LoadModule: "dri"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 2275.145] (II) Module dri: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension XFree86-DRI
[ 2275.145] (II) LoadModule: "dri2"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2275.145] (II) Module dri2: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.2.0
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension DRI2
[ 2275.145] (II) LoadModule: "intel"
[ 2275.146] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 2275.146] (II) Module intel: vendor="X.Org Foundation"
[ 2275.146] compiled for 1.12.3.901, module version = 2.20.5
[ 2275.146] Module class: X.Org Video Driver
[ 2275.146] ABI class: X.Org Video Driver, version 12.1
[ 2275.146] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+)
[ 2275.146] (--) using VT number 7
[ 2275.149] drmOpenDevice: node name is /dev/dri/card0
[ 2275.149] drmOpenDevice: open result is 7, (OK)
[ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 2275.150] drmOpenDevice: node name is /dev/dri/card0
[ 2275.150] drmOpenDevice: open result is 7, (OK)
[ 2275.150] drmOpenByBusid: drmOpenMinor returns 7
[ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 2275.150] drmOpenDevice: node name is /dev/dri/card0
[ 2275.150] drmOpenDevice: open result is 8, (OK)
[ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 2275.150] drmOpenDevice: node name is /dev/dri/card0
[ 2275.150] drmOpenDevice: open result is 8, (OK)
[ 2275.150] drmOpenByBusid: drmOpenMinor returns 8
[ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 2275.150] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 2275.150] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 2275.150] (==) intel(0): RGB weight 888
[ 2275.150] (==) intel(0): Default visual is TrueColor
[ 2275.150] (**) intel(0): Option "AccelMethod" "sna"
[ 2275.150] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
[ 2275.151] (**) intel(0): Framebuffer tiled
[ 2275.151] (**) intel(0): Pixmaps tiled
[ 2275.151] (**) intel(0): 3D buffers tiled
[ 2275.151] (**) intel(0): Throttling enabled
[ 2275.151] (**) intel(0): Delayed flush enabled
[ 2275.151] (**) intel(0): "Tear free" disabled
[ 2275.151] (**) intel(0): Forcing per-crtc-pixmaps? no
[ 2275.151] (II) intel(0): Output LVDS1 has no monitor section
[ 2275.152] (II) intel(0): found backlight control interface acpi_video0 (type 'firmware')
[ 2275.152] (II) intel(0): Output VGA1 has no monitor section
[ 2275.153] (II) intel(0): Output HDMI1 has no monitor section
[ 2275.193] (II) intel(0): Output DP1 has no monitor section
[ 2275.193] (II) intel(0): EDID for output LVDS1
[ 2275.193] (II) intel(0): Manufacturer: LGD Model: 371 Serial#: 0
[ 2275.193] (II) intel(0): Year: 2012 Week: 0
[ 2275.193] (II) intel(0): EDID Version: 1.3
[ 2275.193] (II) intel(0): Digital Display Input
[ 2275.193] (II) intel(0): Max Image Size [cm]: horiz.: 29 vert.: 16
[ 2275.193] (II) intel(0): Gamma: 2.20
[ 2275.193] (II) intel(0): No DPMS capabilities specified
[ 2275.193] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 2275.193] (II) intel(0): First detailed timing is preferred mode
[ 2275.193] (II) intel(0): redX: 0.589 redY: 0.347 greenX: 0.343 greenY: 0.555
[ 2275.193] (II) intel(0): blueX: 0.160 blueY: 0.124 whiteX: 0.313 whiteY: 0.329
[ 2275.193] (II) intel(0): Manufacturer's mask: 0
[ 2275.193] (II) intel(0): Supported detailed timing:
[ 2275.193] (II) intel(0): clock: 70.0 MHz Image Size: 293 x 165 mm
[ 2275.193] (II) intel(0): h_active: 1366 h_sync: 1402 h_sync_end 1438 h_blank_end 1476 h_border: 0
[ 2275.193] (II) intel(0): v_active: 768 v_sync: 772 v_sync_end 780 v_blanking: 790 v_border: 0
[ 2275.193] (II) intel(0): LG Display
[ 2275.193] (II) intel(0): LP133WH2-TLF1
[ 2275.193] (II) intel(0): EDID (in hex):
[ 2275.193] (II) intel(0): 00ffffffffffff0030e4710300000000
[ 2275.193] (II) intel(0): 00160103801d10780afc359658578e29
[ 2275.193] (II) intel(0): 1f505400000001010101010101010101
[ 2275.193] (II) intel(0): 010101010101581b566e500016302424
[ 2275.194] (II) intel(0): 480025a5100000190000000000000000
[ 2275.194] (II) intel(0): 00000000000000000000000000fe004c
[ 2275.194] (II) intel(0): 4720446973706c61790a2020000000fe
[ 2275.194] (II) intel(0): 004c503133335748322d544c463100ce
[ 2275.194] (II) intel(0): EDID vendor "LGD", prod id 881
[ 2275.194] (II) intel(0): Printing DDC gathered Modelines:
[ 2275.194] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
[ 2275.194] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Printing probed modes for output LVDS1
[ 2275.194] (II) intel(0): Modeline "1366x768"x60.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
[ 2275.194] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 2275.194] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 2275.194] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 2275.194] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 2275.194] (II) intel(0): EDID for output VGA1
[ 2275.195] (II) intel(0): EDID for output HDMI1
[ 2275.236] (II) intel(0): EDID for output DP1
[ 2275.236] (II) intel(0): Output LVDS1 connected
[ 2275.236] (II) intel(0): Output VGA1 disconnected
[ 2275.236] (II) intel(0): Output HDMI1 disconnected
[ 2275.236] (II) intel(0): Output DP1 disconnected
[ 2275.236] (II) intel(0): Using exact sizes for initial modes
[ 2275.236] (II) intel(0): Output LVDS1 using initial mode 1366x768
[ 2275.236] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 2275.236] (**) intel(0): Display dimensions: (290, 160) mm
[ 2275.236] (**) intel(0): DPI set to (119, 121)
[ 2275.236] (II) Loading sub module "dri2"
[ 2275.236] (II) LoadModule: "dri2"
[ 2275.237] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2275.237] (II) Module dri2: vendor="X.Org Foundation"
[ 2275.237] compiled for 1.12.4, module version = 1.2.0
[ 2275.237] ABI class: X.Org Server Extension, version 6.0
[ 2275.237] (==) Depth 24 pixmap format is 32 bpp
[ 2275.237] (II) intel(0): SNA initialized with IvyBridge backend
[ 2275.237] (==) intel(0): Backing store disabled
[ 2275.237] (==) intel(0): Silken mouse enabled
[ 2275.237] (II) intel(0): HW Cursor enabled
[ 2275.237] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 2275.238] (==) intel(0): DPMS enabled
[ 2275.239] (II) intel(0): [DRI2] Setup complete
[ 2275.239] (II) intel(0): [DRI2] DRI driver: i965
[ 2275.239] (II) intel(0): direct rendering: DRI2 Enabled
[ 2275.239] (==) intel(0): hotplug detection: "enabled"
[ 2275.239] (--) RandR disabled
[ 2275.239] (II) Initializing built-in extension Generic Event Extension
[ 2275.239] (II) Initializing built-in extension SHAPE
[ 2275.239] (II) Initializing built-in extension MIT-SHM
[ 2275.239] (II) Initializing built-in extension XInputExtension
[ 2275.239] (II) Initializing built-in extension XTEST
[ 2275.239] (II) Initializing built-in extension BIG-REQUESTS
[ 2275.239] (II) Initializing built-in extension SYNC
[ 2275.239] (II) Initializing built-in extension XKEYBOARD
[ 2275.239] (II) Initializing built-in extension XC-MISC
[ 2275.239] (II) Initializing built-in extension SECURITY
[ 2275.239] (II) Initializing built-in extension XINERAMA
[ 2275.239] (II) Initializing built-in extension XFIXES
[ 2275.239] (II) Initializing built-in extension RENDER
[ 2275.239] (II) Initializing built-in extension RANDR
[ 2275.239] (II) Initializing built-in extension COMPOSITE
[ 2275.239] (II) Initializing built-in extension DAMAGE
[ 2275.250] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 2275.250] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 2275.250] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 2275.250] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 2275.250] (II) AIGLX: Loaded and initialized i965
[ 2275.250] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 2275.251] (II) intel(0): switch to mode 1366x768 on crtc 3 (pipe 0)
[ 2275.276] (II) intel(0): Setting screen physical size to 361 x 203
[ 2275.319] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[ 2275.319] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2275.319] (II) LoadModule: "evdev"
[ 2275.319] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2275.320] (II) Module evdev: vendor="X.Org Foundation"
[ 2275.320] compiled for 1.12.3.901, module version = 2.7.3
[ 2275.320] Module class: X.Org XInput Driver
[ 2275.320] ABI class: X.Org XInput driver, version 16.0
[ 2275.320] (II) Using input driver 'evdev' for 'Power Button'
[ 2275.320] (**) Power Button: always reports core events
[ 2275.320] (**) evdev: Power Button: Device: "/dev/input/event6"
[ 2275.320] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2275.320] (--) evdev: Power Button: Found keys
[ 2275.320] (II) evdev: Power Button: Configuring as keyboard
[ 2275.320] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6"
[ 2275.320] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 2275.320] (**) Option "xkb_rules" "evdev"
[ 2275.320] (**) Option "xkb_model" "evdev"
[ 2275.320] (**) Option "xkb_layout" "se"
[ 2275.355] (II) config/udev: Adding input device Fujitsu FUJ02E3 (/dev/input/event3)
[ 2275.356] (**) Fujitsu FUJ02E3: Applying InputClass "evdev keyboard catchall"
[ 2275.356] (II) Using input driver 'evdev' for 'Fujitsu FUJ02E3'
[ 2275.356] (**) Fujitsu FUJ02E3: always reports core events
[ 2275.356] (**) evdev: Fujitsu FUJ02E3: Device: "/dev/input/event3"
[ 2275.356] (--) evdev: Fujitsu FUJ02E3: Vendor 0 Product 0x6
[ 2275.356] (--) evdev: Fujitsu FUJ02E3: Found keys
[ 2275.356] (II) evdev: Fujitsu FUJ02E3: Configuring as keyboard
[ 2275.356] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/FUJ02E3:00/input/input3/event3"
[ 2275.356] (II) XINPUT: Adding extended input device "Fujitsu FUJ02E3" (type: KEYBOARD, id 7)
[ 2275.356] (**) Option "xkb_rules" "evdev"
[ 2275.356] (**) Option "xkb_model" "evdev"
[ 2275.356] (**) Option "xkb_layout" "se"
[ 2275.357] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 2275.357] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 2275.357] (II) Using input driver 'evdev' for 'Video Bus'
[ 2275.357] (**) Video Bus: always reports core events
[ 2275.357] (**) evdev: Video Bus: Device: "/dev/input/event9"
[ 2275.357] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 2275.357] (--) evdev: Video Bus: Found keys
[ 2275.357] (II) evdev: Video Bus: Configuring as keyboard
[ 2275.357] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input9/event9"
[ 2275.357] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 2275.358] (**) Option "xkb_rules" "evdev"
[ 2275.358] (**) Option "xkb_model" "evdev"
[ 2275.358] (**) Option "xkb_layout" "se"
[ 2275.359] (II) config/udev: Adding input device Fujitsu FUJ02B1 (/dev/input/event2)
[ 2275.359] (**) Fujitsu FUJ02B1: Applying InputClass "evdev keyboard catchall"
[ 2275.359] (II) Using input driver 'evdev' for 'Fujitsu FUJ02B1'
[ 2275.359] (**) Fujitsu FUJ02B1: always reports core events
[ 2275.359] (**) evdev: Fujitsu FUJ02B1: Device: "/dev/input/event2"
[ 2275.359] (--) evdev: Fujitsu FUJ02B1: Vendor 0 Product 0x6
[ 2275.359] (--) evdev: Fujitsu FUJ02B1: Found keys
[ 2275.359] (II) evdev: Fujitsu FUJ02B1: Configuring as keyboard
[ 2275.359] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/FUJ02B1:00/input/input2/event2"
[ 2275.359] (II) XINPUT: Adding extended input device "Fujitsu FUJ02B1" (type: KEYBOARD, id 9)
[ 2275.359] (**) Option "xkb_rules" "evdev"
[ 2275.359] (**) Option "xkb_model" "evdev"
[ 2275.359] (**) Option "xkb_layout" "se"
[ 2275.360] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 2275.360] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2275.360] (II) Using input driver 'evdev' for 'Power Button'
[ 2275.360] (**) Power Button: always reports core events
[ 2275.360] (**) evdev: Power Button: Device: "/dev/input/event5"
[ 2275.360] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2275.360] (--) evdev: Power Button: Found keys
[ 2275.360] (II) evdev: Power Button: Configuring as keyboard
[ 2275.361] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5/event5"
[ 2275.361] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 10)
[ 2275.361] (**) Option "xkb_rules" "evdev"
[ 2275.361] (**) Option "xkb_model" "evdev"
[ 2275.361] (**) Option "xkb_layout" "se"
[ 2275.362] (II) config/udev: Adding input device Lid Switch (/dev/input/event4)
[ 2275.362] (II) No input driver specified, ignoring this device.
[ 2275.362] (II) This device may have been added with another device file.
[ 2275.362] (II) config/udev: Adding input device FJ Camera (/dev/input/event7)
[ 2275.362] (**) FJ Camera: Applying InputClass "evdev keyboard catchall"
[ 2275.362] (II) Using input driver 'evdev' for 'FJ Camera'
[ 2275.362] (**) FJ Camera: always reports core events
[ 2275.362] (**) evdev: FJ Camera: Device: "/dev/input/event7"
[ 2275.363] (--) evdev: FJ Camera: Vendor 0x10f1 Product 0x1a44
[ 2275.363] (--) evdev: FJ Camera: Found keys
[ 2275.363] (II) evdev: FJ Camera: Configuring as keyboard
[ 2275.363] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input7/event7"
[ 2275.363] (II) XINPUT: Adding extended input device "FJ Camera" (type: KEYBOARD, id 11)
[ 2275.363] (**) Option "xkb_rules" "evdev"
[ 2275.363] (**) Option "xkb_model" "evdev"
[ 2275.363] (**) Option "xkb_layout" "se"
[ 2275.364] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
[ 2275.364] (II) No input driver specified, ignoring this device.
[ 2275.364] (II) This device may have been added with another device file.
[ 2275.364] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11)
[ 2275.364] (II) No input driver specified, ignoring this device.
[ 2275.364] (II) This device may have been added with another device file.
[ 2275.365] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
[ 2275.365] (II) No input driver specified, ignoring this device.
[ 2275.365] (II) This device may have been added with another device file.
[ 2275.365] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 2275.365] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 2275.365] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 2275.366] (**) AT Translated Set 2 keyboard: always reports core events
[ 2275.366] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 2275.366] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 2275.366] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 2275.366] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[ 2275.366] (**) Option "xkb_rules" "evdev"
[ 2275.366] (**) Option "xkb_model" "evdev"
[ 2275.366] (**) Option "xkb_layout" "se"
[ 2275.366] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8)
[ 2275.366] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Touchpad Catchall"
[ 2275.366] (II) LoadModule: "synaptics"
[ 2275.366] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 2275.367] (II) Module synaptics: vendor="X.Org Foundation"
[ 2275.367] compiled for 1.12.2, module version = 1.6.2
[ 2275.367] Module class: X.Org XInput Driver
[ 2275.367] ABI class: X.Org XInput driver, version 16.0
[ 2275.367] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 2275.367] (**) Option "Device" "/dev/input/event8"
[ 2275.367] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 2275.367] (**) Option "TapButton1" "1"
[ 2275.367] (**) Option "TapButton2" "2"
[ 2275.367] (**) Option "TapButton3" "3"
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 2275.367] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input8/event8"
[ 2275.368] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
[ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.040
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 2275.368] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 2275.368] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 2275.368] (II) No input driver specified, ignoring this device.
[ 2275.368] (II) This device may have been added with another device file.
[ 2275.368] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
[ 2275.368] (II) No input driver specified, ignoring this device.
[ 2275.368] (II) This device may have been added with another device file.
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Fujitsu FUJ02E3 id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Fujitsu FUJ02B1 id=9 [slave keyboard (3)]
↳ Power Button id=10 [slave keyboard (3)]
↳ FJ Camera id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
running
dmesg | grep -i synaptics
doesn't show anything. However running
dmesg | grep -i psmouse
returns a lot of
psmouse serio1: bad data from KBC - timeout
Last edited by flako (2012-11-08 09:44:59)

I have tried doing that with both linux mint, and now fedora live usb. Neither one loads the touchpad correctly. So yeah, our problems weren't really related
Anyway, I tried looking into the
psmouse serio1: bad data from KBC - timeout
messages, and tried running psmouse proto (defined in /etc/modprobe.conf/psmouse.conf) as both raw and imps as per https://answers.launchpad.net/ubuntu/+s … ion/206950 Unfortunately, that didn't solve anything. Using the raw setting meant that the touchpad wasn't loaded at all (as in not appearing in the Xorg.log at all).
The laptop is quite new, but at the same time what i figured from the touchpad vendor & product ID, the touchpad itself isn't. So it should technically work. Before installing arch i booted into windows to see if everything worked, and found no issues with the touchpad. So I have ruled out any hardware errors. Maybe its just the Fn-key that doesn't work yet in Linux? But that doesn't explain the "psmouse serio1: bad data from KBC - timeout" Any pointers to where I should look/ what commands I should run to delve deeper into this issue?
Last edited by flako (2012-09-09 12:10:51)

Macbook Pro Pinch/Zoom feature does not work with Firefox 6

Can someone please tell me how to fix this major problem?
I can not get the Pinch/Zoom feature on the track pad to work on my Macbook Pro. I am running OS 10.6.8.
I have seen this below in other posts, and have tried it, but it STILL does not work !!!!
'''''Some gestures have been removed in Firefox 4.
'''You can restore the zoom feature by changing the values of the related prefs on the about:config page.
'''browser.gesture.pinch.in -> cmd_fullZoomReduce<br>
'''browser.gesture.pinch.in.shift -> cmd_fullZoomReset<br>'''
'''browser.gesture.pinch.out -> cmd_fullZoomEnlarge<br>'''
'''browser.gesture.pinch.out.shift -> cmd_fullZoomReset<br>''''''
'''To open the about:config page, type about:config in the location (address) bar and press the "Enter" key, just like you type the url of a website to open a website.'''
'''If you see a warning then you can confirm that you want to access that page.'''''''''''
Please someone help me - this is a great feature and its really pissing me off that I can't use it.
HELP !!!

I'VE TRIED THIS:
browser.gesture.pinch.in -> cmd_fullZoomReduce
browser.gesture.pinch.in.shift -> cmd_fullZoomReset
browser.gesture.pinch.out -> cmd_fullZoomEnlarge
browser.gesture.pinch.out.shift -> cmd_fullZoomReset
browser.gesture.pinch.latched -> false
I'VE TRIED ALL OF THE ABOVE NUMEROUS TIMES AND IT DOES NOT WORK ON MACBOOK PRO AND FIREFOX 6.
CAN ANYBODY HELP? THANKS ♥

MBA 11 (2013) pinch zoom does not work after some time, how to fix it ?

Recently I purchased MBA 11 (2013) model ( 4GB ram & 1.3 Ghz dual core). Although I use iPhone 5 & iPad 4 but never used mac. So when I found the track pad is capable of pinch zoom(along with other gesture) I was excited. But later I found after opening few apps (like safari, chrome etc) pinch zoom stop working . I need to restart in order to make it work again. Other gestures works fine just issue with the pinch zoom. Along with this issue I have some other questions as well
1) How to fix this pinch zoom issue?
2) I use eclipse for android development, but when I connect android phone/tablet - os crashes, no idea why?
3) How to uninstall & update apps properly which was downloaded from web (like I installed x-code) ?
4) I want to use mouse (i am comfortable) - I need to know whether right click, wheel, ling click & drag works perfectly.
5) How to back up the os if something goes wrong I can retrieve from there ?

Error 2, 4 (or -4), 6, 40, 1000, 9006
Follow Troubleshooting security software. Often, uninstalling third-party security software will resolve these errors.
There may be third-party software that modifies your default packet size in Windows by inserting a TcpWindowSize entry into your registry. Your default packet size being set incorrectly can cause these errors. Contact the manufacturer of the software that installed the packet size modification for assistance or follow this article by Microsoft: How to reset Internet Protocol (TCP/IP).
Verify that access to ports 80 and 443 are allowed on your network.
Verify that communication to albert.apple.com or photos.apple.com is not blocked by a firewall, or other Internet security setting.
Discard the .ipsw file, open iTunes and attempt to download the update again. See the steps underAdvanced Steps > Rename, move, or delete the iOS software file (.ipsw) below for file locations.
Restore your device while connected to a different network.
Restore using a different computer.
http://support.apple.com/kb/TS3694#error6

Issues with Fn-keys and Synaptics touchpad on Asus X51RL laptop

Hello,
Since I installed Arch on my laptop, it's been working great. But I still have a few issues:
1) Fn-keys do not work. The brightness Fn-keys work, but I think that's done internally by the laptop, since it works even in the BIOS. The sound Fn-keys don't work, which is the ones I really need. How can I fix this? And I read somewhere that I have to switch from the kbd drivers to the evdev driver, is that true?
2) Since the latest update to the synaptics package in testing, the touchpad lost one-touch tapping, along with some other stuff. I know the solution is to disable hotplugging, but I sometimes need to plug in a keyboard or mouse, so I can't. How can I retain the scrolling and one-touch tapping settings from Xorg.conf AND hotplugging while using the latest synaptics?
3) The pre-configured options for the synaptics touchpad in the archwiki are good, but not that accurate. The size of the scrolling section of the touchpad is a bit too large, among other things. It's a minor problem compared to the others, but it'd be nice to fix it. In Windows, I definitely remember the settings being more accurate. Is there a way to have the Synaptics driver autodetect like the Windows one, or am I missing something here?
Thanks a lot in advance!

I have the S62J (Intel verified whatnot version) with this Asus, the brightness keys work. I think they are hard wired though as they work in the BIOS.
I tried the acpi-support, but I haven't had any luck with it yet. I'll have to mess with it some more to see if I'm missing something.
I'm also wondering if there isn't a different keyboard layout I should use. I notice that there is a 30-something-asus-something.fdi (I'm not on the notebook at the moment) on the system, but I don't know if it's being used by anything.
The other observation is that using the Fn button is throwing ACPI calls into my dmesg.log file. I need to research to find out how to use them.

I just wanted to chime in here on the Synaptics Touchpad issues...

I have a Toshiba L305D-S5934 Laptop with an AMD Turion X2 Dual Core Processor, it has a Synaptics touchpad as do most laptops these days and I have run into the following problems: I am running Windows 7 RC Build 7100 (an official download not a torrent download) and my Synaptics Touchpad shows up as a PS2 compatable mouse in device manager. If I download the drivers that come through Windows Update they seem to work fine untill I reboot my system, at reboot just after the Windows 7 splash screen, she blue screens with a memory dump going to somewhere and then does an automatic restart, if I attempt to start windows normally after the restart she bluescreens again with the same results, and this will go on time and time again until I either go into safe mode and remove the Synaptics driver or let startup repair do its thing or do a system restore, all of which leaves me with a Synaptics Touchpad with erattic behavior, that loses its scrolling functionality, and is hypersensitive almost to the point that I can't type much of anything without the cursor jumping around all over the place and relocating like it has a mind of its own. Now Toshiba has something called Toshiba's Value Added Package (not much value there for 64 bit systems it seems this thing was a pain in Vista x64 and it is more of a pain in Windows 7 x64) I will not install the Value added Package until I am convinced t hat Toshiba or whoever makes it gives a rat's rear-end about 64 bit systems and Windows 7 the last time I tried to install it gave all kinds of problems and produced some blue screens of its own I believe. The Value Added Package however includes Toshiba's Flash Cards Utility that makes the Fn key work and gives access to disabling the Synaptics touchpad (you can do this in the driver as well, but when the driver is installed well she bluescreens except in safe mode) The Synaptics driver seems to do okay in safe mode so that could mean that another driver is causing the conflict but something is not wanting to lay nice with the Synaptics driver. I must note however that the Synaptics driver worked just fine in Windows Vista x64. Also I have downloaded the driver from Toshiba's site, the 64 bit Synaptics driver from the Synaptic's site and a couple of others, the one that came closeest to working the best was a version 12.something for HP laptops but the option to disable the touchpad wasn't in the driver. I usually use a mouse with my laptop but I use the touchpad when I take it places with me sometimes, it would be nice to have full functionality of both mouse and touchpad and to be able to disable the touchpad when an external pointing device is attached the way I could in Vista but right now I would settle to just be able to disable the touchpad until this is resolved so I can use the laptop without the cursor jumping all over the place and seemingly having a mind of it's own. As a side note I am very careful about allowing Windows Update to install any updates that it wants at this poing, more than once it has installed things that gave me bluescreens at reboot most notably the Toshiba Value Added Package and the Synaptics driver and maybe an Atheros Wireless driver but it does not yet seem to have the best interests of my PC at heart. On the other hand I have the 32 bit version installed on a Desktop PC with an old Athlon XP 2000+ and 2 GB of Ram it runs wonderfully nearly as well as Windows XP but there is no Synaptics touchpad on the desktop of course, and no Toshiba Value Added Package.
Charles

I have had a similar problem, windows update does NOT update the synaptics touchpad. I have a Toshiba Windows 7 and I did everything that was told by man and beast.
Finally, I went to control panel again, uninstalled synaptics and had to use the a program called Driver Update. This program installed my Realtek Audio even though this was working apparently the two work together. It SUCKS that you have to pay
to install security programs that run your programs but this was the only thing that worked for me and I went through months of not having a touchpad.
I hope this helps others solve their touchpad problems. Good Luck
Sandia

Synaptics Touchpad No Longer Working Properly

Hello Internet!
Hear my plight and tremble: I just recently updated my Synaptics touchpad drivers from the official manufacturer's website. Prior to the update, I could double tap the top left of the touchpad to enable and disable the touchpad. This was a convenient feature that I have grown quite fond of. However, after the update this feature no longer works! I am so devastated... I really enjoyed watching the pretty light outline of my touchpad turn to an evil red when it was disabled. I suppose that I could revert the drivers back to their old form, but I wanted to check if anybody knew a separate fix so that I could have both the new drivers and the old functions that I so cherished.
My model number is: A6Y49UA#ABA
My operating system: Windows 7
Thanks for your help, I'll remember you when I'm the dictator of the world.
This question was solved.
View Solution.

Hi @El-Nacho ,
Welcome to the HP Forums!
It is a terrific place to find answers.
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I see that you upgraded your driver from the manufacturer's site. HP only recommends the drivers listed on the HP driver page. These drivers have all been tested and known to function correctly.When you install drivers from manuacturer's site, they may or may not function correctly with your notebook. OEM can and do sometimes alter a driver so that it functions correctly with your exact notebook.
Downloading or Updating Software and Drivers for HP Computers
If you did not have an issue with the old driver, I suggest you do a driver roll back.
Version 15.3.11.0 is the recommended version for your notebook and Windows 7.
Here is a link to the driver download page should you require it. HP Pavilion dv6-6c10us Entertainment Notebook PC Drivers
Best of Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

New Pavillion DV6 with Windows 7. Synaptics TouchPad cannot start - error code 10.

I've had the laptop for about three weeks. Installed an HP 3005pr USD 3.0 Port Replicator a few days ago and the Synaptics TouchPad stopped working (perhaps not related?). Keyboard works fine. I've used a Microsoft USB keyboard and mouse for several weeks with no problem. Spent an hour and 20 minutes with HP tech support while the BIOS was refreshed and the TP driver updated (although the download didn't install correctly).
I am now getting a message: "device cannot start (code 10).
Any suggestions?

Hi,
First, can you provide the specific model of dv6 you have, that can impact what steps are suggested.
Which Touchpad driver did you attempt to install with HP Tech Support? You mentioned that the driver didn't install correctly, did it generate an error message? If so what was the error?
The first thing I would do in your situation would be to use MS System Restore to go back to a restore point when the Touchpad was working, if such a restore point exists. Take a look at the document below, and look for the section called "Restoring Windows to a previous point" and follow those steps, choosing a restore point when you are sure that the touchpad was working.
Using Microsoft System Restore (Windows 7)
Let us know what happens.
Although I am an HP Employee, I am speaking for myself and not for HP.

Satellite L955-10K - Synaptics Touchpad Driver does not work properly

Hello, ASRR here.
I've been having a problem with my Synaptics touchpad driver since yesterday. I am very used to using the "gestures" to work with my touchpad and the gestures haven't worked properly (in fact at all) for a while. The two-finger scrolling, the three-finger touch and others (actually all of the gestures) do not work anymore.
The cursor moves, and works fine but the gestures don't.
When I go to the Mouse option in the Control Panel, a window pops up stating that the PC is "Unable to connect to the Synaptics Pointing Device Driver." and asks me whether I want to uninstall it.
I have tried uninstalling it, then going on the support page for Toshiba and downloading a driver that was suitable for my model, operating system, etc.
When I set up the driver I downloaded and restart the PC, the same window pops up when I try and go to the Mouse options in the Control Panel and the gestures do not work.
One interesting thing I noticed however, is the fact that when I roll back the driver (in the Hardware properties- then settings) the gestures work FINE. However, as it always asks you to restart the computer in order for the Rolling back of the driver to take place, when I do restart it, it sets the Microsoft touchpad driver from 2006; which does not include the gestures I need.
I have tried multiple times to fix it but I can't. I went to the UEFI firmware set up and tried resetting it to default but with no success.
I really do not know what to do. Could somebody PLEASE help?
My Toshiba Model is a Satellite L-955-10K with a 64bit processor and originally installed Windows 8 operating system.
Any help would be greatly appreciated. Thanks

>One interesting thing I noticed however, is the fact that when I roll back the driver (in the Hardware properties- then settings) the gestures work FINE. However, as it always asks you to restart the computer in order for the Rolling back of the driver to take place, when I do restart it, it sets the Microsoft touchpad driver from 2006; which does not include the gestures I need.
To me it looks like the Synaptics touchpad driver could not be installed properly and after the new restart the touchpad driver isnt indicated by the Windows 8 system.
By the way: are you still using the Win 8? Didnt you upgrade the system to Win 8.1? Should do this since many different bugs have been solved in new Win 8.1 version.
Back to the Synaptics touchpad driver.
Usually the drivers should be downloaded from the Toshiba driver page but in some cases you could also use the drivers directly from manufacturer pages. In this case the touchpad driver has been released by Synaptics and it would be interesting to know how the touchpad driver from Synaptics driver page would act on your notebook
http://www.synaptics.com/en/drivers.php

Pinch zoom on Synaptics touchpad?

Similar Messages

Maybe you are looking for