Change ctrl + alt + s

I've searche all over the internet to try to change the shortcut ctrl + alt + s, and when i play games, it tabbs me out so i lose...
I have a "HP Pavilion 17 notebook PC"
Product number:F8T46EA#UUW
cant find the Model number

I am using a Razer Black Widdow Elite 2013 and the shortcut still works...

Similar Messages

Change Ctrl+Alt+Backspace to something else

Hi
Is there any way to change the Ctrl+Alt+Backspace key combination in X to something else, e.g. Ctrl+Alt+Windows+Backspace?
Note that I don't want to disable the "zapping" behavior by changing DontZap, but simply change the combination.

This _looks_ like it, but doesn't really make a lot of sense:
xmodmap -pke | grep BackSpace
keycode 22 = BackSpace Terminate_Server BackSpace Terminate_Server BackSpace Terminate_Server
The first keysym is used when no modifier key is pressed in conjunction with this key, the second with Shift, the third when the Mode_switch key is used with this key and the fourth when both the Mode_switch and Shift keys are used. The last four are not used in any major X server implementation.

Change ctrl+alt+s System Information keyboard shortcut

Hello,
since last HP update, there is this new keyboard shortcut CTRL+ALT+S that opens the System Information panel. That shortcut is also used by other applications i.e. Adobe Photoshop. How can i change/disable that shortcut?
My OS is windows 8.1.
I've already unsuccessfully tried the steps described in the document http://h10025.www1.hp.com/ewfrf/wc/document?cc=it&lc=it&dlc=it&docname=c00761879. It does not work for me because I have windows 8.1 and there is no such program as "HP Help and Tools".
Thanks

Use Windows System Restore to return to a checkpoint made on the date of the update. Each checkpoint will list details on the update that it was made for.
Use system restore, not Refresh or reset.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Revolve 810 G1 Unlock Computer when in Tablet Mode. Press CTRL-ALT-DEL or Windows Security Button

1. I have an Revolve 810 G1
Running Windows 7 Pro (64 Bit).
When I change the screen to Tablet Mode
(Folding tablet over keyboard and using as tablet).
I lock my computer.
2. What to know how to unlock without having to Open back up and use the CTL-Alt-DEL keys.
When Locked screen shows: Press CTRL-ALT-DEL or use the Windows Security Button to unlock this computer.
I would like to use the Windows Button on the bottom of the screen
(One Used in Windows 8 to change between Desktop and Metro) to Unlock screen And bring up on screen keyboard to put in my password.
This is probably how it should work, but it does not work.
Even bringing up the onscreen keyboard via the blue power button On the screen to Ease Of Access does not work.
The CLT-ALT-DEL on the on screen keyboard will not unlock the screen.
P.S.
Where is that Windows Security Button when you need it?
Thanks,
Rog

If you are using Windows 7 (not Windows 8), you should be able to touch the Ease of Access button at the lower left of the screen, then select Type without the keyboard (On-screen keyboard). When the on-screen keyboard pops-up, press CTRL, then ALT, then DEL. You should get a password prompt; the on-screen keyboard will stay visible unless and until you close it.
Although I am an HP employee, I am speaking for myself and not for HP.
Please click the little thumbs-up dealybopper to the lower right if my reply was helpful to you. Please mark Accept As Solution if it solves your problem. This will help others, too!

Ctrl Alt Del and Task manager not working

Hi, Ive been having a problem getting task manager to run at all. On a fresh reboot, if I use the ctrl alt del function the according screen will come up like normal, and I will click on task manager. It bring me back to my desktop and nothing pops up.
Its not running in my task bar or anything. Then if I try to use the ctrl alt del function again, nothing happens. Ive tried running task manager straight from the start menu, but then I get an error saying that the version of that file is not compatible with
the version of windows I am running, which is 64 bit W7. It just started happening on my system a few days ago and I have changed nothing the past few days. I have tried to do a system restore, but to my idiocy, I did not know I needed to manually create restore
points. So I can only restore to yesterday which would fix nothing. I have run antivirus and anti spyware programs and they have shown no problems and my hard drive only has a 1% disk fragmentation. Is there a way to uninstall and re download a 64 bit compatible
version of the windows 7 task manager? Or is there a separate reason why it is not working? Thankyou

Also try it By Registry Editor :
Start --> Run --> regedit --> ok
Then
Hive: HKEY_CURRENT_USER
Key: Software\Microsoft\Windows\CurrentVersion\Policies\System
Name: DisableTaskMgr
Type: REG_DWORD
Value: 0=Disablethis key, that is Don't Disable, Enable TaskManager
Regards,
MCP | MCTS | MCITP
The first fix did not work, I tried doing the second one but there is no system folder in
Software\Microsoft\Windows\CurrentVersion\Policies\
The only one its showing is an explorer folder.

