F9 and F10 keys and my Logitech Mouse

I've been using the wireless Logitech Mouse with my iMac G5 and have got all my buttons set juuuuuust the way I like them. I recently got the PB G4 17" and I am trying to set my mouse buttons like my iMac G5. I having problems with the F9 and F10 keys ( all windows and application windows ) When I press them the keyboard illumination thingy pops up. If I look in keyboard shortcuts in system preferences F9 and F10 are set for all windows and app. windows?? two actions for the same buttons??

To use the F9 and F10 keys to control Exposé, you need to do one of two things:
- Press the fn key with F9 and/or F10
- Go to System Preferences > Keyboard & Mouse > Keyboard and check the box 'Use F1-F12 keys to control software features' and use the fn key with F9 and/or F10 to control the keyboard backlighting. If you check that box, then Exposé will behave in the same way it does on your iMac wrt your mouse buttons.

Similar Messages

10.5.2 crasing while using wireless logitech mouse

Having just installed the 10.5.2 update my mac was constantly crashing. Unable to work out what was wrong, I had a suspicion it was my mouse. After disconnecting my Logitech trackball, everything was fine. My colleague who is also running 10.5.2 and a logitech mouse experienced the same problem all yesterday. I'd submit this issues at the logitech site - though there is nowhere to do so.

Hi hunthunthunt-
greetings and welcome to the Apple boards
Good job troubleshooting. Is this a BlueTooth device or does it use a dongle?
Unfortunately it is up to Logitech to release updated compatible drivers. Is there anything on the support section of the site that refers to updated drivers?
Luck-
DaddyPaycheck

I am having troubles with 3 things: scrolling with my laptop mouse, controlling my laptops volume with F9 and F10 keys, and I can not copy and paste images.

I am having troubles with 3 things: scrolling with my laptop mouse, controlling my laptops volume with F9 and F10 keys, and I can not copy and paste images.

Hello,
Try disabling graphics hardware acceleration. Since this feature was added to Firefox, it has gradually improved, but there still are a few glitches.
You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).
Then perform these steps:
*Click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
*In the Firefox options window click the ''Advanced'' tab, then select "General".
*In the settings list, you should find the ''Use hardware acceleration when available'' checkbox. Uncheck this checkbox.
*Now, restart Firefox and see if the problems persist.
Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:
[[Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems]]
[[Upgrade your graphics drivers to use hardware acceleration and WebGL]]
volume controls issues are windows, not firefox.
How your copy and paste your image? from where to where

X11, xinput and the Logitech LX710 Cordless Desktop Laser Mouse

