Wireless logitech keyboard - unable to set keyboard map in X.

Hi,
i have a wireless usb keyboard - logitech k360. When I restart X i always have to manually set keyboard layout using "setxkbmap pl" which is little annoying.
My laptop keyboard has polish layout set correctly. I tried to modify /etc/X11/xorg.conf.d/keyboard.conf, but cannot find the right options. Here's how it looks now:
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbModel" "logii350"
Option "XkbLayout" "pl"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
I've tried to remove option XkbModel, tried to set it to pc105 and now it is set to logii350 (I've searched through the /usr/share/X11/xkb/rules/ to find my exact keyboard model but it isn't there).
Funny thing is, that when I type some polish character at my laptop keyboard, suddenly wireless keyboard gets good layout.
Any thoughts?

Is this one with the Logitech Unifying Device receiver?
There are a few threads on this forum about it defaulting to the default QWERTY layout (hell, I have an AZERTY layout - not just as a locale, the key prints are AZERTY). It seems to be some udev bug.

Similar Messages

Will both ipad mini and wireless Logitech keyboard fit In the Logitech case that opens like a book?

I have an ipad mini and the wireless Logitech keyboard and I want to know if the Logitech case will fit both my ipad and the keyboard ?

Hi emsiecat,
Here is an article that will explain some Bluetooth troubleshooting steps for you:
iOS: Troubleshooting Bluetooth connections
http://support.apple.com/kb/TS4562
You may also want to check your manual for the keyboard for further troubleshooting steps. Thanks for coming to the Apple Support Communities!
Regards,
Braden

Wireless Logitech keyboard

If anybody has a positive experience of compatibility the K800 wireless Logitech keyboard with MAC OS X Version 10.7.3?
I connected the KB to Mac mini with "Unifing" (Logitech) software installed, but I do not have full functionality: I have no NumPad working. Some of keys respond not correctly. For example, there is no "point" key at the Russian layout.
I asked Logitech support for the driver and they told: "All Logitech products works on standard OS drivers and if you have any problems with it it is better to contact Apple..."
Below - my correspondence with the Logitech support:
Logitech 02/28/2012 10:35 AM Dear Aeksei Thank you for contacting Logitech's Customer Care. Sorry, but no one has experience K800 on the MAC OS X Version 10.7.3 Best advise to you is to contact apple. They might help you with drivers.   Kind Regards Denis M. Logitech Customer Care - Asia-Pacific
Aleksei Pariy     02/27/2012 08:47 PM Thank you for the prompt reply. First of all, I want to assure you that the keyboard itself is working. It works without any problems in Windows 7. Mac Mini also properly functioning, I believe. It had been just bought and tested true. But, the keyboard in Mac OS X ... When I try to change the keyboard type, system reports that the keyboard should be identified and invites to press the key, right to "left shift" key. Then the system prompts to select the keyboard type of the three options:
- ISO European
- ANSI U.S.
- JIS Japan
None of these options lets work NumPad. I have no NumPad working. Some of keys respond not correctly. For example, there is no "point" key at the Russian layout. Please let me know if anybody has a positive experience with the K800 an the MAC OS X Version 10.7.3?
Logitech 02/27/2012 03:38 PM Dear Aeksei Thank you for contacting Logitech's Customer Care. You can use your keyboard on Mac. Only we do not have Software for it, but it should work without any s/w. All Logitech products works on standard OS drivers and if you have any problems with it it is better to contact Apple of Microsoft. To test keyboard you can try it on different PC and if problem stays - it is hardware, if not - software.   Kind Regards Denis M. Logitech Customer Care - Asia-Pacific
Aleksei Pariy     02/26/2012 10:50 AM Could I use Your K800 keyboard with Mac Mini (OS X Lion) and Unifing software installed? I use it, but not complete functionality. Could You indicate me the driver.

I have tried advice of Klaus1at http://bit.ly/wgi53h
Unfortunately it does not help. Logitech Control Centre says: No Logitech Device Found. The KB and Logitech mouse are possible to be controled only thpough Unifing software.

Wireless Logitech keyboard won't work

