Remove Touchpad Buttons G510

Hello everyone,
on my two month old lenovo g510 the left mouse button from the touchpad is very wobbly. The right mouse button is still fine. Is it possible to remove the button to see whats wrong with the left one? Or do I have to send my g510 to lenovo?!
Thanks in advance.

hi bagges,
Welcome to Lenovo Community Forums!
The touchpad for this model is attatched to the Top cover "The cover where your palm rests when typing"
You can find a guide here on how to remove the part.
http://download.lenovo.com/consumer/mobiles_pub/lenovo_g400g500g405g505g410g510_hmm.pdf
Note: if the system is still within warranty period, I strongly suggest to have the laptop Touchpad fixed by lenovo technicians, Call Technical Team and have the assess the situation.
Regards
Solid Cruver
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Similar Messages

Satellite U400 - Is it possible to replace the touchpad button?

Hello
I need help please. I want to know if there is a possible way to change the button at my Satellie U400 because they are getting soft and they are not as good and hard as it was before, so please anyone know's if I can remove those and put 2 new one's?
If you dont understand exactly what I mean take a look at the picture and you will see/understand.
[http://oi56.tinypic.com/j0wwoj.jpg]
thank you.

Hi Loow,
Im sure its possible to replace the touchpad buttons because you can replace everything on a notebook. But I think its a little bit tricky because you have to disassemble a lot of parts and thats not easy.
You should ask an authorized service provider The guys can order new spare part for you and exchange it. Just write an email for example to get in contact with them.
You can find a list of ASPs here:
http://eu.computers.toshiba-europe.com > Support & Downloads > Find an authorized service provider

DV5-1000 touchpad buttons, premature wear

After about a year of using my DV5-1000, the silver coated left touchpad button began to wear through to the black plastic underneath. Also, the button became noticeably loose, especially when compared to the right touchpad button. It eventually got to the point where the button would click unreliably.
I managed to buy a replacement palmrest part for the DV5, which contains the touchpad assembly (you cannot buy the assembly separately). Unfortunately, the palmrest is an integral part of the laptop, requiring 75% of it to be disassembled to remove the original part. I downloaded a service manual and went to work... and I got it done after 2 long hours. The new part fit properly and the laptop appeared as new.
A year later, I'm faced with the same problem yet again! I am not abusive to the touchpad buttons. This kind of wear should not be happening. I dread having to take apart the laptop again... but I am worried that the button will start developing click problems as the previous one did. I wonder if some kind of protective coating added to the button would help it. Anybody else here suffer premature wear to the left touchpad button?
"If you keep an open mind, life will give you more possibilities."

I had a look at some of the newer DV5 models and... I'm rather taken aback with how HP solved the touchpad button problem. They no longer have tactile keys. Instead, there's a soft touch membrane. This makes it very difficult to control sustained pressing of the button, as the travel from on to off is so short. It was a real cop-out in my mind, that HP didn't stick with tactile buttons. Sure, there were some problems with how they were intially implemented, but c'mon--so many other laptop makers have tactile buttons that don't wear out. Why couldn't HP have gone that route of just improving the button?
Also, what's with all of the wacky patterns that HP is now slathering over their laptop casings? It makes the laptop look a lot less professional. If they want to appeal to kids, make it so that there's an optional shell you can get with the laptop with whatever zany pattern you wish. Or instead, just opt for something conservative and wear resistant.
"If you keep an open mind, life will give you more possibilities."

T430 right touchpad button stuck

Hello,
I'm not sure whether this issue has been talked about here, but i can't find anything on the subject anywhere.
My T430 right touchpad button gets stuck whenever i press it (by stuck, i mean mechanically stuck). Is there anyone else with the same problem?

Hi,
Welcome to Lenovo Community Forums!
I’m sorry to hear that right click button of the touchpad got stuck in your Lenovo ThinkPad T430.
In some situations dirt, hair, dust, etc. can obstruct the buttons causing them not to work. Try to insert a sheet of thick paper under the button to remove the dirt that can be stuck there.
If you are confident enough, you can open the laptop to reach under the touchpad, clean and do a proper reseating. Refer the hardware maintenance manual to understand how to reseat the palm rest assembly.
Hope this helps!
Best regards,
Mithun.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

How to remove the buttons in ALV GUI?

Hi All,
I am using the FM REUSE_ALV_GRID_DISPLAY for disaplying the ALV grid. i need how to remove these buttons ( mail word processing, loal file, Mail recipient, ABC analysis, Microsoft Execl and Graphics ) from the ALV Gui?
please give solution.
Regards,
Santha

hi,
IT_EXCLUDING TYPE SLIS_T_EXTAB OPTIONAL
you need to append the Fucntion codes to the it_exclude and then pass it to the parameter it_excluding.
append '&ABC' to it_excluding.
append '&BAC' to it_excluding.
call function 'REUSE_ALV_GRID_DISPLAY'
IT_EXCLUDING = it_exlcuding
Regards
Anver

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

Remove EDIT button from FPM ToolBar

Hi All,
I am new to FPM, and I am working on SRM 7.0. In the Monitor Shopping cart WD application, after search event, a list of Shopping Carts are displayed, when we click on one of the SC number, the SC screen opens as a new Pop-up.
Here we have an EDIT button, and we need to remove this button from this screen.
Technical Details(EDIT button):
Application: /SAPSRM/WDA_L_FPM_OIF
Web Dynpro Component: FPM_OIF_COMPONENT
Window Information: FPM_WINDOW
View Information: CNR_VIEW
Configuration ID: ZSAPSRM_WDCC_FPM_OIF_SC_PROFNL
Technical Details(SC screen):
Application: /SAPSRM/WDA_L_FPM_OIF
Web Dynpro Component: /SAPSRM/WDC_UI_SC_DOFC_HD
Window Information: IV_L_FPC_CA_HDR
View Information: V_SC_BOFC_HD
Configuration ID: /SAPSRM/WDCC_FPM_SC_HD_PR
Appreciate any help on this.
Thanks,
Prabhakaran

Hi Prabhakaran
You will need remove the static usage of config id ZSAPSRM_WDCC_FPM_OIF_SC_PROFNL and make use of dynamic component configuration depending on the particular scenario.
Create two configuration id's ZSAPSRM_WDCC_FPM_OIF_SC_PROFNL1 and ZSAPSRM_WDCC_FPM_OIF_SC_PROFNL2. Set visible property of Edit button as visible in the first config ID and none in the second.
Now assign this config ID dynamically depending on the scenario. If scenario is Monitor SC, then assign config ID ZSAPSRM_WDCC_FPM_OIF_SC_PROFNL2, else assign config ID ZSAPSRM_WDCC_FPM_OIF_SC_PROFNL1.
Please refer the below document for usage of dynamic component configuration.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70337875-167f-2e10-daa7-a1c69d55ee95
Hope this helps.
Regards
Lorraine

Hide or remove delete button - ESS personal data iView

Hi, regarding for example ESS(50.4) personal data overview iView.
How to hide or remove delete button in the personal data overview iView screen(I know that this can be done on the ITS server side (web studio), but I want to do this in R3)
/Best Regards
Patrick

Achim was right on. Edit/Change the Internet Service in R/3. A few things to consider though....
(1) if using the original service, you may want to create a copy of theme 99 into your own theme (any number will do...99 is just the default theme). If doing so, be sure to change the service's service file (yeh, I always loved that about SAP's naming) to point the ~theme paramter to your new theme.
or
(2) Copy the entire service into your own "Z" service. Then modify the templates as you wish. You will need to point the iView to this "Z" service too.
Also, it is best to do it via SE80 vs. file level because then it will be part of a transport and follow the correct path through the landscape.
Now, if you really want to go back to R/3....find the function module or program the transaction code for your service actually calls, make a "Z" version of it, modify it, create your own "Z" t-code to call it, and THEN modify the internet service's service file (either the original SAP one or a custom version) to call your new "Z" t-code. Lot of work...yes, I know....but that's the way it's done if you gotta get back down to the ABAP level.
Hope this helps!
Message was edited by: Christopher Solomon

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.