Hello all,
First, lets be clear, the problem I'll describe in the lines below drives me nuts. This forum is my last change before:
1 - Throwing myself through the window
2 - Spend 50€ for a new mouse
Before taking one of those solutions here is my problem:
I bought a Logitech LX710 kit with keyboard and a mouse connected to a single usb bundle. The keyboard works fine but using the mouse can transform you insane. The single click works 1 time on 3, the double click is random, the single click is sometime taken as a press and hold. At the beginning I thought it was an hardware problem but the kit works fine on windows .
So here is how I configure my kit:
¤ Here is what the /proc/bus/input/devices lists
[romain@arch ~]$ more /proc/bus/input/devices
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
U: Uniq=
H: Handlers=kbd event2
B: EV=3
B: KEY=10000000000000 0
I: Bus=0003 Vendor=0471 Product=0331 Version=0100
N: Name="Philips SPC 1300NC Webcam"
P: Phys=usb-0000:00:1d.7-3/button
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0003 Vendor=046d Product=c517 Version=0110
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f
I: Bus=0003 Vendor=046d Product=c517 Version=0110
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.0-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/input/input5
U: Uniq=
H: Handlers=kbd mouse1 event5
B: EV=1f
B: KEY=837fff042c332f bf08444400000000 ff0001 1f848a37cc00 667bfadd71dfed 9e000000000000 0
B: REL=1c3
B: ABS=100000000
B: MSC=10
¤ here is how I configure X11:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "pad" "SendCoreEvents"
EndSection
Section "Files"
FontPath "/usr/share/fonts/default/Type1"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "ServerFlags"
#Option "Xinerama" "0"
Option "AIGLX" "on"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
#Driver "evdev"
# Change the value of the "Dev Phys" option to the physical
# address of the corresponding keyboard, found in the file
# /proc/bus/input/devices .
Option "Protocol" "kbd"
#Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event4"
# Configure your keyboard as usual
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
#Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-*/input1"
Option "Device" "/dev/input/event5"
Option "XExtentionPointer"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "Mode" "Absolute"
Option "USB" "On"
Option "Tilt" "On"
Option "Thresold" "10"
EndSection
Section "InputDevice"
Identifier "cursor"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "Mode" "Relative"
Option "USB" "On"
Option "Speed" "3.0"
Option "Thresold" "10"
EndSection
Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "Mode" "Absolute"
Option "USB" "On"
Option "Tilt" "On"
Option "Thresold" "10"
EndSection
Section "InputDevice"
Identifier "pad"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "ButtonsOnly" "on" # IMPORTANT
Option "Button9" "2"
Option "Button13" "3"
Option "Mode" "Absolute"
Option "USB" "On"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Maxdata (RogenTech) B102035W"
HorizSync 31.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7600 GS"
Option "AddARGBGLXVisuals" "True"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
¤ And here is the X11 log:
X.Org X Server 1.6.3
Release Date: 2009-7-31
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH x86_64
Current Operating System: Linux arch 2.6.30-ARCH #1 SMP PREEMPT Mon Aug 17 16:06:45 CEST 2009 x86_64
Build Date: 14 August 2009 11:20:44AM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 24 20:43:22 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "stylus"
(**) |-->Input Device "eraser"
(**) |-->Input Device "pad"
(**) Option "AIGLX" "on"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/default/Type1" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules/extensions/nvidia,/usr/lib/xorg/modules/drivers,/usr/lib/xorg/modules"
(**) Extension "Composite" is enabled
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(II) Loader magic: 0x74c0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0:1:0:0) 10de:0392:1043:822a nVidia Corporation G73 [GeForce 7600 GS] rev 161, Mem @ 0xfd000000/16777216, 0xc0000000/268435456, 0xfc000000/16777216, I/O @ 0x00008c00/128, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 96.43.13 Thu Jun 25 18:28:54 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 2.2.4
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) Wacom driver level: 47-0.8.3-7 $
(II) NVIDIA dlloader X Driver 96.43.13 Thu Jun 25 18:07:12 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "nvidia-auto-select +0+0"
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "CRT-0"
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 7600 GS at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 05.73.22.50.00
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 7600 GS at PCI:1:0:0:
(--) NVIDIA(0): Maxdata (RogenTech) B102035W (CRT-0)
(--) NVIDIA(0): Maxdata (RogenTech) B102035W (CRT-0): 400.0 MHz maximum pixel
(--) NVIDIA(0): clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select+0+0"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (99, 98); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) NVIDIA(0): Initialized GART.
(II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
(**) Option "SendCoreEvents" "true"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Mouse0: Device: "/dev/input/event5"
(II) Mouse0: Found 12 mouse buttons
(II) Mouse0: Found x and y relative axes
(II) Mouse0: Found scroll wheel(s)
(II) Mouse0: Found keys
(II) Mouse0: Configuring as mouse
(II) Mouse0: Configuring as keyboard
(**) Mouse0: YAxisMapping: buttons 4 and 5
(**) Mouse0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Mouse0" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Mouse0: (accel) keeping acceleration scheme 1
(**) Mouse0: (accel) filter chain progression: 2.00
(**) Mouse0: (accel) filter stage 0: 20.00 ms
(**) Mouse0: (accel) set acceleration profile 0
(II) Mouse0: initialized for relative axes.
(**) Option "SendCoreEvents"
(**) stylus: always reports core events
(**) stylus device is /dev/input/wacom
(**) stylus is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "Tilt" "On"
(**) Option "USB" "On"
(**) stylus: reading USB link
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : No such file or directory
(EE) Couldn't init device "stylus"
(II) UnloadModule: "wacom"
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/wacom
(**) eraser is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "Tilt" "On"
(**) Option "USB" "On"
(**) eraser: reading USB link
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : No such file or directory
(EE) Couldn't init device "eraser"
(II) UnloadModule: "wacom"
(**) Option "SendCoreEvents"
(**) pad: always reports core events
(**) pad device is /dev/input/wacom
(**) pad is in relative mode
(**) WACOM: suppress value is 2
(**) Option "USB" "On"
(**) pad: reading USB link
(**) Option "ButtonsOnly" "on"
(**) pad: buttons only
(**) Option "Button9" "2"
(**) pad: button9 assigned to 2
(**) Option "Button13" "3"
(**) pad: button13 assigned to 3
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : No such file or directory
(EE) Couldn't init device "pad"
(II) UnloadModule: "wacom"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event5"
(WW) Logitech USB Receiver: device file already in use. Ignoring.
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for "Logitech USB Receiver"
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event4"
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as keyboard
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "fr"
Look at this section of the Xorg.0.log file
(**) Option "SendCoreEvents" "true"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Mouse0: Device: "/dev/input/event5"
(II) Mouse0: Found 12 mouse buttons
(II) Mouse0: Found x and y relative axes
(II) Mouse0: Found scroll wheel(s)
(II) Mouse0: Found keys
(II) Mouse0: Configuring as mouse
(II) Mouse0: Configuring as keyboard
(**) Mouse0: YAxisMapping: buttons 4 and 5
(**) Mouse0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Mouse0" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Mouse0: (accel) keeping acceleration scheme 1
(**) Mouse0: (accel) filter chain progression: 2.00
(**) Mouse0: (accel) filter stage 0: 20.00 ms
(**) Mouse0: (accel) set acceleration profile 0
(II) Mouse0: initialized for relative axes.
I think this is the problem. Mouse0 is well detected, configured as a mouse, the as a keyboad and to finish, xinput add it as
type: KEYBOARD
. How can I avoid that? Where am I wrong? Do you see anything else in my configuration, or in the log that can help me?
Hoping someone can help me, I've already open the window...
Regards,
KaB

I've got the same hardware and have not yet experienced any issues. However, I am using openSUSE 11.1 Here the xorg config:
# SaX generated X11 config file
# Created on: 2009-08-08T07:17:17-0400.
# Version: 8.1
# Contact: Marcus Schaefer <[email protected]>, 2005
# Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
# Automatically generated by [ISaX] (8.1)
# PLEASE DO NOT EDIT THIS FILE!
Section "Files"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/local"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/URW"
FontPath "/usr/share/fonts/Speedo"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/latin2/misc:unscaled"
FontPath "/usr/share/fonts/latin2/75dpi:unscaled"
FontPath "/usr/share/fonts/latin2/100dpi:unscaled"
FontPath "/usr/share/fonts/latin2/Type1"
FontPath "/usr/share/fonts/latin7/75dpi:unscaled"
FontPath "/usr/share/fonts/baekmuk:unscaled"
FontPath "/usr/share/fonts/japanese:unscaled"
FontPath "/usr/share/fonts/kwintv"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/uni:unscaled"
FontPath "/usr/share/fonts/CID"
FontPath "/usr/share/fonts/ucs/misc:unscaled"
FontPath "/usr/share/fonts/ucs/75dpi:unscaled"
FontPath "/usr/share/fonts/ucs/100dpi:unscaled"
FontPath "/usr/share/fonts/hellas/misc:unscaled"
FontPath "/usr/share/fonts/hellas/75dpi:unscaled"
FontPath "/usr/share/fonts/hellas/100dpi:unscaled"
FontPath "/usr/share/fonts/hellas/Type1"
FontPath "/usr/share/fonts/misc/sgi:unscaled"
FontPath "/usr/share/fonts/xtest"
FontPath "/opt/kde3/share/fonts"
InputDevices "/dev/gpmdata"
InputDevices "/dev/input/mice"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "on"
Option "ZapWarning" "on"
EndSection
Section "Module"
Load "dri"
Load "dbe"
Load "freetype"
Load "extmod"
Load "glx"
EndSection
Section "InputDevice"
Driver "kbd"
Identifier "Keyboard[0]"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "microsoftpro"
Option "XkbRules" "xfree86"
EndSection
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "14"
Option "Device" "/dev/input/mice"
Option "Name" "Logitech USB Receiver"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
DisplaySize 428 255
HorizSync 30-81
Identifier "Monitor[0]"
ModelName "SAMSUNG SYNCMASTER"
Option "DPMS"
Option "PreferredMode" "1440x900"
VendorName "SAM"
VertRefresh 43-75
UseModes "Modes[0]"
EndSection
Section "Modes"
Identifier "Modes[0]"
Modeline "1440x900" 104.58 1440 1520 1672 1904 900 901 904 931
Modeline "1440x900" 85.75 1440 1488 1520 1600 900 903 909 925 +HSync -Vsync
Modeline "1280x960" 105.61 1280 1360 1496 1712 960 961 964 995
Modeline "1280x960" 86.75 1280 1328 1360 1440 960 963 967 988 +HSync -Vsync
Modeline "1024x768" 81.80 1024 1080 1192 1360 768 769 772 802
Modeline "1024x768" 76.16 1024 1080 1192 1360 768 769 772 800
Modeline "1024x768" 69.71 1024 1080 1184 1344 768 769 772 798
Modeline "1024x768" 69.50 1024 1072 1104 1184 768 771 775 796 +HSync -Vsync
Modeline "1024x768" 64.11 1024 1080 1184 1344 768 769 772 795
Modeline "800x600" 48.91 800 840 920 1040 600 601 604 627
Modeline "800x600" 45.50 800 840 920 1040 600 601 604 625
Modeline "800x600" 44.00 800 848 880 960 600 603 607 622 +HSync -Vsync
Modeline "800x600" 42.11 800 840 920 1040 600 601 604 623
Modeline "800x600" 38.22 800 832 912 1024 600 601 604 622
Modeline "1440x900" 106 1440 1520 1672 1904 900 903 909 934 +hsync -vsync
EndSection
Section "Screen"
DefaultDepth 24
SubSection "Display"
Depth 15
Modes "1440x900" "1280x960" "1024x768" "800x600"
Virtual 3840 1200
EndSubSection
SubSection "Display"
Depth 16
Modes "1440x900" "1280x960" "1024x768" "800x600"
Virtual 3840 1200
EndSubSection
SubSection "Display"
Depth 24
Modes "1440x900" "1280x960" "1024x768" "800x600"
Virtual 3840 1200
EndSubSection
SubSection "Display"
Depth 8
Modes "1440x900" "1280x960" "1024x768" "800x600"
Virtual 3840 1200
EndSubSection
Device "Device[0]"
Identifier "Screen[0]"
Monitor "Monitor[0]"
EndSection
Section "Device"
BoardName "ATI Radeon HD 3670"
Driver "radeonhd"
Identifier "Device[0]"
Option "monitor-DVI-I_1/digital" "Monitor[0]"
VendorName "ATI"
EndSection
Section "ServerLayout"
Identifier "Layout[all]"
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
Option "Clone" "off"
Option "Xinerama" "off"
Screen "Screen[0]"
EndSection
Section "DRI"
Group "video"
Mode 0660
EndSection
Section "Extensions"
EndSection

Black Keys and Black Glossy Mouse

I'm new to the Mac, so forgive me if my question seems blasphemous: I don't know if it's design no-no or something, but would it so hard to make version of the aluminum keyboard that has black keys, and a black version of the Mighty mouse? I like my new iMac, but when I look at the setup on my desk, it seems like it's jusssst so from perfection. Perhaps someone can suggest a matching keyboard/mouse? The only thing I've come across is the PC based Logitech glossy/aluminum (Bluetooth) keyboard and new Air Mouse (both much too expensive, by the way). Thanks.

Hello and Welcome to Apple Discussions.
I agree that a re-design, or shock-horror a choice of colours, is needed. Please leave feedback for Apple here:
http://www.apple.com/feedback/imac.html
kind regards
mrtotes

The back and forward buttons on Logitech mouse don't work

My logitech performance MX back and forward buttons don't work. I tried in safe mode and they still don't work. I tried creating a custom shortcut in logitech setpoint and that didn't work either. I tried using the native mouse driver and not logitech. No luck.
I really like this functionality. Is there a way to enable these buttons?

Hi mike,
i'm not sure if this will help but how about this add-on called "Vimperator". It is easy to use and works like vim. (Try this as an alternate till we figure out the problem) :)
Hope that helped.

F10 key and focus lost

When I press the F10 key in Windows on a JavaFX program the focus goes to the titleBar, you can see it if you press Return later. Is there any way to disable this functionality?, I use keyboard accelerators and F10 key can't be used because of this behaviour.
Thanks in advance

I know that it's the default behaviour that's way I discover where was the focus after pressing F10. I have changed my keyboard accelerators to not use F10 key but if it's pressed the focus goes to the title bar (if you don't have a menu) and in my case, I use an undecorated window so is more difficult to see it. If you press return key after F10 you will get the window menu popup.
It will be great to be able to control this...