Hi guys,
I have a wireless Logitech diNovo edge keyboard that used to work fine. A few months ago it stopped working and I never bothered to look at it. The keyboard works fine in other PCs running Windows. When I plug it into the Archlinux box the keyboard never synchs to the bluetooth dongle (just blinks).
This is what happens when I plug the keyboard in (NOVATEK is a wired USB keyboard):
dmesg
[ 51.878109] usb 4-2: USB disconnect, device number 2
[ 55.840026] usb 4-2: new full-speed USB device number 4 using ohci_hcd
[ 56.045166] hub 4-2:1.0: USB hub found
[ 56.048080] hub 4-2:1.0: 3 ports detected
[ 56.345080] usb 4-2.2: new full-speed USB device number 5 using ohci_hcd
[ 56.479450] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11
[ 56.479739] generic-usb 0003:046D:C713.0004: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
[ 56.548115] usb 4-2.3: new full-speed USB device number 6 using ohci_hcd
[ 56.703434] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12
[ 56.704162] logitech 0003:046D:C714.0005: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
[ 56.948094] usb 4-2.1: new full-speed USB device number 7 using ohci_hcd
[ 57.089411] Bluetooth: Core ver 2.16
[ 57.090507] NET: Registered protocol family 31
[ 57.090518] Bluetooth: HCI device and connection manager initialized
[ 57.090529] Bluetooth: HCI socket layer initialized
[ 57.090535] Bluetooth: L2CAP socket layer initialized
[ 57.090563] Bluetooth: SCO socket layer initialized
[ 57.093514] usbcore: registered new interface driver btusb
[ 90.226597] usb 4-2: USB disconnect, device number 4
[ 90.226605] usb 4-2.1: USB disconnect, device number 7
[ 90.227663] usb 4-2.2: USB disconnect, device number 5
[ 90.283551] usb 4-2.3: USB disconnect, device number 6
[ 93.210021] usb 4-2: new full-speed USB device number 8 using ohci_hcd
[ 93.415200] hub 4-2:1.0: USB hub found
[ 93.418081] hub 4-2:1.0: 3 ports detected
[ 93.715081] usb 4-2.2: new full-speed USB device number 9 using ohci_hcd
[ 93.849470] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13
[ 93.849808] generic-usb 0003:046D:C713.0006: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
[ 93.918121] usb 4-2.3: new full-speed USB device number 10 using ohci_hcd
[ 94.057378] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14
[ 94.058052] logitech 0003:046D:C714.0007: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
[ 94.291136] usb 4-2.1: new full-speed USB device number 11 using ohci_hcd
[ 96.400094] usb 4-2: USB disconnect, device number 8
[ 96.400102] usb 4-2.1: USB disconnect, device number 11
[ 96.402936] usb 4-2.2: USB disconnect, device number 9
[ 96.460224] usb 4-2.3: USB disconnect, device number 10
[ 99.843366] usb 4-2: new low-speed USB device number 12 using ohci_hcd
[ 100.047501] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15
[ 100.047781] generic-usb 0003:0603:00F2.0008: input,hidraw0: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input0
[ 100.060244] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16
[ 100.060670] generic-usb 0003:0603:00F2.0009: input,hiddev0,hidraw1: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input1
See here for udev events.
Xorg log:
[ 56.500] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
[ 56.500] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 56.500] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 56.500] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 56.500] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
[ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
[ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 56.501] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 56.501] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11/event2"
[ 56.501] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
[ 56.501] (**) Option "xkb_rules" "evdev"
[ 56.501] (**) Option "xkb_model" "evdev"
[ 56.501] (**) Option "xkb_layout" "us"
[ 56.720] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
[ 56.720] (II) No input driver specified, ignoring this device.
[ 56.720] (II) This device may have been added with another device file.
[ 56.721] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
[ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
[ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 56.721] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 56.721] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 56.721] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
[ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
[ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
[ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
[ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 56.722] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12/event3"
[ 56.722] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
[ 56.722] (**) Option "xkb_rules" "evdev"
[ 56.722] (**) Option "xkb_model" "evdev"
[ 56.722] (**) Option "xkb_layout" "us"
[ 56.723] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
[ 56.723] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
[ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
[ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
[ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
[ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
[ 90.266] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 90.267] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 90.267] (II) UnloadModule: "evdev"
[ 90.363] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 90.364] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 90.364] (II) UnloadModule: "evdev"
[ 93.870] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
[ 93.870] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 93.870] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 93.871] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 93.871] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
[ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
[ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 93.871] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 93.871] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13/event2"
[ 93.871] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
[ 93.871] (**) Option "xkb_rules" "evdev"
[ 93.871] (**) Option "xkb_model" "evdev"
[ 93.871] (**) Option "xkb_layout" "us"
[ 94.083] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
[ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
[ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 94.083] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 94.084] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 94.084] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
[ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
[ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 94.090] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14/event3"
[ 94.090] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
[ 94.090] (**) Option "xkb_rules" "evdev"
[ 94.091] (**) Option "xkb_model" "evdev"
[ 94.091] (**) Option "xkb_layout" "us"
[ 94.091] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
[ 94.091] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
[ 94.094] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
[ 94.094] (II) No input driver specified, ignoring this device.
[ 94.094] (II) This device may have been added with another device file.
[ 96.443] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 96.444] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 96.444] (II) UnloadModule: "evdev"
[ 96.536] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 96.537] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 96.538] (II) UnloadModule: "evdev"
[ 100.084] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event3)
[ 100.084] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 100.084] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
[ 100.084] (**) NOVATEK USB Keyboard: always reports core events
[ 100.084] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event3"
[ 100.084] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
[ 100.084] (--) evdev: NOVATEK USB Keyboard: Found 20 mouse buttons
[ 100.084] (--) evdev: NOVATEK USB Keyboard: Found keys
[ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as mouse
[ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
[ 100.085] (**) evdev: NOVATEK USB Keyboard: YAxisMapping: buttons 4 and 5
[ 100.085] (**) evdev: NOVATEK USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 100.085] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16/event3"
[ 100.085] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 8)
[ 100.085] (**) Option "xkb_rules" "evdev"
[ 100.085] (**) Option "xkb_model" "evdev"
[ 100.085] (**) Option "xkb_layout" "us"
[ 100.087] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event2)
[ 100.088] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 100.088] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
[ 100.088] (**) NOVATEK USB Keyboard: always reports core events
[ 100.088] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event2"
[ 100.088] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
[ 100.088] (--) evdev: NOVATEK USB Keyboard: Found keys
[ 100.088] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
[ 100.088] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15/event2"
[ 100.088] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 9)
[ 100.088] (**) Option "xkb_rules" "evdev"
[ 100.088] (**) Option "xkb_model" "evdev"
[ 100.088] (**) Option "xkb_layout" "us"
Anyone have a clue what's wrong? Thanks,

