Change Layout in Sales Support Monitor

Hi,
We want to change layout of Sales support Monitor. T. code VC05. We can change the layout but can not save the changed layout. Can you please help us, how we can save the changed layout?
Regards,
Soumen

Hi Sanjay,
Thanks for your reply. I am not asking about selection screen variant. Once we execute VC05 we get the report. I am asking about Report layout. Is there any possibility to change report layout?
Regards,
Soumen

Similar Messages

VC 05 Sales support monitor

Hi Gurus,
I need to understand transaction VC 05 (Sales Support Monitor), if any body can forward some good link get going.
Thanks & Regards
Bawa

Use this link to know
Sourse : SAP Help
[Sales Support|http://help.sap.com/saphelp_erp60_sp/helpdata/en/10/748534c4603c34e10000009b38f83b/frameset.htm]

Problem with changing layouts in xorg

Hi,
After installing new system (latest) i cant change layouts from keyboard
/etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.60 ([email protected]) Sun Oct 14 21:34:47 PDT 2012
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
Option "XkbOptions" "grp:ctrl_shift_toggle"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
/etc/X11/xorg.conf.d/10-evdev.conf
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbVariant" ","
Option "XkbLayout" "us,ru"
Option "XkbOptions" "grp:ctrl_shift_toggle"
# Option "XkbOptions" "grp:caps_toggle,grp_led:scroll"
EndSection
Xorg log
[ 3949.901]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 3949.901] X Protocol Version 11, Revision 0
[ 3949.901] Build Operating System: Linux 3.6.2-1-ARCH x86_64
[ 3949.901] Current Operating System: Linux Hybrid 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64
[ 3949.901] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=34540cd4-1fc1-4e6d-815f-f26b49fd0ffd ro quiet
[ 3949.901] Build Date: 19 October 2012 03:54:56PM
[ 3949.902]
[ 3949.902] Current version of pixman: 0.26.2
[ 3949.902] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3949.902] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3949.902] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 7 15:47:17 2012
[ 3949.902] (==) Using config file: "/etc/X11/xorg.conf"
[ 3949.902] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 3949.902] (==) ServerLayout "Layout0"
[ 3949.902] (**) |-->Screen "Screen0" (0)
[ 3949.902] (**) | |-->Monitor "Monitor0"
[ 3949.902] (**) | |-->Device "Device0"
[ 3949.902] (**) |-->Input Device "Keyboard0"
[ 3949.902] (**) |-->Input Device "Mouse0"
[ 3949.902] (==) Automatically adding devices
[ 3949.902] (==) Automatically enabling devices
[ 3949.902] (==) Automatically adding GPU devices
[ 3949.902] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3949.902] Entry deleted from font path.
[ 3949.902] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3949.902] Entry deleted from font path.
[ 3949.902] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3949.902] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3949.902] Entry deleted from font path.
[ 3949.902] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3949.902] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3949.902] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3949.902] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 3949.902] (WW) Disabling Keyboard0
[ 3949.902] (WW) Disabling Mouse0
[ 3949.902] (II) Module ABI versions:
[ 3949.902] X.Org ANSI C Emulation: 0.4
[ 3949.902] X.Org Video Driver: 13.0
[ 3949.902] X.Org XInput driver : 18.0
[ 3949.902] X.Org Server Extension : 7.0
[ 3949.904] (--) PCI:*(0:1:0:0) 10de:11c0:1043:8423 rev 161, Mem @ 0xf6000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3949.904] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3949.904] Initializing built-in extension Generic Event Extension
[ 3949.904] Initializing built-in extension SHAPE
[ 3949.904] Initializing built-in extension MIT-SHM
[ 3949.904] Initializing built-in extension XInputExtension
[ 3949.904] Initializing built-in extension XTEST
[ 3949.904] Initializing built-in extension BIG-REQUESTS
[ 3949.904] Initializing built-in extension SYNC
[ 3949.904] Initializing built-in extension XKEYBOARD
[ 3949.904] Initializing built-in extension XC-MISC
[ 3949.904] Initializing built-in extension SECURITY
[ 3949.904] Initializing built-in extension XINERAMA
[ 3949.904] Initializing built-in extension XFIXES
[ 3949.904] Initializing built-in extension RENDER
[ 3949.904] Initializing built-in extension RANDR
[ 3949.904] Initializing built-in extension COMPOSITE
[ 3949.904] Initializing built-in extension DAMAGE
[ 3949.904] Initializing built-in extension MIT-SCREEN-SAVER
[ 3949.904] Initializing built-in extension DOUBLE-BUFFER
[ 3949.904] Initializing built-in extension RECORD
[ 3949.904] Initializing built-in extension DPMS
[ 3949.904] Initializing built-in extension X-Resource
[ 3949.904] Initializing built-in extension XVideo
[ 3949.904] Initializing built-in extension XVideo-MotionCompensation
[ 3949.904] Initializing built-in extension XFree86-VidModeExtension
[ 3949.904] Initializing built-in extension XFree86-DGA
[ 3949.904] Initializing built-in extension XFree86-DRI
[ 3949.904] Initializing built-in extension DRI2
[ 3949.904] (II) LoadModule: "glx"
[ 3949.904] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3949.914] (II) Module glx: vendor="NVIDIA Corporation"
[ 3949.914] compiled for 4.0.2, module version = 1.0.0
[ 3949.914] Module class: X.Org Server Extension
[ 3949.914] (II) NVIDIA GLX Module 304.60 Sun Oct 14 20:44:54 PDT 2012
[ 3949.914] Loading extension GLX
[ 3949.914] (II) LoadModule: "nvidia"
[ 3949.915] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 3949.915] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 3949.915] compiled for 4.0.2, module version = 1.0.0
[ 3949.915] Module class: X.Org Video Driver
[ 3949.915] (II) NVIDIA dlloader X Driver 304.60 Sun Oct 14 20:24:42 PDT 2012
[ 3949.915] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 3949.915] (++) using VT number 1
[ 3949.915] (II) Loading sub module "fb"
[ 3949.915] (II) LoadModule: "fb"
[ 3949.915] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 3949.916] (II) Module fb: vendor="X.Org Foundation"
[ 3949.916] compiled for 1.13.0, module version = 1.0.0
[ 3949.916] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3949.916] (II) Loading sub module "wfb"
[ 3949.916] (II) LoadModule: "wfb"
[ 3949.916] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 3949.916] (II) Module wfb: vendor="X.Org Foundation"
[ 3949.916] compiled for 1.13.0, module version = 1.0.0
[ 3949.916] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3949.916] (II) Loading sub module "ramdac"
[ 3949.916] (II) LoadModule: "ramdac"
[ 3949.916] (II) Module "ramdac" already built-in
[ 3949.916] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 3949.916] (==) NVIDIA(0): RGB weight 888
[ 3949.916] (==) NVIDIA(0): Default visual is TrueColor
[ 3949.916] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 3949.916] (**) NVIDIA(0): Enabling 2D acceleration
[ 3950.393] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3950.393] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.403] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3950.403] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.403] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 660 (GK106) at PCI:1:0:0 (GPU-0)
[ 3950.403] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 3950.403] (--) NVIDIA(0): VideoBIOS: 80.06.10.00.0e
[ 3950.403] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 3950.403] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 3950.406] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 660 at PCI:1:0:0
[ 3950.406] (--) NVIDIA(0): CRT-0
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0) (connected)
[ 3950.406] (--) NVIDIA(0): DFP-1
[ 3950.406] (--) NVIDIA(0): DFP-2
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3) (connected)
[ 3950.406] (--) NVIDIA(0): DFP-4
[ 3950.406] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0): 330.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0): Internal Dual Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3): 330.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3): Internal Dual Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-4: 960.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 3950.406] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.406] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3950.406] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.407] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.407] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.407] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.407] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.407] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.407] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.407] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.407] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.407] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.407] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.408] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.408] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3950.408] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.408] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.408] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.408] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.408] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.408] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.409] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.409] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.409] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.409] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.409] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.410] (==) NVIDIA(0):
[ 3950.410] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 3950.410] (==) NVIDIA(0): will be used as the requested mode.
[ 3950.410] (==) NVIDIA(0):
[ 3950.410] (II) NVIDIA(0): Validated MetaModes:
[ 3950.410] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3950.410] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
[ 3950.443] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
[ 3950.443] (--) NVIDIA(0): option
[ 3950.443] (--) Depth 24 pixmap format is 32 bpp
[ 3950.443] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 3950.443] (II) NVIDIA: access.
[ 3950.445] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 3950.445] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 3950.445] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 3950.445] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 3950.445] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 3950.445] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 3950.445] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 3950.445] (II) NVIDIA(0): Config Options in the README.
[ 3950.448] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3950.551] Loading extension NV-GLX
[ 3950.608] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 3950.608] (==) NVIDIA(0): Backing store disabled
[ 3950.608] (==) NVIDIA(0): Silken mouse enabled
[ 3950.608] (**) NVIDIA(0): DPMS enabled
[ 3950.608] Loading extension NV-CONTROL
[ 3950.609] Loading extension XINERAMA
[ 3950.609] (II) Loading sub module "dri2"
[ 3950.609] (II) LoadModule: "dri2"
[ 3950.609] (II) Module "dri2" already built-in
[ 3950.609] (II) NVIDIA(0): [DRI2] Setup complete
[ 3950.609] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 3950.609] (--) RandR disabled
[ 3950.611] (II) Initializing extension GLX
[ 3950.643] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 3950.643] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3950.643] (II) LoadModule: "evdev"
[ 3950.643] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 3950.643] (II) Module evdev: vendor="X.Org Foundation"
[ 3950.643] compiled for 1.13.0, module version = 2.7.3
[ 3950.643] Module class: X.Org XInput Driver
[ 3950.643] ABI class: X.Org XInput driver, version 18.0
[ 3950.643] (II) Using input driver 'evdev' for 'Power Button'
[ 3950.643] (**) Power Button: always reports core events
[ 3950.643] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 3950.643] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3950.644] (--) evdev: Power Button: Found keys
[ 3950.644] (II) evdev: Power Button: Configuring as keyboard
[ 3950.644] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 3950.644] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 3950.644] (**) Option "xkb_rules" "evdev"
[ 3950.644] (**) Option "xkb_model" "evdev"
[ 3950.644] (**) Option "xkb_layout" "us,ru"
[ 3950.644] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.663] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 3950.663] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3950.663] (II) Using input driver 'evdev' for 'Power Button'
[ 3950.663] (**) Power Button: always reports core events
[ 3950.663] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 3950.663] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3950.663] (--) evdev: Power Button: Found keys
[ 3950.663] (II) evdev: Power Button: Configuring as keyboard
[ 3950.663] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 3950.663] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 3950.663] (**) Option "xkb_rules" "evdev"
[ 3950.663] (**) Option "xkb_model" "evdev"
[ 3950.663] (**) Option "xkb_layout" "us,ru"
[ 3950.663] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.663] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
[ 3950.663] (II) No input driver specified, ignoring this device.
[ 3950.663] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device UVC Camera (046d:0821) (/dev/input/event6)
[ 3950.664] (**) UVC Camera (046d:0821): Applying InputClass "evdev keyboard catchall"
[ 3950.664] (II) Using input driver 'evdev' for 'UVC Camera (046d:0821)'
[ 3950.664] (**) UVC Camera (046d:0821): always reports core events
[ 3950.664] (**) evdev: UVC Camera (046d:0821): Device: "/dev/input/event6"
[ 3950.664] (--) evdev: UVC Camera (046d:0821): Vendor 0x46d Product 0x821
[ 3950.664] (--) evdev: UVC Camera (046d:0821): Found keys
[ 3950.664] (II) evdev: UVC Camera (046d:0821): Configuring as keyboard
[ 3950.664] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.2/input/input6/event6"
[ 3950.664] (II) XINPUT: Adding extended input device "UVC Camera (046d:0821)" (type: KEYBOARD, id 8)
[ 3950.664] (**) Option "xkb_rules" "evdev"
[ 3950.664] (**) Option "xkb_model" "evdev"
[ 3950.664] (**) Option "xkb_layout" "us,ru"
[ 3950.664] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.664] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/event3)
[ 3950.664] (**) Razer Razer Mamba Charging Dock: Applying InputClass "evdev pointer catchall"
[ 3950.664] (II) Using input driver 'evdev' for 'Razer Razer Mamba Charging Dock'
[ 3950.664] (**) Razer Razer Mamba Charging Dock: always reports core events
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: Device: "/dev/input/event3"
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Vendor 0x1532 Product 0xf
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found 11 mouse buttons
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found scroll wheel(s)
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found relative axes
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found x and y relative axes
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as mouse
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: Adding scrollwheel support
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: YAxisMapping: buttons 4 and 5
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.664] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.0/input/input3/event3"
[ 3950.664] (II) XINPUT: Adding extended input device "Razer Razer Mamba Charging Dock" (type: MOUSE, id 9)
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: initialized for relative axes.
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) keeping acceleration scheme 1
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration profile 0
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration factor: 2.000
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration threshold: 4
[ 3950.665] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/mouse0)
[ 3950.665] (II) No input driver specified, ignoring this device.
[ 3950.665] (II) This device may have been added with another device file.
[ 3950.665] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/event4)
[ 3950.665] (**) Razer Razer Mamba Charging Dock: Applying InputClass "evdev keyboard catchall"
[ 3950.665] (II) Using input driver 'evdev' for 'Razer Razer Mamba Charging Dock'
[ 3950.665] (**) Razer Razer Mamba Charging Dock: always reports core events
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: Device: "/dev/input/event4"
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Vendor 0x1532 Product 0xf
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found 1 mouse buttons
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found scroll wheel(s)
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found relative axes
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Forcing relative x/y axes to exist.
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found absolute axes
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Forcing absolute x/y axes to exist.
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found keys
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as mouse
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as keyboard
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Adding scrollwheel support
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: YAxisMapping: buttons 4 and 5
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.665] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.1/input/input4/event4"
[ 3950.665] (II) XINPUT: Adding extended input device "Razer Razer Mamba Charging Dock" (type: KEYBOARD, id 10)
[ 3950.665] (**) Option "xkb_rules" "evdev"
[ 3950.665] (**) Option "xkb_model" "evdev"
[ 3950.665] (**) Option "xkb_layout" "us,ru"
[ 3950.665] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: initialized for relative axes.
[ 3950.665] (WW) evdev: Razer Razer Mamba Charging Dock: ignoring absolute axes.
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) keeping acceleration scheme 1
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration profile 0
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration factor: 2.000
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration threshold: 4
[ 3950.665] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:2010 (/dev/input/event5)
[ 3950.665] (**) Logitech Unifying Device. Wireless PID:2010: Applying InputClass "evdev keyboard catchall"
[ 3950.665] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:2010'
[ 3950.665] (**) Logitech Unifying Device. Wireless PID:2010: always reports core events
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: Device: "/dev/input/event5"
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Vendor 0x46d Product 0xc52b
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found 1 mouse buttons
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found scroll wheel(s)
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found relative axes
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Forcing relative x/y axes to exist.
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found absolute axes
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Forcing absolute x/y axes to exist.
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found keys
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Configuring as mouse
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Configuring as keyboard
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Adding scrollwheel support
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: YAxisMapping: buttons 4 and 5
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.665] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.2/0003:046D:C52B.0005/input/input5/event5"
[ 3950.665] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:2010" (type: KEYBOARD, id 11)
[ 3950.665] (**) Option "xkb_rules" "evdev"
[ 3950.665] (**) Option "xkb_model" "evdev"
[ 3950.665] (**) Option "xkb_layout" "us,ru"
[ 3950.666] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.666] (II) evdev: Logitech Unifying Device. Wireless PID:2010: initialized for relative axes.
[ 3950.666] (WW) evdev: Logitech Unifying Device. Wireless PID:2010: ignoring absolute axes.
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) keeping acceleration scheme 1
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration profile 0
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration factor: 2.000
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration threshold: 4
[ 3950.666] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.666] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.666] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event9)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.702] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3950.702] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.702] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.702] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3950.702] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.702] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.702] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.702] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.702] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.702] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.703] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.703] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.703] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.703] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.703] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.714] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3950.714] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.714] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.714] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3950.714] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.714] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.714] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.714] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.714] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.714] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.714] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.714] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.714] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.714] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.714] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.033] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3951.033] (II) NVIDIA(GPU-0): Vision stereo.
[ 3951.033] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3951.033] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3951.033] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3951.033] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3951.033] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.033] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.033] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.033] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3951.034] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.034] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.034] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.034] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.044] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3951.044] (II) NVIDIA(GPU-0): Vision stereo.
[ 3951.044] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3951.044] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3951.044] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3951.044] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3951.044] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.044] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.044] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.044] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.045] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3951.045] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.045] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.045] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.045] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.685] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3961.685] (II) NVIDIA(GPU-0): Vision stereo.
[ 3961.685] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3961.685] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3961.685] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3961.686] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3961.686] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.686] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.686] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.686] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.686] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3961.686] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.686] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.686] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.686] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.697] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3961.697] (II) NVIDIA(GPU-0): Vision stereo.
[ 3961.697] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3961.697] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3961.697] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3961.697] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3961.697] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.697] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.697] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.697] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.697] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3961.697] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.697] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.697] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.697] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.080] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3963.080] (II) NVIDIA(GPU-0): Vision stereo.
[ 3963.080] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3963.080] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3963.080] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3963.080] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3963.080] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.080] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.080] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.080] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3963.081] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.081] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.081] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.081] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.091] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3963.091] (II) NVIDIA(GPU-0): Vision stereo.
[ 3963.091] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3963.091] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3963.091] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3963.091] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3963.091] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.091] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.091] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.091] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.092] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3963.092] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.092] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.092] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.092] (WW) NVIDIA(GPU-0): for mode "1920x1080".
Output of setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: evdev
layout: us,ru
variant: ,
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+ru:2+inet(evdev)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+ru:2+inet(evdev)" };
xkb_geometry { include "pc(pc104)" };
But this comand helps:
setxkbmap -layout "us,ru" -option "grp:ctrl_shift_toggle"
New output of setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: evdev
layout: us,ru
options: grp:ctrl_shift_toggle
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+ru:2+inet(evdev)+group(ctrl_shift_toggle)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+ru:2+inet(evdev)+group(ctrl_shift_toggle)" };
xkb_geometry { include "pc(pc104)" };
This config is still not changing visualistaion of layout (right top corner of gnome), but triggering is ok
If it helps - keyboard is Logitech K800, desktop - gnome 3
Thanks for attention and sorry for my bad english
UPD: Solved by Gnome settings, not Xorg
Last edited by fu2re (2012-11-12 09:44:01)