How to remove go button for prompt

Hi everyone,
I got a requirement from client asking to remove 'GO' button for prompts which has single value to select and have go button for those which need multiple select values.
If prompt has one select value the report has to change based the selection of value no need to press go button.
Will it be possible to remove 'GO' button for some prompt filter and have for others .
Thanks in advance.
Regards
Sandeep

Sandeep,
I think it's not possible to remove the 'GO' button for prompts. If you need to rename the 'GO' button, follow the below steps.
Go to {OracleBIDir}:\oraclebi\web\msgdb\l_en\messages and Open the globalfiltermessages.xml file.
Find this text
<WebMessage name="kmsgGFPGo"><TEXT>Go</TEXT></WebMessage>
Edit the 'Go' which is there between the TEXT tags.. for e.g.., replace the Go with Confirm
<WebMessage name="kmsgGFPGo"><TEXT>Confirm</TEXT></WebMessage>
Thanks,
Balaa...

How to dynamically add/remove a button from the ribbon based on some condition? (Ribbon XML)

Hi,
I have a ribbon (done using ribbon XML) with menu options. I need to remove few buttons from the menu dynamically based on some condition. Also, I want to change the label of another button. How to achieve this programmatically? (C#)
Thanks in advance.
Thanks Prasad

Hello Prasad,
Use callbacks for populating Ribbon controls such as menu, dropDown, gallery and etc. Then you can use the
Invalidate or
InvalidateControl methods of the
IRibbonUI interface to get your callbacks invoked when required. Thus, you will be able to delete the required item(s).
You will find the following articles in MSDN helpful:
Chapter 11: Creating Dynamic Ribbon Customizations (1 of 2)
Chapter 11: Creating Dynamic Ribbon Customizations (2 of 2)
To change the label of your controls at runtime you need to use the getLabel callback and call the Invalidate or InvalidateControl methods of the IRibbonUI interface. The following series of articles describe the Fluent UI in depth:
Customizing the 2007 Office Fluent Ribbon for Developers (Part 1 of 3)
Customizing the 2007 Office Fluent Ribbon for Developers (Part 2 of 3)
Customizing the 2007 Office Fluent Ribbon for Developers (Part 3 of 3)

I hit the remove device button on itunes. How do i add my iphone back?

i hit the remove device button on itunes. How do i add my iphone back?

You will either need to use iTunes Match or automatic downloads on it, or redownload some of your past purchases.
Associating a device to an account : http://support.apple.com/kb/HT4627

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.

How to remove the buttons coming from report program?

Hi All,
I need to remove the buttons from an iview which is a sap transaction. when i execute the report program which uses a ldb (PCH) shows a selection screen having all the buttons.
We have created variants for this.Now i want to remove the buttons which are coming from the report program.how to do this ?
Lakshmi.

Goto sicf ->sap->bc->gui->sap->its->
open Webgui application
in the GUI Config enter the following parameters.
~noHeaderOkCode = 1
~webTransactionType = EWT.
All buttons can also be removed by ~webgui_simple_toolbar =0 ..
Also now open the trancsaction of the program form SE93 for which you want to hide
the Menu bar, in its properties select the EASY WEB TRANSACTION radio button.

Remove Touchpad Buttons G510

Similar Messages

Maybe you are looking for