Splex wrote:
I also prefer to not run the dongle in bluetooth mode... it causes so many headaches.
There may be a better way to disable the bluetooth mode, but you can comment out the 'Logitech devices' rule in /usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules:
# Logitech devices
#KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
# RUN+="hid2hci --method=logitech-hid --devpath=%p"
Once you save the changes, simply replug your dongle, hit the connect buttons and it should work as if it is wired.
Whenever udev is upgraded, the rule file will be overwritten... you can add this to your /etc/pacman.conf to prevent it from being overwritten:
NoUpgrade = usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules
If anyone knows of a better way to prevent the default udev rules from switching the dongle to HCI mode, please speak up
Just tried this, didn't work for me :-/
grr.

Wireless Headset Pro - Unable to set application settings

Just got my Wireless Headset Pro. Paired it to my Xperia Arc S (running ICS, all bog standard, not rooted). Prompted to Install Smart Wireless Headset Pro plugin for LiveWare Manager, installed OK. Click on Smart Wireless Headset Pro from LiveWare Manage, click 'Applications and Settings', click 'Applications.' I then choose each application in turn and click to install - Calendar Remider, Messaging etc (go to Google Play Store and click the 'Install' button). All Applications installed correctly. Click again on any application (e.g. Messaging - Smart Extras) to change settings and get taken back to the Google Play Store to install the app again! The only option in the Google Play Store is the 'Uninstall' button.
Even through I've installed all the smart extra applications, they are not being recognised as installed by the LiveWare Manager plugin. The status of each Application in the Wireless Headset Pro LiveWare Manager says 'Download and Install'. They are showing as installed to the phone memory under the phone Settings>>Apps.
I have tried restarted the phone and the Wireless Headset Pro several times. Also tried resetting the WHP and re-pairing. No difference.
Anyone else found this?