I am having problem with my F9 AND F10 KEYS TO CONTROL sound

i think my f9 and f10 keys are not working properly..
This question was solved.
View Solution.

Ok. I found where was the problem. Actually the letter O should be the number 0.
Please do the below procedure.
Uninstall the current driver for the IDT audio.
Resource:
Uninstalling Software in Windows 7
Uninstall or change a program in Windows 7
Download and install the latest IDT audio driver for your model from here.
Restart the system.
Uninstall the current driver for the HP Quick Launch Software (if it's installed in the system).
Resource:
Uninstalling Software in Windows 7
Uninstall or change a program in Windows 7
Download and install the latest HP Quick Launch Software driver for your model from here.
Restart the system.
Download and install the latest HP On-Screen Display Utility version from here.
Restart the system and check the results.
** Say thanks by clicking the "Thumb up" icon which is on the left. **
** Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue. **

Logitech Mouse (MX 1000), Logitech Control Centre 2.3.1, Leopard and iTunes

I have installed Leopard ever since it came out in Late Oct. On my Mac mini (PPC), I use a logitech mouse (MX1000) with the latest software from Logitech. Everything was fine until this morning, whenever I use iTunes if I move my mouse pointer anywhere near the volume slider, it automatically moves the slider to the far left (no volume). So now I cannot control the volume or even skip tracks because as I mentioned, if the mouse pointer is anywhere near the volume slider it moves the slider.
I am wondering if anyone with a similar setup of mine is experiencing the same problems as me.

Hi, all!
Just a "me, too" to add to oceans' comments about SteerMouse.
I tried then purchased it recently, primarily because it provides what I consider superior mouse tracking speed/acceleration control for my Apple wireless mouse, well beyond the built-in drivers. When I switch to an older Logitech mouse (OpticalMouse11), SteerMouse enables some handy programmable functions I'd never been able to manage before. Thus, worth it to me... [1]
Of course, the new Logitech Control Center 2.0.0 is free, so I'd suggest trying both to evaluate what provides acceptable performance.
Regards,
Dean
[1] I'd guess the tried-and-true USB Overdrive would also be excellent for this case; I simply haven't tried recent versions because Bluetooth support hasn't been added yet. But it's been the favorite of many Mac folks for years.

DEFAULT&SMARTBAR to commit and F10 Key to commit. Is there a difference?

I'm using the Menu Module DEFAULT&SMARTBAR in the form. When a user creates a record and uses the SAVE icon validation occurs in the form. However when the user hits the F10 key (save record), sometimes but not always validation in the form is being ignored. Is there a way to synchronize those 2 methods to commit a record?
We have enabled the key layout for 6i in the frmpcweb.res file. The form version we are using is Forms [32 Bit] Version 10.1.2.3.0 (Production)
Thanks

Hi!
If your key-mapping is like forms 6i client/server, the F10 key executes the key-commit trigger.
If there is no key-commit trigger in your form, the standard commit_form build-in is beeing executed.
Regards

Running Boot Camp in Windows 7 with Bluetooth Wireless Keyboard and Wireless Magic Mouse

NOTE: I was installing a fresh copy of Windows 7 Professional on a 27" iMac mid-2010 with a Processor Speed of 2.93 GHz, a Core i7 Processor Type, a Quad Core Processor Configuration, 8GB RAM, and a ATI Radeon HD 5750 Graphics Card. I run Snow Leopard so it is a 64-bit OS. I have a Wireless Keyboard and Wireless Magic Mouse as well. In order to install Windows 7 you need a Wired Keyboard and Mouse. You will also need a Wired Keyboard and Wired Mouse to update Boot Camp.
Updating Boot Camp Assistant (VERY IMPORTANT)
First, plug in a wired keyboard and wired mouse. The Boot Camp Assistant version that came with my iMac was 3.0 so I upgraded it to 3.1 and then to 3.2. I'm not sure if only the upgrade to 3.1 is necessary, but I took it a step further. I was told by Apple Tech Support that you first needed to upgrade to version 3.1 before being able to upgrade to 3.2 These upgrades will not be found using Software Update on the Mac. However, they can be found at http://support.apple.com/downloads/#macoscomponents
They also have software updates for 32-bit machines as well and MacBook Pro updates.
NOTE: Before updating the version of Boot Camp, but after installing Windows 7 and after putting in the Mac OS X Install DVD to run Setup.exe to download the Mac drivers, run Software Update for the Mac while logged into Windows 7 by clicking on Start - All Programs - Software Update for any additional updates.
Next I installed Boot Camp Software Update 3.1 for Windows 64 bit found at http://support.apple.com/kb/DL1336
I then ran Software Update for the Mac while logged into Windows 7 by clicking on Start - All Programs - Software Update
Then I installed Boot Camp Software Update 3.2 for Windows 64 bit found at http://support.apple.com/kb/DL979
I then installed Boot Camp 3.2 Update for iMac (early 2011) found at http://support.apple.com/kb/DL979 but I'm not sure if this was necessary.
Once Boot Camp 3.2 has been installed I ran Software Update for the Mac again while logged into WIndows 7 to make sure I had all the updates.
Configuring a Bluetooth device on a Windows-based computer
(from http://support.microsoft.com/kb/952818)
How to make sure that the Bluetooth service is started (MY COMPUTER WAS ALREADY SET UP TO RUN BLUETOOTH, SO THE NEXT 8 STEPS COULD BE OPTIONAL)
Open the Microsoft Management Console (MMC) snap-in for Services. To do this, follow these steps.
Windows Vista or Windows 7Windows XP
Click Start, and then click Run.
Copy and then paste (or type) the following command in the Open box, and then press ENTER:services.msc
Click Start , copy and then paste (or type) the following command in the Start Searchbox, and then press ENTER:services.msc
In the Programs list, click Services.
If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
Double-click the Bluetooth Support service.
If the Bluetooth Support service is stopped, click Start.
On the Startup type list, click Automatic.
Click the Log On tab.
Click Local System account.
Click OK.
If you prompted to restart the computer, click Yes.
How to connect the Bluetooth device to the computer
1. First off, you need to go into Mac OS and remove the keyboard and mouse from your Bluetooth settings entirely. You'll add them back in later (see 9) below).
2. Boot into Windows using a USB connected Mouse and Keyboard.
3. Go to Control Panel – Hardware and Sound – Device and Printers – Add a Device
4. Turn on the Mouse to send out a signal and once it sees it select it to be paired to the computer
5. Run 3.) again except select the keyboard.
6. Turn on the Keyboard to send out a signal and once it sees it select it to be paired to the computer by typing in the 8 digit number into the wireless keyboard and hit ENTER/RETURN.
7. To see if everything was added go to Devices and Printers and see if they were added to the list.
8. Shutdown Windows 7 and Restart using Mac OSX. If you adjusted the Boot Camp settings while in Windows 7 you will see a Boot Camp icon in the system tray located at the bottom right of the screen. From here you can logoff and reboot in Mac OSX. If you don't, do a RESTART and hold the Option key down after hearing the GONG and select the Mac HD option while logging in. Now it's time to add back the wireless mouse and keyboard to be recognized by your Mac.
9. Go to System Preferences – Internet and Wireless – Bluetooth
10. Hit the “+” button to launch the Bluetooth Setup Assistant to find the devices sending out the signal.
11. Highlight the device found and hit “Continue”
12. Do this for both the keyboard and mouse. You will be prompted to type in the 8 digit code into the wireless keyboard in order to pair it with your computer.
13. Click on the pinwheel next to the “-“ sign to rename the wireless devices if you'd like.
I then logged back into Windows 7 to see if the mouse and keyboard were functional and had no problems. For some reason, Windows has problems pairing bluetooth devices that are already paired under a Mac OSX. Many people have updated Boot Camp, yet still were not able to pair their wireless devices because they didn't break the Bluetooth connection on the Mac side first. So both steps are necessary (1) Updating to at least Boot Camp 3.1 if not 3.2 and (2) Deleting the Wireless mouse and keyboard link while running Mac OSX before trying to pair them in a Windows OS.

I found the answers by trial and errors.
@ is obtained by CTRL + OPT + 2
# is obtained by CTRL + OPT + 3
(without shift or caps lock)
These two signs are critical and I fail to understand why this information is not readily available from the help function or from the Apple support.
Jean-Philippe

PSE 13 Organiser and apple magic mouse - unusable

Just bought PSE 13 and to my dissapointment discover that scrolling within the organiser is so erratic that its near impossible to select two photos and then stack them.
In addition the slightest touch seems to send the media window shooting off in random directions.
I see from other comments this problem seems to have been around for several versions of PSE. I had v10 before and didn't notice this but had to upgrade for the 5k iMac.
Come on adobe... sort it out.

Thanks don_mayer, I really thought about upgrading my PSE10 to PS12 to fix the scrolling issue.
Your post saved me some money.
@adobe: it would be nice to know, if this problem is planned to be fixed in a future release of PSE. It is NOT linked to the specific "Magic Mouse" from Apple. On OSX Mavericks, scrolling is nearly unusable in the photo browser in PSE no matter which type of mouse is connected to the Mac.
After reading through all the posts in this forum, I haven't solved this problem yet. Also a Logitech mouse (as recommend in one of the posts) did not fix this.
PSE is the only application, I know of on Mac, that seems to have this problem.

PC and MBP keyboard/mouse switch

I got a MS natural keyboard as well as Logitech thumb-ball mouse that I use often with my PC. When I put the MBP on the desk, I'm constantly switching to the MS Natural KB and Logitech Mouse and thought if there's such KVM device that will handle only USB based keyboard and mouse? No videos switch is needed, since I do like having two screens.
I don't know if the Dlink KVM devices will work that way, will it?
Thanks.

I may be wrong, but I was under the impression that BT devices can only be 'actively' paired with one device at a time. It may be that the mouse works because it sees the host system as a generic device, while the keyboard doesn't because it requires a unique driver. Regrettably I can't test this because I gave up trying to use BT mice and keyboards a while back due to interference problems, but thought I'd throw that thought in to at least prevent your question being left dangling!
It might be that the KVM is the culprit, and that a different one would work better. You might be able to test that by removing the KVM from the keyboard/mouse connection altogether. Since the mini has BT already, plug the BT dongle directly into the PC and see if you can pair with both systems at the same time. I suspect you won't be able to, but at least that'll remove the KVM from consideration as the culprit.

After updated software on mac mini with os x 10.7.5 and restart the mouse pointer after about 30 sec. converted to the rainbow wheel and I can't control the computer.

After updated software on mac mini with os x 10.7.5 and restart the mouse pointer after about 30 sec. converted to the rainbow wheel and I can't control the computer. The rainbow wheel was runnig 8 hrs and I turn off mac mini by power button, then I turn on mac mini with key Shift and p/w, checked HD. My HD has
capacity 499.25 GB used 86.91GB. Is there a solution to fix this problem axcept the reinstall os?

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.
These steps are to be taken while booted in safe mode.
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
Step 1
Triple-click the line of text below to select it:
for k in /Sy*/L*/Ex*/{,.?}*.kext; do test -f "$k/Contents/Info.plist" && /usr/libexec/PlistBuddy -c "Print :CFBundleIdentifier" "$_" | egrep -qv "apple|Accusys|ArcMSR|ATTO|CalDigit|HighPoint|hp-fax|JMicron|print|SoftRAID|stex" && echo $k; done | open -f -a TextEdit
Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. Post the contents of that window, if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
Step 2
Repeat with this line:
sudo defaults read com.apple.loginwindow LoginHook | open -f -a TextEdit
This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.
Step 3
Repeat with this line:
ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null | open -f -a TextEdit
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.
Step 4
osascript -e 'tell application "System Events" to get name of every login item' 2> /dev/null | open -f -a TextEdit
Remember, Steps 1-4 are all copy-and-paste — no typing, except your password. Also remember to post the output.
You can then quit Terminal.

2008 Mac Pro, Lion, and a flaky mouse?

For some reason, shortly after upgrading to Mac OS X Lion, my 2008 Mac Pro has developed intermitent problems with my Logitech Desktop Wave mouse. The problem seems primarily associated with the left mouse button and includes problems selecting files and highlighting text, problems dragging, random double-clicks, and general weirdness.
Here's what I've done so far:
Replaced the mouse batteries
Updated to the latest version of the Logitech Control Center (3.5.1-23)
Checked the system preferences for Mouse, Universal Access, and the Logitech Control Center
Reset the PRAM
Restarted the MacPro
Nothing works. I even substituted my existing Logitech mouse for another one and the problem remains. This has gotten to the point where it's driving me absolutely batty. The only thing that I haven't checked is the PRAM battery inside my MacPro, which is about 4 years old, but I'm not having any problems with the date and time resetting, which is usually indicative of a failing PRAM battery. Please help me save my sanity.
Thanks,
Kelly

At idle, kernel_task is running at .3-.5%, but disconnecting and reconnecting the DVI connectors didn't have any effect for me.
Plus, I'm not really having issues with jumpiness, as the user's post describes. My mouse problem has more to do with not being able to click and drag windows on the first attempt, the inability to click and drag lines of text, random double clicks instead of single clicks, and stuff like that.
However, if kernel_task is suppose to idle at 1-2%, that's clealry not happening.

F9 and F10 keys and my Logitech Mouse

Similar Messages

Maybe you are looking for