Can't switch VT's with Ctrl+Alt+Fx or Ctrl+Alt+backspace terminate

Ctrl+Alt+F2 doesn't seem to register. It's been a long term issue I have had for years. I've tried all the various fixes.
I can manually change to virtual terminals without issues using:
sudo chvt 2
Once I'm in a VT I can use Alt+Fx to change between them, until I go back into Xorg. So it's unlikely to be a graphics driver problem, most other people with similar issues complain of getting a blank screen.
Although without sudo I get
# chvt 2
Couldn't get a file descriptor referring to the console.
I have the following in /etc/X11/xorg.conf.d/15-forcevt.conf
Section "ServerFlags"
Option "HandleSpecialKeys" "always"
Option "DontVTSwitch" "false"
Option "DontZap" "false"
EndSection
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
A also enabled the terminate option in gnome-tweak-tool.
xmodmap -pke has the following:
keycode 67 = F1 F1 F1 F1 F1 F1 XF86Switch_VT_1
keycode 68 = F2 F2 F2 F2 F2 F2 XF86Switch_VT_2
Nothing is printed in Xorg logs when I try pushing the keys.
I'm using SLIM (although I tried manually via startx), AwesomeWM (also tried fluxbox with a blank conf), nvidia (proprietary), UEFI.
[ 2490.220]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 2490.225] X Protocol Version 11, Revision 0
[ 2490.227] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 2490.229] Current Operating System: Linux ender 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64
[ 2490.229] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ff84efeb-e43f-47fe-a14d-07894feb0013 rw rootflags=subvol=@ quiet
[ 2490.233] Build Date: 14 March 2015 06:45:50PM
[ 2490.234]
[ 2490.236] Current version of pixman: 0.32.6
[ 2490.240] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2490.240] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2490.247] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 1 10:44:03 2015
[ 2490.249] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2490.250] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2490.250] (==) ServerLayout "Layout0"
[ 2490.250] (**) |-->Screen "Screen0" (0)
[ 2490.250] (**) | |-->Monitor "Monitor0"
[ 2490.251] (**) | |-->Device "Device0"
[ 2490.251] (**) |-->Input Device "Keyboard0"
[ 2490.251] (**) |-->Input Device "Mouse0"
[ 2490.251] (**) Option "DontVTSwitch" "false"
[ 2490.251] (**) Option "DontZap" "false"
[ 2490.251] (**) Option "Xinerama" "0"
[ 2490.251] (==) Automatically adding devices
[ 2490.251] (==) Automatically enabling devices
[ 2490.251] (==) Automatically adding GPU devices
[ 2490.251] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2490.251] Entry deleted from font path.
[ 2490.251] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2490.251] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2490.251] Entry deleted from font path.
[ 2490.251] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2490.251] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 2490.251] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2490.251] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2490.251] (WW) Disabling Keyboard0
[ 2490.251] (WW) Disabling Mouse0
[ 2490.251] (II) Loader magic: 0x815d80
[ 2490.251] (II) Module ABI versions:
[ 2490.251] X.Org ANSI C Emulation: 0.4
[ 2490.251] X.Org Video Driver: 19.0
[ 2490.251] X.Org XInput driver : 21.0
[ 2490.251] X.Org Server Extension : 9.0
[ 2490.254] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 2490.254] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2490.254] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 2490.258] (--) PCI:*(0:1:0:0) 10de:1180:10de:0969 rev 161, Mem @ 0xfa000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 2490.258] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2490.258] (II) LoadModule: "glx"
[ 2490.258] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2490.268] (II) Module glx: vendor="NVIDIA Corporation"
[ 2490.268] compiled for 4.0.2, module version = 1.0.0
[ 2490.268] Module class: X.Org Server Extension
[ 2490.268] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 2490.268] (II) LoadModule: "nvidia"
[ 2490.268] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2490.269] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2490.269] compiled for 4.0.2, module version = 1.0.0
[ 2490.269] Module class: X.Org Video Driver
[ 2490.269] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 2490.269] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2490.269] (++) using VT number 1
[ 2490.269] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 2490.269] (II) Loading sub module "fb"
[ 2490.269] (II) LoadModule: "fb"
[ 2490.269] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2490.269] (II) Module fb: vendor="X.Org Foundation"
[ 2490.269] compiled for 1.17.1, module version = 1.0.0
[ 2490.269] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2490.269] (II) Loading sub module "wfb"
[ 2490.269] (II) LoadModule: "wfb"
[ 2490.270] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2490.270] (II) Module wfb: vendor="X.Org Foundation"
[ 2490.270] compiled for 1.17.1, module version = 1.0.0
[ 2490.270] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2490.270] (II) Loading sub module "ramdac"
[ 2490.270] (II) LoadModule: "ramdac"
[ 2490.270] (II) Module "ramdac" already built-in
[ 2490.270] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 2490.270] (==) NVIDIA(0): RGB weight 888
[ 2490.270] (==) NVIDIA(0): Default visual is TrueColor
[ 2490.270] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2490.270] (**) NVIDIA(0): Option "Stereo" "0"
[ 2490.270] (**) NVIDIA(0): Option "SLI" "Off"
[ 2490.270] (**) NVIDIA(0): Option "MultiGPU" "Off"
[ 2490.270] (**) NVIDIA(0): Option "BaseMosaic" "off"
[ 2490.270] (**) NVIDIA(0): Stereo disabled by request
[ 2490.270] (**) NVIDIA(0): NVIDIA SLI disabled.
[ 2490.270] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[ 2490.271] (**) NVIDIA(0): Option "MetaModes" "DVI-I-1: nvidia-auto-select +1280+0, DVI-D-0: nvidia-auto-select +0+416"
[ 2490.271] (**) NVIDIA(0): Enabling 2D acceleration
[ 2490.690] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 2490.692] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 680 (GK104) at PCI:1:0:0 (GPU-0)
[ 2490.692] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 2490.692] (--) NVIDIA(0): VideoBIOS: 80.04.09.00.01
[ 2490.692] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 2490.709] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 680 at PCI:1:0:0
[ 2490.709] (--) NVIDIA(0): CRT-0
[ 2490.709] (--) NVIDIA(0): Samsung SMS27A850T (DFP-0) (boot, connected)
[ 2490.709] (--) NVIDIA(0): DFP-1
[ 2490.709] (--) NVIDIA(0): DFP-2
[ 2490.709] (--) NVIDIA(0): Samsung SyncMaster (DFP-3) (connected)
[ 2490.709] (--) NVIDIA(0): DFP-4
[ 2490.709] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): Samsung SMS27A850T (DFP-0): Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): Samsung SMS27A850T (DFP-0): 330.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): Samsung SyncMaster (DFP-3): Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-3): 330.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 2490.710] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 2490.710] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2490.710] (**) NVIDIA(0): device Samsung SMS27A850T (DFP-0) (Using EDID frequencies
[ 2490.710] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 2490.712] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2490.712] (**) NVIDIA(0): device Samsung SyncMaster (DFP-3) (Using EDID frequencies
[ 2490.712] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2490.713] (II) NVIDIA(0): Validated MetaModes:
[ 2490.713] (II) NVIDIA(0):
[ 2490.713] (II) NVIDIA(0): "DVI-I-1:nvidia-auto-select+1280+0,DVI-D-0:nvidia-auto-select+0+416"
[ 2490.713] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1440
[ 2490.742] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
[ 2490.742] (--) NVIDIA(0): option
[ 2490.742] (--) Depth 24 pixmap format is 32 bpp
[ 2490.743] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 2490.743] (II) NVIDIA: access.
[ 2490.746] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 2490.746] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 2490.746] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 2490.746] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 2490.746] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 2490.746] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 2490.746] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 2490.746] (II) NVIDIA(0): Config Options in the README.
[ 2490.761] (II) NVIDIA(0): Setting mode "DVI-I-1:nvidia-auto-select+1280+0,DVI-D-0:nvidia-auto-select+0+416"
[ 2490.853] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 2490.853] (==) NVIDIA(0): Backing store enabled
[ 2490.853] (==) NVIDIA(0): Silken mouse enabled
[ 2490.853] (**) NVIDIA(0): DPMS enabled
[ 2490.853] (II) Loading sub module "dri2"
[ 2490.853] (II) LoadModule: "dri2"
[ 2490.853] (II) Module "dri2" already built-in
[ 2490.853] (II) NVIDIA(0): [DRI2] Setup complete
[ 2490.853] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 2490.853] (--) RandR disabled
[ 2490.856] (II) Initializing extension GLX
[ 2490.856] (II) Indirect GLX disabled.(II) config/udev: Adding input device Power Button (/dev/input/event7)
[ 2490.914] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2490.914] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 2490.914] (II) LoadModule: "evdev"
[ 2490.914] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2490.914] (II) Module evdev: vendor="X.Org Foundation"
[ 2490.914] compiled for 1.17.1, module version = 2.9.2
[ 2490.914] Module class: X.Org XInput Driver
[ 2490.914] ABI class: X.Org XInput driver, version 21.0
[ 2490.915] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 30 paused 0
[ 2490.915] (II) Using input driver 'evdev' for 'Power Button'
[ 2490.915] (**) Power Button: always reports core events
[ 2490.915] (**) evdev: Power Button: Device: "/dev/input/event7"
[ 2490.915] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2490.915] (--) evdev: Power Button: Found keys
[ 2490.915] (II) evdev: Power Button: Configuring as keyboard
[ 2490.915] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input9/event7"
[ 2490.915] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 2490.915] (**) Option "xkb_rules" "evdev"
[ 2490.915] (**) Option "xkb_model" "pc104"
[ 2490.915] (**) Option "xkb_layout" "us"
[ 2490.915] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.940] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[ 2490.940] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2490.940] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 2490.941] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 31 paused 0
[ 2490.941] (II) Using input driver 'evdev' for 'Power Button'
[ 2490.941] (**) Power Button: always reports core events
[ 2490.941] (**) evdev: Power Button: Device: "/dev/input/event6"
[ 2490.941] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2490.941] (--) evdev: Power Button: Found keys
[ 2490.941] (II) evdev: Power Button: Configuring as keyboard
[ 2490.941] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input8/event6"
[ 2490.941] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 2490.941] (**) Option "xkb_rules" "evdev"
[ 2490.941] (**) Option "xkb_model" "pc104"
[ 2490.941] (**) Option "xkb_layout" "us"
[ 2490.941] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event20)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event21)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event10)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event11)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event12)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event14)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event15)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event16)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.944] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event17)
[ 2490.944] (II) No input driver specified, ignoring this device.
[ 2490.944] (II) This device may have been added with another device file.
[ 2490.944] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/event0)
[ 2490.944] (**) HID 1017:0002: Applying InputClass "evdev keyboard catchall"
[ 2490.944] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.944] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 32 paused 0
[ 2490.944] (II) Using input driver 'evdev' for 'HID 1017:0002'
[ 2490.944] (**) HID 1017:0002: always reports core events
[ 2490.944] (**) evdev: HID 1017:0002: Device: "/dev/input/event0"
[ 2490.945] (--) evdev: HID 1017:0002: Vendor 0x1017 Product 0x2
[ 2490.945] (--) evdev: HID 1017:0002: Found keys
[ 2490.945] (II) evdev: HID 1017:0002: Configuring as keyboard
[ 2490.945] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.1/0000:06:00.0/usb2/2-1/2-1:1.0/0003:1017:0002.0001/input/input2/event0"
[ 2490.945] (II) XINPUT: Adding extended input device "HID 1017:0002" (type: KEYBOARD, id 8)
[ 2490.945] (**) Option "xkb_rules" "evdev"
[ 2490.945] (**) Option "xkb_model" "pc104"
[ 2490.945] (**) Option "xkb_layout" "us"
[ 2490.945] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.945] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/event1)
[ 2490.945] (**) HID 1017:0002: Applying InputClass "evdev pointer catchall"
[ 2490.945] (**) HID 1017:0002: Applying InputClass "evdev keyboard catchall"
[ 2490.945] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.946] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 33 paused 0
[ 2490.946] (II) Using input driver 'evdev' for 'HID 1017:0002'
[ 2490.946] (**) HID 1017:0002: always reports core events
[ 2490.946] (**) evdev: HID 1017:0002: Device: "/dev/input/event1"
[ 2490.946] (--) evdev: HID 1017:0002: Vendor 0x1017 Product 0x2
[ 2490.946] (--) evdev: HID 1017:0002: Found 9 mouse buttons
[ 2490.946] (--) evdev: HID 1017:0002: Found scroll wheel(s)
[ 2490.946] (--) evdev: HID 1017:0002: Found relative axes
[ 2490.946] (--) evdev: HID 1017:0002: Found x and y relative axes
[ 2490.946] (--) evdev: HID 1017:0002: Found absolute axes
[ 2490.946] (II) evdev: HID 1017:0002: Forcing absolute x/y axes to exist.
[ 2490.946] (--) evdev: HID 1017:0002: Found keys
[ 2490.946] (II) evdev: HID 1017:0002: Configuring as mouse
[ 2490.946] (II) evdev: HID 1017:0002: Configuring as keyboard
[ 2490.946] (II) evdev: HID 1017:0002: Adding scrollwheel support
[ 2490.946] (**) evdev: HID 1017:0002: YAxisMapping: buttons 4 and 5
[ 2490.946] (**) evdev: HID 1017:0002: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.946] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.1/0000:06:00.0/usb2/2-1/2-1:1.1/0003:1017:0002.0002/input/input3/event1"
[ 2490.946] (II) XINPUT: Adding extended input device "HID 1017:0002" (type: KEYBOARD, id 9)
[ 2490.946] (**) Option "xkb_rules" "evdev"
[ 2490.946] (**) Option "xkb_model" "pc104"
[ 2490.946] (**) Option "xkb_layout" "us"
[ 2490.946] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.946] (II) evdev: HID 1017:0002: initialized for relative axes.
[ 2490.946] (WW) evdev: HID 1017:0002: ignoring absolute axes.
[ 2490.946] (**) HID 1017:0002: (accel) keeping acceleration scheme 1
[ 2490.946] (**) HID 1017:0002: (accel) acceleration profile 0
[ 2490.946] (**) HID 1017:0002: (accel) acceleration factor: 2.000
[ 2490.946] (**) HID 1017:0002: (accel) acceleration threshold: 4
[ 2490.946] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/mouse0)
[ 2490.946] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.946] (II) No input driver specified, ignoring this device.
[ 2490.947] (II) This device may have been added with another device file.
[ 2490.947] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event2)
[ 2490.947] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev pointer catchall"
[ 2490.947] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 34 paused 0
[ 2490.947] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[ 2490.947] (**) Logitech G9x Laser Mouse: always reports core events
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event2"
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found 20 mouse buttons
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found x and y relative axes
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.947] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:046D:C066.0003/input/input4/event2"
[ 2490.947] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: MOUSE, id 10)
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[ 2490.948] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/mouse1)
[ 2490.948] (II) No input driver specified, ignoring this device.
[ 2490.948] (II) This device may have been added with another device file.
[ 2490.948] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event3)
[ 2490.948] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev keyboard catchall"
[ 2490.948] (**) Logitech G9x Laser Mouse: Applying InputClass "Keyboard Defaults"
[ 2490.949] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 35 paused 0
[ 2490.949] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[ 2490.949] (**) Logitech G9x Laser Mouse: always reports core events
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event3"
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found 1 mouse buttons
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Forcing relative x/y axes to exist.
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found absolute axes
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Forcing absolute x/y axes to exist.
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found keys
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Configuring as keyboard
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.949] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:046D:C066.0004/input/input5/event3"
[ 2490.949] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: KEYBOARD, id 11)
[ 2490.949] (**) Option "xkb_rules" "evdev"
[ 2490.949] (**) Option "xkb_model" "pc104"
[ 2490.949] (**) Option "xkb_layout" "us"
[ 2490.949] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[ 2490.949] (WW) evdev: Logitech G9x Laser Mouse: ignoring absolute axes.
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[ 2490.949] (II) config/udev: Adding input device USB Keyboard (/dev/input/event4)
[ 2490.949] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2490.949] (**) USB Keyboard: Applying InputClass "Keyboard Defaults"
[ 2490.950] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 36 paused 0
[ 2490.950] (II) Using input driver 'evdev' for 'USB Keyboard'
[ 2490.950] (**) USB Keyboard: always reports core events
[ 2490.950] (**) evdev: USB Keyboard: Device: "/dev/input/event4"
[ 2490.950] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x274
[ 2490.950] (--) evdev: USB Keyboard: Found keys
[ 2490.950] (II) evdev: USB Keyboard: Configuring as keyboard
[ 2490.950] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.4/5-1.4:1.0/0003:04D9:0274.0005/input/input6/event4"
[ 2490.950] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 12)
[ 2490.950] (**) Option "xkb_rules" "evdev"
[ 2490.950] (**) Option "xkb_model" "pc104"
[ 2490.950] (**) Option "xkb_layout" "us"
[ 2490.950] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.951] (II) config/udev: Adding input device USB Keyboard (/dev/input/event5)
[ 2490.951] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2490.951] (**) USB Keyboard: Applying InputClass "Keyboard Defaults"
[ 2490.951] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 37 paused 0
[ 2490.951] (II) Using input driver 'evdev' for 'USB Keyboard'
[ 2490.951] (**) USB Keyboard: always reports core events
[ 2490.951] (**) evdev: USB Keyboard: Device: "/dev/input/event5"
[ 2490.951] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x274
[ 2490.951] (--) evdev: USB Keyboard: Found 1 mouse buttons
[ 2490.951] (--) evdev: USB Keyboard: Found scroll wheel(s)
[ 2490.951] (--) evdev: USB Keyboard: Found relative axes
[ 2490.951] (II) evdev: USB Keyboard: Forcing relative x/y axes to exist.
[ 2490.951] (--) evdev: USB Keyboard: Found absolute axes
[ 2490.951] (II) evdev: USB Keyboard: Forcing absolute x/y axes to exist.
[ 2490.951] (--) evdev: USB Keyboard: Found keys
[ 2490.951] (II) evdev: USB Keyboard: Configuring as mouse
[ 2490.951] (II) evdev: USB Keyboard: Configuring as keyboard
[ 2490.951] (II) evdev: USB Keyboard: Adding scrollwheel support
[ 2490.951] (**) evdev: USB Keyboard: YAxisMapping: buttons 4 and 5
[ 2490.951] (**) evdev: USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.951] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.4/5-1.4:1.1/0003:04D9:0274.0006/input/input7/event5"
[ 2490.951] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 13)
[ 2490.951] (**) Option "xkb_rules" "evdev"
[ 2490.951] (**) Option "xkb_model" "pc104"
[ 2490.951] (**) Option "xkb_layout" "us"
[ 2490.951] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.952] (II) evdev: USB Keyboard: initialized for relative axes.
[ 2490.952] (WW) evdev: USB Keyboard: ignoring absolute axes.
[ 2490.952] (**) USB Keyboard: (accel) keeping acceleration scheme 1
[ 2490.952] (**) USB Keyboard: (accel) acceleration profile 0
[ 2490.952] (**) USB Keyboard: (accel) acceleration factor: 2.000
[ 2490.952] (**) USB Keyboard: (accel) acceleration threshold: 4
[ 2490.952] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event9)
[ 2490.952] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 2490.952] (**) Eee PC WMI hotkeys: Applying InputClass "Keyboard Defaults"
[ 2490.952] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 38 paused 0
[ 2490.952] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[ 2490.952] (**) Eee PC WMI hotkeys: always reports core events
[ 2490.952] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event9"
[ 2490.953] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[ 2490.953] (--) evdev: Eee PC WMI hotkeys: Found keys
[ 2490.953] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[ 2490.953] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input12/event9"
[ 2490.953] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 14)
[ 2490.953] (**) Option "xkb_rules" "evdev"
[ 2490.953] (**) Option "xkb_model" "pc104"
[ 2490.953] (**) Option "xkb_layout" "us"
[ 2490.953] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.953] (II) config/udev: Adding input device PC Speaker (/dev/input/event8)
[ 2490.953] (II) No input driver specified, ignoring this device.
[ 2490.953] (II) This device may have been added with another device file.
[ 2491.022] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2491.022] (**) NVIDIA(0): device Samsung SyncMaster (DFP-3) (Using EDID frequencies
[ 2491.022] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2491.034] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2491.034] (**) NVIDIA(0): device Samsung SMS27A850T (DFP-0) (Using EDID frequencies
[ 2491.034] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
Last edited by H3g3m0n (2015-04-01 00:11:52)

WonderWoofy wrote:I'm not sure about your VT issue, but if you set the 'terminate:ctrl_alt_bksp' option with setxkbmap or loginctl, does it work then?
I tried setxkbmap before without success.
Also tried:
localectl set-x11-keymap "us" "" "" "terminate:ctrl_alt_bksp"
Not sure how to go about using loginctl to do the same thing.
Last edited by H3g3m0n (2015-04-01 03:25:35)

How to disable CTRL+ALT+S on Win8

I have an HP notebook (Pavilion 17 or something) with Windows 8 64-bit.
I mainly use it (and primarily bought it) to play video games.
The shortcut CTRL+ALT+S (which opens system information) interferes with playing video games as I use those keys when doing so and far too often at the same time.
How do I disable the CTRL+ALT+S shortcut?
I mean besides a clean install of Windows without any HP programs, obviously.

Hello @jdk21,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I have read your post on how you are looking to disable the CTRL + ALT + S combination on your notebook computer, and I would be happy to assist you in this matter!
To disable this combination, I recommend performing a clean boot on your computer. This can be done by following the steps in this document on How to perform a clean boot in Windows. This should help boot your system with a minimal set of drivers and software, enabling your system to keep the settings changed with the keyboard combination.
If the issue continues, I recommend following the steps below by proceeding to this file location:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\HP Help and Support
Right click HP Support Information
Click properties
Click the box next to shortcut key
Hit backspace so the field says 'none'
Apply
Done!
(Note, If you can't access the folder above you need to show hidden & system files. In a file explorer window click the view tab at the top, then click options on the right, select 'change folder and search options' if prompted. go to the view tab in the popup. check show hidden files, folders, drives. uncheck hide protected operating system files. apply)
reference: http://h30434.www3.hp.com/t5/Desktop-Operating-Systems-Software-Recovery/How-to-disable-Alt-S-shortc...
Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

HT5628 ctrl-alt-del logon & Bitlocker on Win8 with new MacBookAir doesn't work

Am running the latest BootCamp and have a brand new MacBookAir and Win8.
On the Windows Logon Screen I can't use ctrl+alt-del even with fn key or on-screen keyboard. The only way I can logon is by plugging in my keyboard - does any one have a tip please?
I'd like to use Bitlocker HD encryption in Win8, but don't know how to do this, e.g. with storing the Key on a USB thumbdrive if that's the only option - any help is apppreciated.
Thanks!!
Chris

Tthere seems to be a non TPM compatible BIOS on MacBookAir: http://technet.microsoft.com/en-us/library/ee449438%28WS.10%29.aspx#BKMK_NoTPM
And the a plugged in USB drive during the BitLocker Requirement Check yields no change.

Ctrl+Alt+C Shortcut Problem in Indesign CS3

I cannot use the ctrl+alt+c shortcut in IdCS3. The alt key works with all other shortcuts. I believe this is caused by ATI's catalyst control center which uses the same shortcut to open it's window but I disabled the hotkeys in catalyst and even changed that hotkey to one besides ctrl+alt+c and I can still not get the shortcut to work in Id.
This happened to me about a year ago and I can't remember how I fixed it.
Thanks in advance for any help.

I had this problem, Ctrl-Alt-C did not work in Indesign or Photoshop (but CS5.5 & Windows 7).
To fix it:
> right click your desktop background
> select catalyst Control Centre (top of list)
> ‘Options’ at top right pull down menu
(if you can’t see this, choose Advanced install, OK, then go back to step one again)
>Hotkeys > Hot Keys Manager
> select the one thing in the list, then press Edit
> Change from Ctrl+Alt+C to Ctrl+Alt+Shift+C
> OK, OK, OK
Hey presto! It’s all working now!

Ctrl/Alt click to activate link closes current document

We just upgraded from Framemaker 7.2 to 12, and there's a behavior I can't figure out. I have a book file with cross-references between FM documents. Before, in FM 7.2, when I used Ctrl/Alt+click to activate a cross-reference link and follow the marker to a different Frame document, it left the original document open, and also opened the document the link caused me to jump to. In FM 12, it is closing the original document every time I click on a link to follow it. Is there a preference setting or another way to stop Frame from closing the first document every time it opens the document the link is referencing?

Some of these resources might come in handy...They have illustrated workflows and embedded videos. For more assistance: [email protected] and [email protected]
1. 10-part blog series on reasons to upgrade from FM 7.x to FM 10: http://blogs.adobe.com/techcomm/2012/04/part-5-%C2%BD-reasons-to-upgrade-from-fm-7-x-to-fm -10-summary-thus-far.html
2. 8-part blog series on reasons to upgrade from FM 7.x to FM 11:
Part 1 - Part (1) Reasons to upgrade from FM 7.x to FM 11: Catalogs, UI, rich media and more « TechComm Central by Adobe
Part 2 - Part (2) Reasons to upgrade from FM 7.x to FM 11: Workspaces and a Friendlier UI « TechComm Central by Adobe
Part 3 - Part (3) Reasons to upgrade from FM 7.x to FM 11: Track changes and Import PDF comments « TechComm Central by Adobe
Part 4 - Part (4) Reasons to upgrade from FM 7.x to FM 11: Catalogs and Format Overrides « TechComm Central by Adobe
Part 5 - Part (5) Reasons to upgrade from FM 7.x to FM 11: Where were you in 2002? « TechComm Central by Adobe
Part 6 - Part (6) Reasons to upgrade from FM 7.x to FM 11: Book Building « TechComm Central by Adobe
Part 7 - Part (7) Reasons to upgrade from FM 7.x to FM 11: XML and Structured Editing « TechComm Central by Adobe
Part 8 - Part (8) Reasons to upgrade from FM 7.x to FM 11: “Real” support for DITA « TechComm Central by Adobe
3. 8-part blog series on reasons to upgrade from FM 7.x to FM 12.
Upgrade to FM12 INTRO: Overview of many reasons
http://blogs.adobe.com/techcomm/2014/06/why-upgrade-from-fm7-8-or-9-intro-overview-of-many -reasons.html
Upgrade to FM12 Reason #1) Fewer steps, more automation
http://blogs.adobe.com/techcomm/2014/06/why-upgrade-from-fm7-1-new-workflow-ui-powertools- more.html
Upgrade to FM12 Reason #2) Greater customization, customized workflows
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-2-workspaces-productivity-too ls.html
Upgrade to FM12 Reason #3) Collaborative and Mobile Review
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-3-review-cycle-with-mo bile-dropbox-and-cms.html
Upgrade to FM12 Reason #4) Fuller Format and structure control
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-4.html
Upgrade to FM12 Reason #5) Tools for handling large projects
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-5-book-building-and-ex ternal-references.html
Upgrade to FM12 Reason #6) Full DITA Compliance, Accessible Structured Editing
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-6-xml-and-structured-e diting.html
Upgrade to FM12 Reason #7) Direct XML editing and low-cost FM XML Author
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-7-real-ditaxml-authori ng-with-a-junior-version.html
Thanks,
Saibal

Ctrl +Alt + F7 problem

Hi all,
I have installed Arch yesterday and has a problem with X
I installed xfce4, xorg, xorg-xdm and config the /etc/inittab to run xdm at startup like which the wiki says. But anytime I press Ctrl+Alt+F1 to change to tty1, then I can't switch to GUI again, pressing Ctrl+Alt+F7 doesn't have the Xfce appear again.
Anyone can give some reason ?
Thank you for reading and sorry for my enlish

Peasantoid wrote:
You sure it's on tty7?
If so, try `chvt 7`.
Also: you don't need to apologize for your English.
'chvt 7' likes Ctrl+Alt+F7, it draws a black full screen (but I can switch to tty1 again by Ctrl+Alt+F1) Also when I logout from xfce, xdm doesn't "appear" - a black full screen
Thank you anyway. Other suggestion ?

Ctrl-Alt shortcuts to switch modules not working

I'm having trouble with LR 4.1 (Win 7 64 bit) recognizing keyboard input properly. Sometimes it just stops "seeing" ctrl-alt-n (where n=1, 2, 3...) to switch between modules (Library, Develop, etc.). I can do everything else with the keyboard (Tab to show/hide panels, rate, keyword, etc.), but it just doesn't recognize the module shortcuts (or the arrow key versions to move to next/previous). I can change modules with the mouse, but I'd prefer to use keyboard shortcuts. This is a US keyboard on an English-language system. Anyone else experiencing this issue?

Nope, can't say it's happened to me. But I tend to use "d" for develop, or "g" (or "e") for Library.
Could it be that your numeric lock got toggled somehow? What number keys are you using (keypad, or top row)?
Hal

CTRL + ALT doesn't resize my brush anymore !!!! :'(

Hi everyone !
I'm using OSX 10.8.2 and Photoshop CS6, with an intuos 4, and 10 minutes ago the function CTRL+ALT+left or right on my intuos was visually changing the size of my brush, and now, when I use the same combination, it just drags my photoshop window and move it from left to right...!
I can't remember changing anything in the options of my intuos or Photoshop, and make the settings back to defaults doesn't change my problem.
If you have any answer, clue, tip, or anything helpfull, I'd be sooooooo glad !!
thanks !!

Boilerplate-text:
Are Photoshop and OS fully updated and have you performed the usual trouble-shooting routines (trashing prefs by keeping command-alt-shift/ctrl-alt-shift pressed while starting Photoshop after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed, 3rd party plug-ins deactivation, system maintenance, cleaning caches, font validation, etc.)?

Nitro3 kernel and menuconfig and ctrl+alt+fX problem

Hi, im having the stranges occurrences.
I tried 2 use this PKGBUILD of nitro in here http://bbs.archlinux.org/viewtopic.php? … ight=nitro, but changed the nitrover = 3.
it downloaded fine, and it goes to the choice menu :
==> How do you want to configure the kernel:
==> ----------------------------------------
==> (for ArchLinux defaults, use 'not_at_all (1)')
==>
1) not_at_all
2) menuconfig
3) xconfig
4) oldconfig
5) config
when i choose '2', it goes into menuconfig ok, but once i get there, the only keys i can use is enter and esc. when i press the arrow keys to try to move, it already ask you if you want to save the config. I find this very strange since I compiled nitro2 thru menuconfig the last time and it operated normally.
Since menuconfig is out of wack, i tried xconfig, and it operated normally. But strange thing is that after it starts compiling, in the middle of the compliation, i get this error :
if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b /var/abs/local/kernel26/pkg -r 2.6.9-nitro3-ARCH; fi
WARNING: /var/abs/local/kernel26/pkg/lib/modules/2.6.9-nitro3-ARCH/kernel/drivers/video/vesafb-tng.ko needs unknown symbol vesafb_setup
./PKGBUILD: line 133: cd: /var/abs/local/kernel26/pkg/lib/modules/2.6.9-nitro3: No such file or directory
==> ERROR: Build Failed. Aborting...
which I am stoked as what it means.
I am also having problem with switching to console mode after I have started X, like startx or startxfce4. It seems that after it's started I can't switch back to console thru ctrl+alt+f3.
thanks
dammit