You could try to clear data for the LiveWare app. If that doesn't help I think that you will to try to repair your phone software via PC Companion.
http://www.sonymobile.com/gb/tools/pc-companion/
Let me know if this problem remains.
- Community Manager Sony Xperia Support Forum
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page.

PRINT SCREEN WITH A LOGITECH KEYBOARD

CAN YOU PLEASE HELP ME I BOUGHT THIS WIRELESS LOGITECH KEYBOARD AND PAIRED IT WITH MY MAC DESKTOP COMPUTER. AM TRYING TO PRINTSCREEN BUT IT DOES NOT WANT TO. CAN ANYONE PLEASE HELP ME WITH THIS? THANK YOU!

Press the Shift, Command, and 3 keys to capture the whole screen.
Press the Shift, Command, and 4 keys to capture a draggable part of the screen, or follow it with the spacebar to capture a window.
Open the PNG on the desktop. Alternatively, combine either of the above with the Control key to put the screenshot onto the clipboard instead of the desktop.
(124233)

Wireless keyboard mapping is not same as printed on Leopard and MacMini

Hi ...
I bought MacMini and Wireless Keyboard.
when I type, the character that shows are not same like it`s printed
This is what I type+
Keyboard Mapping
~!”#$%&’()0=~
`1234567890-^
QWERTYUIOP`{}
qwertyuiop@[]
ASDFGHJKL+*
Asdfghjkl;:
ZXCVBNM<>?
zxcvbnm,./
If you have a Mac Keyboard, what ever it is, it will show different character as I type above, mostly on the special character.
Can someone help me on this?
Thank you and regads,
Faizal A.-

Hi Tom,
Thanks for identifying the issue.
I am trying to follow that article, here is the result:
/System/Library/CoreServices/KeyboardSetupAssistant.app/Contents/MacOS/KeyboardS etupAssistant ; exit;
2012-02-07 07:22:42.702 KeyboardSetupAssistant[491:507] No unknown keyboard connected - terminating
logout
[Process completed]

[SOLVED]Setting x11 keyboard map PERMANENTLY for all.

Read carefully through https://wiki.archlinux.org/index.php/Ke … on_in_Xorg.
Ran 'localectl set-x11-keymap gb' as instructed. Confirmed this creates: /etc/X11/xorg.conf.d/00-keyboard.conf
Ran 'grep "config directory" /var/log/Xorg.0.log' which confirms that this /etc/X11/xorg.conf.d is where it's looking.
Ran 'grep "xkb" /var/log/Xorg.0.log' which confirms that 'Option "xkb_layout "gb"' is the ONLY one found. (it appears several times).
But setxkbmap -print -verbose 10 shows xkb_symbols { include "pc+us+inet(evdev" }
and the keyboard map is STILL 'us'. @=" etc...
Reread the wiki, still don't understand.
Typing 'setxlbmap gb' into a terminal works for the session.
Adding that to .xinitrc before the window manager command has NO effect.
I tried adding the option to 10-evdev.conf, but that doesn't do it.
So HOW DO you set the damn thing permanently? Clearly evdev is not logging what it is doing in Xorg.0.log, so where is it logging?
Something seems to have changed since the wiki article was written.
TOF
Last edited by TheOldFellow (2013-11-25 14:58:29)

Sorry for the noise. The Window Manager (Cinnamon) is changing it!
TOF

Logitech wireless solar keyboard K750 for MAC OSX OS 10x8x

is the logitech wireless solar keyboard K750 an acceptable paring choice for the MAC OS X Mountain Lion OS 10x8x

You have the MacBookPro6,2, the Edsel of Macs. It may be covered by this program:
MacBook Pro (15-inch, Mid 2010): Intermittent black screen or loss of video
Make a "Genius" appointment at an Apple Store to have the machine tested. The routine hardware diagnostics used by service providers may not detect the fault. There is a specific test for this issue.
Print the first page of the panic report, and the support page linked above, and bring them with you.
Note that the replacement program only applies within three years of purchase. If you wait beyond that date, Apple may refuse the service.
Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
*An SSD doesn't need to be zeroed.
You may be able to stop the panics by disabling automatic graphics switching in the Energy Saver preference pane, but that's not a solution.
Most likely, the logic board will be replaced. Sometimes the replacement part is also defective, so be prepared for that possibility.

My wireless Apple keyboard won't connect, it just keeps blinking to pair, but nothing connects. I even tried hooking up another wireless I have and it does the same thing. Should I delete it and set it up again?

My wireless Apple keyboard won't connect, it just keeps blinking to pair, but nothing connects. I even tried hooking up another wireless I have and it does the same thing. Should I delete it and set it up again?

Hey Apple Health,
Welcome to Apple Support Communities! There's an article that helps to resolve issues with wireless keyboards. I'd take a look at it, go through the troubleshooting steps, and see if that resolves the issue for you:
Troubleshooting wireless mouse and keyboard issues
http://support.apple.com/kb/TS3048
Best,
David

Keyboard Mapping Incorrectly at Bootup - not consistent

Not sure if I'm posting this in the right place, but here goes.
I have 2 users that both have 15" G4 Powerbooks with OS X 10.4.6 loaded on them. They're using a standard image that's used for all our computers. So far we have have never seen this particular problem until last week.
Occasionally on bootup the keyboard maps incorrectly. The systems are set to boot to a login screen which the user cannot authenticate with as the incorrect letters are being typed. This has only occurred while they were offsite and using airport so I have been unable to verify the keystrokes. The only mapping they remember was that the "L" key mapped to one of the volume keys and "delete" (as in backspace) mapped to an elongated parenthesis, but they weren't more specific than that. I've since re-imaged a third machine with the same specs and swapped with one of the afflicted powerbooks but have been unable to replicate the problem.
I've checked the International preferences and he's set to a U.S. keyboard with nothing else selected. Verified and repaired permissions. Checked his fonts.
Has anyone ever seen this? I'm completely stumped.

Sounds to me like one of your Shift keys is stuck--holding down the Shift key while starting the computer puts it into "safe mode."
Might be easiest to bring the machine in and have a tech take a look.
~Lyssa

Non-wireless backlit keyboard

Looking for a non-wireless backlit keyboard. Have done lots of searching online and in forums but finding very little useful info. Anyone have one that they really like?
Thanks.

I tried a few shortcuts that make use of the "control" key on the Mac, and the Logitech keyboard's CRTL key works just fine. Examples:
Control+mouse click = right click
Control-Command-Up Arrow = "Open enclosed folder in a new window"
The dedicated "Windows" key performs the "command" function just fine as you'd expect.
The only thing I haven't tried is getting the Logitech's F1-F12 keys to map to the respective functions on the MacBook's built in keyboard, namely brightness adjustment, keyboard backlight adjustment (as useful as that could be in this case anyway), volume, and eject. I should note thought that for volume/mute the dedicated Logitech keys on the right side work just fine without any tinkering, and for the rest (Exposé/Spaces/Dashboard) you can just map the F key directly to trigger them.
Hope this helps!

Wireless Aluminum Keyboard Troubleshooting

If you're having issues with your Apple Wireless (Aluminum) Keyboard disconnecting, there are a few things you can try.
First, check your wireless network configuration to see if you can avoid interference. See this post in another topic:
http://discussions.apple.com/message.jspa?messageID=5783742#5783742
Although I did have success with tweaking my wifi setup, my keyboard disconnect problem returned again a couple of weeks ago. I had recently upgraded to Leopard (10.5.1) which may have contributed - although I had been using wired ethernet, and switched back to wifi around the same time as my Leopard upgrade.
Like others have posted, I also noticed the bluetooth daemon log errors in my system log. To look for them, you can open console.app, and search for "blued" in the system.log and also its archive history. Here's an example:
+Jan 25 09:17:22 Macintosh-2 kernel[0]: IOBluetoothHCIRequest::Create [0x55da000] Request OpCode 0000 Generated by: blued (47) status: 0 timeout 1000. has a too small timeout, a reasonable value would be 5000 (5 seconds)+
Here are some other things to try. You should only try one at a time - so that you can tell which change fixed your problem.
1. In the Bluetooth System Preferences panel, unpair your keyboard, and re-pair it again
2. Also in the Bluetooth System Preferences panel, add the keyboard to your favorites. To do this in Leopard: select the keyboard in the bluetooth devices list. Click on the tasks cog at the foot of that pane (just beside the plus and minus). Select "Show more info". Select "Add To Favorites".
3. Reset the bluetooth preferences by moving system preference files. Warning: only try this if you are comfortable using the OS X terminal!! :
sudo mv /var/root/Library/Preferences/blued.plist /var/root/Library/Preferences/blued.plist.old
sudo mv /var/root/Library/Preferences/com.apple.Bluetooth.plist /var/root/Library/Preferences/com.apple.Bluetooth.plist.old
(you will need to enter your password at least once, and then will need to restart your machine).
Keep a log of all the things you've tried. If none of these work, its probably time to call AppleCare. If you have one of the new Apple (Aluminum) Wireless Keyboards, it is still covered by warranty at this point.

It sounds like the bluetooth in both of your keyboards has simply died. If it's still under warranty (if it has one), take it to the apple store and show them. They may give you a new one. For future reference, the new wired USB keyboard is now exactly the same as the wireless (except that it has a wire), and you won't face any bluetooth issues like that. You can get the new wired keyboard here:
http://store.apple.com/us/product/MB869LL/A?fnode=MTY1NDA1Mg&mco=NDE4NjI4Mg
Also, if you're willing to spend a bit more money, Macworld rated the Logitech DiNovo Edge Keyboard very highly. Here's a link to that:
http://store.apple.com/us/product/TU938LL/A?fnode=MTY1NDA1Mg&mco=MjgzMTkxNA
Hope this helps.

_Is there a way to make custom keyboard mapping a default?

_Is there a way to make custom keyboard mapping a default?
What I mean is, for example, I want to disable <command> S for saving (so I don't accidentally hit it).
Thanks!
Hugh

Edit>Keyboard Shortcuts Make the changes you want to the shortcuts and save with a new name. In the dropdown at the top choose your new set and close. Quit and restart to seal the deal.

Help with very slow connection if apple tv linked to wireless apple keyboard

My husband and I trying to connect the wireless Apple keyboard to our Apple tv so we can get rid of the pesky and cumbersome Apple tv clicker. However, when we do so, our connection slows to a crawl and we cannot access sites like Netflix et al. We disconnected Bluetooth from our Mac Book Pro as we noticed that the keyboard serves only one master. This did not fix the problem. We are at our wits' end. Your help would be immensely appreciated.
Oh, and also, I had been thinking of installing AirPort Utilty. Is this a good idea and why do I not see it in the AppStore, only on websites of dubious provenance?
Thousand thanks,
J and F
Er, and while we're at it, why do we need to choose between my apple address and my husband's when we set up homesharing? This is another clunky thing that simply is opaque.

However, when we do so, our connection slows to a crawl and we cannot access sites like Netflix et al.
Not caused by the keyboard. It connects via BluTooth, the video services over eithernet. They have nothing to do with one another. There is something else going on. Have you tried connecting ATV via a wired connection instead of WiFi.
why do we need to choose between my apple address and my husband's when we set up homesharing?
Because you can only use one AppleId. It would be a huge leagal mess if it displayed content from multiple accounts at the same time. The copyright holders would never allow it.

Wireless logitech keyboard - unable to set keyboard map in X.

Similar Messages

Maybe you are looking for