I have re-checked the issue and I found that the problem is with JPG file.
I wasn't even aware you could save a path to a jpeg file (always use PSD because of wanting to keep the Alpha Channel, jpeg only can contain 1 layer and no alpha channels and/or transparency).
However I tried it on a file with a simple path and one with a complex path. It seems indeed you have found a bug. The simple path is no problem but the more complex path is indeed disappearing.
It is not only label but also rate or adding IPTC in the description field. The moment metadata is saved to this jpeg file and reopened the earlier present work path of a more complex path is gone.
Despite the fact that to my opinion a jpeg is not the most suitable file format for saving a work path this should not happen. If a work path is saved to a jpeg then it should be kept saved after just altering metadata in Bridge.
It still is the same behavior in Bridge CC because that is what I use. Don't know when it started but it still needs to be repaired
Here is the link for filing a problem or bug:
http://feedback.photoshop.com/photoshop_family/

PLD: B1 always uses the same layout in Sales Opportunity(2005A SP1 PL31&36)

Hi all,
I can change the print layout of Sales Opportunities and Payment Receipts (B1 will show the defined layout in bold), but when I preview it, or print it, the same layout is always used. I have noticed this in 4 systems, using SQL Server 2000 and 2005...
Has someone come across this problem? How can I solve it?
Best Regards,
Vítor