Peasantoid wrote:
You sure it's on tty7?
If so, try `chvt 7`.
Also: you don't need to apologize for your English.
'chvt 7' likes Ctrl+Alt+F7, it draws a black full screen (but I can switch to tty1 again by Ctrl+Alt+F1) Also when I logout from xfce, xdm doesn't "appear" - a black full screen
Thank you anyway. Other suggestion ?

Opensource ATI can't switch video modes with CTRL+ALT+plus/minus

Hi,
I've updated my system to the new xorg-server and video driver.
The new video driver (xf86-video-ati-6.7.195-1) can't switch video modes with the CTRL+ALT+plus/minus key combination. I use this key combination a lot and before I upgraded to the new driver this worked :-(
Anybody else having this problem?
I know I can use xrandr to change the video mode, but it doesn't exactly do what I want. Xrandr changes the video mode, but also changes the resolution of the screen, while CTRL+ALT+plus/minus keeps the resolution intact (the screensize is bigger than what is seen on the monitor, you can scroll the screen by moving the mouse "out" of the monitor)
Is there a fix/patch that I can try?

It looks like this is the result of the new opensource ati drivers use the new xrandr.
One of the changes is that it will treat the screen section in xorg.conf differently. Browsing through video modes, using the CTRL+ALT+plus/minus key combination, that are defined in the screen section in xorg.conf is not possible anymore.

Change ctrl + alt + s

Similar Messages

Maybe you are looking for