Hello Shanker,
I did just that, the problem is whatever layout I choose as default, B1 uses one that was set before...
I've been doing some tests and got the following results:
In the Layout Designer, after pressing the "Set as default" button, we have these options:
1. Set as default for All users
2. Set as default for Current User
3. Set as default for all BP's (for whom a default template has not been assigned)
4. Set as default for specific BP
I tried out all the possible combinations and got the following results:+
If,
1     2        3      4
No     Yes     Yes     No   --> Printout OK, B1 Bad
No     Yes     No      Yes --> Printout Bad, B1 OK
Yes    No      Yes     No   --> Printout OK, B1 Bad
Yes    No      No      Yes --> Printout Bad, B1 Bad
Printout OK = The layout I choose as default is the one used;
Printout Bad = The layout I choose as default is not the one used;
B1 OK = SAP B1 shows in bold the layout I choose as default;
B1 Bad = SAP B1 does not show in bold the layout I choose as default.
Can please someone verify if this happens in other systems (I've tested in B1 2005A PL31 and Pl36)?

Change Layout for Document Access Right

Dear SAP B1 dev. team and management,
I have read the LICENSE COMPARISON CHART in the following link:
https://websmp206.sap-ag.de/~sapidb/011000358700000953982007E
I find that there is a confusing functionality in the sales A/R. It is change layout for document. Does it means change PLD for document ?
In the chart, the change layout for document acess right is full for logistict users. Does it means that all users that assigned with limited logistics will be able to change the default PLD before they start to print the delivery order ?
if yes, the SAP B1 8.8 SP00 PL12 seems has bugs. I said so because the user with limited logistic (LL) can open the PLD icon to change the layout they want to use. The chart info seems uncorrect and the SBO end users can claim that it's deceitful.
Could you check it and create hotfix for your B1 8.8 SP00 PL12 ? Thanks in adv.
Rgds,
JimM

Solved in B1 8.8 SP00 PL13

Saving Option in Change layout TAB

Hi ,
I am taking Sales order list in VA05
I clicked on change layout tab n Selct field as per my requirements
but Now I want to save that layout but I am not getting any saving option
in menu bar Settings - layout - saving this option is in grey
How to activate this option?
Regards,
Akshay

Hi,
check this thread, you have only answered this questions answer
VA05 : Save Layout Option is deactive..
Thanks,
Raja

Screen Layout of Sales Orders

Hello All,
Is it possible to define screen layout of sales orders VA01/VA02? The requirement is to disallow changes in the unit of measure field when creating or changing an SO.
In IMG > MM > Purchasing > theres Define screen layout at document level. Is there a similar functionality in SD?
Suggestions for possible work arounds are welcome also.
Thanks!

Hello All,
Thanks for your input.
SHD0: Should this creation of a transaction variant a BASIS Security task?
VOV8: Do i place the variant in Transaction Flow > Variant Field?

Upgraded to iphoto 11 to change layouts for a book I am making. Help!

Upgraded to iphoto 11 to change layouts for a book I am making.
Layout change went great but now I have text in the lower right hand corner of my cover that I cannot remove.
It is the old title of the book but smaller and where the page number would be. Show/Hide page number has no effect although changing the font for page numbers does affect the text.
I really do not want to start over. I have tried changing layouts to no avail. I wish I could make a new cover and just import it to replace the one I have. Any ideas? Is there a command line fix that could solve this?
Thanks for any suggestions!

check a preview of the book and see if it is there - Before ordering your book preview it using this method - http://support.apple.com/kb/HT1040 - and save the resulting PDF for reference - the delivered book will match it.
LN

Changing layout parameters in container

Hi,
Is there a way to chage layout parameters for component wich is already in container???
Sample code:
JPanel jc = new JPanel(new BorderLayout());
JTextLabel xx = new JTextLabel("Text");
jc.add(xx,BorderLayout.CENTER);
public void ButtonClick(){
    changePosition(xx,BorderLayout.SOUTH);
public void changePosition(JComponent x,Object o){
    // Howto change layout constraint to component x
}-jori

Hi,
The gateway is installed within an instance by the dispatcher and reads its parameters from the profile file located in the profile directory in the SAP directory tree.
This means that the parameter can be changed in production operation (in transaction RZ10 or in the gateway monitor (SMGW) by choosing Goto ® Parameter ® Change. See Changing Gateway Parameters).
Hope this helps.
Regards,
Deepak Kori

[svn] 3411: * Change layout-related width/height, explicit width/height, measured width/height properties from post-scale to pre-transform.

Revision: 3411
Author: [email protected]
Date: 2008-09-29 16:44:01 -0700 (Mon, 29 Sep 2008)
Log Message:
* Change layout-related width/height, explicit width/height, measured width/height properties from post-scale to pre-transform. yay!
* Flex3 containers are updated to support the new behavior.
* Repeatedly scaling a component can differ from before, since we no longer accumulate rounding errors.
* The change is gated by a version flag, in compatibility mode these properties don't change.
Reviewed by Glenn, Ely
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/flex/layout/LayoutItemUIC.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Accordion.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Box.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/DividedBox.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/FormItem.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Tile.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/utilityClasses/BoxLayout.a s
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/utilityClasses/CanvasLayou t.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/Container.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
Added Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/utilityClasses/PostScaleAd apter.as

I am sorry to have to point out to you that you have changed SpryMenuBasicSkin.css so much that it is impossible to render any assistance.
To start with, the menubar has an ID of MenuBar, yet in the CSS I only see this referenced as a CLASS as in
.MenuBar {
background-color:#cccccc;
font-family: Arial, Helvetica, sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
MenuItem, and MenuItemLabel
at a given level all use same definition for ems.
Note that this means the size is also inherited to child submenus,
so use caution in using relative sizes other than
100% on submenu fonts. */
font-weight: normal;
font-size: 16px;
font-style: normal;
padding:0;
border-color: #ffffff #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
I would suggest to start again.
Once you have done that, supply a link to your site and we will assist you further.
Gramps

CRM_DNO_MONITOR - way to customise display apart from 'change layout' ?

Hi friends,
In the transaction CRM_DNO_MONITOR, there is a standard screen offering a few selection parameters.
Based on what you choose, the next screen is displayed with all those relevant messages.
There is a "Change Layout Button" as with many SAP reports. One can choose to include a further fields to get displayed on the report screen.
My questions are:
(1) Is there a way to include more fields than suggested by the "Change Layout" dialog box? For instance, I was keen to know why the following fields were not offered for selection:
a) Support Team
b) Subject (field name - LISTCODE)
(2) Is there a way to easily include Z fields as part of the Support Message (standard Transaction Type SLFN) and use such Z fields in display ?
(3) Is there any other transaction, apart from CRM_DNO_MONITOR that offers even better control on filtering/ sorting messages ?
Any suggestions and workarounds would be gratefuly acknowedged.
Regards,
Srini

Dear Alagammai,
Thanks for your time.
Being a person who started from 3.1 days, yes DNOTIFWL was my first port of call
However, what I realised was that if you set a notification to 'Completed', it does not automatically set the Message Status to 'Confirmed'. Therefore, the status values as seen by Testers from within STWB_WORK does not reflect the updated position.
[This|https://websmp103.sap-ag.de/~sapdownload/011000358700001197002005E/Addtional_Information.pdf] document - once proposed by Raguraman C in reply to another member [thread |Notification Vs transaction type;also does not exactly answer the utility served by DNOTIFWL.
At the moment, ii is not an option I have since there is no ABAP talent meant to serve SolMan stream. i is inadequate and iii doesn't help either, unfortunately.
Thanks for your time though. If you ever find a better solution, please update in this thread.
Regards,
Srini
Format changed; Edited by: Srinivasan Radhakrishnan on Apr 24, 2008 1:31 PM

Change layout Button In ALV Grid

Hi all,
I have a requirement where I am creating Field Catalogue from Z Table(has 60 fields) for few(12) fields.
The user would like to have the option to add more fields by changing the Layout. But I dont see the Fields in Hidden Column when I click the Change Layout Button in ALV Toolbar. It just displays the Field based on Field Catalogue defined.
Is there a way I can maintain all the fields without being displayed in ALV initally and letting the user select the hidden fields as per their requirement. As happens in SE16 where we can select the fields to be displayed.
Thanks for the support.

Hi Abhilasha,
In the reuse_alv function module we can see a field I_SAVE.If you pass this as 'X' then the option of saving the layout variants are available.
Create a layout by,selecting just the fileds required for display and set it as the default variant.It can be made Global or user-specific.But we need to declare all fields in the fieldcatalog.
So if the default variant is set,everytime the program is run it shows only the fields selected in it but can select more form the change layout option.
Hope it helps.
Regards
Byju

Chat support link going to sales support

Just tried to get into chat support but the link is going to sales support. Can you please get it changed. The new version says its support but the entry form has changed and the person I spoke with didn't seem to have any idea what I was talking about or was able to help with my question (how to change who receives the weekly report) at all
This the the new link on the website for chat with support: https://sales.liveperson.net/hc/57472748/?cmd=file&file=visitorWantsToChat&site=57472748&v isitor=5520819318907&msessionkey=336866646992
cheers
deb

Dear Arun,
Donu2019t get tensed with the new responsibilities in retail industry most of the tickets you will get would be from Masters Records (Customer, Material), Material Determination, Listing & Exclusion, Free Goods etc.
All the best for your new Endeavour.
Regards,
Ashutosh

Bangalore, India - Printer after sales support is non existent

This is a rant about terrible after sales support in Bangalore, India from your authorized reseller.
We purchased a new photosmart plus recently after the older HP laserjet 3055 conked out. The older printer was to be repaired while we also agreed to purchase a new photosmart plus.
Its been a month since the laserjet was taken away for a suspected motherboard failure - we havent received it back yet.
And the photosmart plus: we've been facing repeated cartridge changes. The black ink cartridge is either unavailable or the service center is just lax in following up on our requests.
This forum post is just the culmination of a week full of calls and threats to the reseller - systech to send us cartridges and return the older laserjet.
At the moment - we've stopped all printing (4 days now) and terribly harried!

Click the "contact support" link toward the lower-left of that page and follow the instructions.
Regards.

Wlan doesn't support monitor mode

Hi everybody,
I'm new in the Arch's world and today I installed Arch on my MacBookAir 4.2 and I installed wifite but when I try to change the wl in "monitor mode" the wl crashes and I must restart the wl.
This is a my pc info with this commands:
uname -a
lspci -nnk | grep -iA2 net
lsusb
iwconfig
rfkill list all
lsmod
Linux Arch-MacOSX 4.0.4-1-ARCH #1 SMP PREEMPT Mon May 18 06:43:19 CEST 2015 x86_64 GNU/Linux
02:00.0 Network controller [0280]: Broadcom Corporation BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Apple Inc. AirPort Extreme [106b:00e9]
Kernel driver in use: wl
Bus 002 Device 003: ID 05ac:8404 Apple, Inc. Internal Memory Card Reader
Bus 002 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 05ac:850a Apple, Inc. FaceTime Camera
Bus 001 Device 005: ID 05ac:024d Apple, Inc. Internal Keyboard/Trackpad (MacBook Air) (ISO)
Bus 001 Device 008: ID 05ac:821f Apple, Inc. Built-in Bluetooth 2.0+EDR HCI
Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
wlp2s0 IEEE 802.11abg ESSID:"cvsg1"
Mode:Managed Frequency:2.452 GHz Access Point: 64:66:B3:2D:FF:BD
Bit Rate=52 Mb/s Tx-Power=200 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=33/70 Signal level=-77 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Module Size Used by
nls_utf8 16384 0
ntfs 204800 0
ppp_deflate 16384 0
bsd_comp 16384 0
ppp_async 20480 1
crc_ccitt 16384 1 ppp_async
l2tp_ppp 24576 0
l2tp_netlink 20480 1 l2tp_ppp
l2tp_core 32768 2 l2tp_ppp,l2tp_netlink
ip6_udp_tunnel 16384 1 l2tp_core
udp_tunnel 16384 1 l2tp_core
pppoe 20480 0
pppox 16384 2 l2tp_ppp,pppoe
ppp_generic 32768 10 l2tp_ppp,pppoe,pppox,bsd_comp,ppp_async,ppp_deflate
slhc 20480 1 ppp_generic
btusb 40960 0
bluetooth 442368 2 btusb
hid_generic 16384 0
wl 6303744 0
coretemp 16384 0
intel_rapl 20480 0
hid_apple 16384 0
iosf_mbi 16384 1 intel_rapl
x86_pkg_temp_thermal 16384 0
intel_powerclamp 20480 0
joydev 20480 0
kvm_intel 155648 0
mousedev 20480 0
kvm 446464 1 kvm_intel
crct10dif_pclmul 16384 0
nls_iso8859_1 16384 1
crc32_pclmul 16384 0
nls_cp437 20480 1
crc32c_intel 24576 0
i915 1024000 8
vfat 24576 1
fat 65536 1 vfat
ghash_clmulni_intel 16384 0
uvcvideo 86016 0
usbhid 49152 0
snd_hda_codec_hdmi 53248 1
hid 110592 3 hid_generic,usbhid,hid_apple
bcm5974 20480 0
applesmc 20480 0
mac_hid 16384 0
iTCO_wdt 16384 0
evdev 24576 13
snd_hda_codec_cirrus 20480 1
iTCO_vendor_support 16384 1 iTCO_wdt
videobuf2_vmalloc 16384 1 uvcvideo
led_class 16384 1 applesmc
aesni_intel 172032 0
snd_hda_codec_generic 65536 1 snd_hda_codec_cirrus
drm_kms_helper 102400 1 i915
input_polldev 16384 1 applesmc
cfg80211 483328 1 wl
aes_x86_64 20480 1 aesni_intel
hwmon 16384 2 applesmc,coretemp
videobuf2_memops 16384 1 videobuf2_vmalloc
lrw 16384 1 aesni_intel
gf128mul 16384 1 lrw
glue_helper 16384 1 aesni_intel
ablk_helper 16384 1 aesni_intel
cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper
videobuf2_core 40960 1 uvcvideo
pcspkr 16384 0
snd_hda_intel 28672 3
v4l2_common 16384 1 videobuf2_core
i2c_i801 20480 0
snd_hda_controller 28672 1 snd_hda_intel
snd_hda_codec 114688 5 snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller,snd_hda_codec_cirrus
videodev 135168 3 uvcvideo,v4l2_common,videobuf2_core
uas 24576 0
media 20480 2 uvcvideo,videodev
sbs 16384 0
snd_hwdep 16384 1 snd_hda_codec
usb_storage 61440 1 uas
rfkill 24576 3 cfg80211,bluetooth
drm 282624 10 i915,drm_kms_helper
sbshc 16384 1 sbs
apple_bl 16384 0
ac 16384 0
snd_pcm 90112 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
video 24576 1 i915
battery 20480 0
snd_timer 28672 1 snd_pcm
mei_me 20480 0
button 16384 1 i915
shpchp 36864 0
mei 77824 1 mei_me
intel_gtt 20480 1 i915
snd 69632 14 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_hda_codec_cirrus
i2c_algo_bit 16384 1 i915
lpc_ich 24576 0
i2c_core 53248 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
soundcore 16384 2 snd,snd_hda_codec
processor 28672 0
sch_fq_codel 20480 3
ext4 512000 3
crc16 16384 2 ext4,bluetooth
mbcache 20480 1 ext4
jbd2 90112 1 ext4
sd_mod 36864 5
ahci 36864 4
libahci 28672 1 ahci
libata 184320 2 ahci,libahci
scsi_mod 147456 4 uas,usb_storage,libata,sd_mod
uhci_hcd 45056 0
ehci_pci 16384 0
ehci_hcd 73728 1 ehci_pci
usbcore 200704 9 uas,btusb,uhci_hcd,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid,bcm5974
usb_common 16384 1 usbcore
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
How I can use the monitor mode for use wifite?
Thanks for any answer!!!
Last edited by skioda86 (2015-05-22 10:00:45)

As far as i know the wl (proprietary broadcom driver) doesn't support monitor/injection.
But the Mac80211 alternatives might. If they support the wifi chip in your MacBook.
From experience with a friends MBP it didn't yet support his broadcom so had to use WL to get basic network connectivity and used an Dual-band(2.4Ghz/5Ghz) 2x2 11n/ac USB dongle for his monitor/injection needs.

Change Layout in Sales Support Monitor

Similar Messages

Maybe you are looking for