GL Posting Screen - Change Layout

Hi Friends,
Could you please as to how can we change the layout of the finial screen for GL Postings so that only the desired columns are displayed and in the sequence desired. It is also desired to change the layout of the screens used for AR/AP postings.
Also is it possible to change the layout of the screen used for Invoice Verification postings.
Thnx in advance.

The following link may guid u
http://help.sap.com/saphelp_47x200/helpdata/en/c7/a88af343dd11d182b30000e829fbfe/frameset.htm
Assign points if u feel so .
Dasharathi

Similar Messages

FB60 screen change layout different between DEV and PRD

Hi,
I'm having problem with transaction FB60. When i try to change the layout in PRD, in screen Edit System Setting, some of the field showing 0 length. For example in WBS element field, in DEV show length 24 but PRD show length 0. I try to compare the version but it is same (program & table structure - ACGL_ITEM). When I debug the program, found out that it will get the structure from sap internal c program call 'AB_GET_CX_DATA'. So, maybe this program version are different between DEV and PRD.
Anybody knows what is the cause of this problem? Or maybe somebody can tell me how to check sap internal c program.
Thank you very much.

Yes. FB60 is Enter Vendor Invoice. In this screen you can see a table with column such as GL Acct, Debit/Credit, Amount in DC, Cost Center and others. You can add or remove some of the field using Table Setting and create Screen Variant. My problem is, the length of WBS Element and Profit Center field is 0. How to change the length.
I already searched in forum but I only found how to create screen variant.
Thanks.

Changing Layout on screen with multiple sections

Hello Gurus,
How can we change layouts for 3 different sections of the screen after executing single transaction.. It allows only one layout to set as default but other two remain unchanged. how can we change layouts for each section on the same screen.
SD

Hi Agnes,
Enable 'Suppress Blank Section" option in Section Expert for those 3 footer section.
Go to Section Expert.
Click on the particular section(Say FooterA)
In the Commen tab, Check 'Suppress Blank Section" (5th one).
Do the same for Other two.
Hope this will help
Regards,
Salah

[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

Changing layout of ALV to excel and displaying the data there

Dear All,
My requirement is that I have to develop an ALV report, and also plot the graphs for the same.
I need different types of graphs, so I have searched on SDN, and I found out a blg:-
"Report with a Graph.. An Approach!"
Here is what the person has done:-
I developed a simple ABAP report using ALV and just dumped all my data on it.
After this I downloaded the Standard Excel template available in the ALV.
Defined my own worksheets in this template, wrote some macros to pick up the data from the RawHeader sheet, which is available by default and will contain the ALV data.
I inserted 1 chart in this Excel template. In this chart I used the same chart type as was being used by the user for his graph. Just right clicked on the Graph area and made the changes in the source data and made it point to the sheet containing the final data.
Thats it my job is almost done.
After this uploaded this template back into the report output through
the layout settings->Change Layout Tab.
Save it as a variant and made it a default. (Do not default it if you have more than 1 user and more than 1 template. Select the appropriate variant for the appropriate user and then display)
Well, this also was not that easy as I had thought. I landed up into 1 trouble.
In my report the number of columns displayed was not constant and kept changing based on the input. This fact was taken care by designing a variable field catalogue. But now I had gone past the simple ALV display and was giving the output in an Excel sheet using a pre-defined template. Well, I immediately found a solution to this with the set_frontend_fieldcatalogue method of CL_GUI_ALV_GRID class and fixed the field catalogue every time after calling the set_table_for_first_display method. This solved most of my problems, which were not many though.
Now here are my issues:-
I have developed the ALV report, and I have also changed the layout to excel.
But, I am unable to get the ALV Report data in the RawHeader Sheet, which is available by default.
Could anyone please guide me through this method??
It is urgent.
Points are assured for helpful answers.
Thanks and regards,
Prerna

Hi Satya Priya,
Do I have to create my own template, or the Standard ones available will do?
HEre is what I do:-
Once I get my ALV output, I goto Change LAyout->View tab.->Prefered view->Microsoft Excel.
Here I get a list of available excel templates There are 2:-
sap_mm.xls, and sap_om.xls
I select one of these, and the excel spreadsheet is displayed on the ALV screen.
But the re is another button, "Upload Document to BDS".
Do I have to upload one of the above templated to BDS?
And please tell me in detail, what is BDS???
Thanks for your help, and waiting for reply,
Prerna

Why miss change layout button in ALV report

Hello Experts,
I have strange problem, I run the same transaction two times, one I have the change layout button but another I miss it...
Anything control this button?
thanks a lot for your help!

Hi,
Is this standard Tcode or customized Tcode?
If it is standard tcode, what is the tcode?
If it is customized tcode, can you post some code for us to analyse?
Thanks.
Regards,
Keng Haw

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/

How to Insert Fields in ColumnSet of Change Layout Buttonof ALVgrid Output?

Hi Guys,
Can anybody tell me how to insert columns in Column Set of Change Layout Button.My Reuireemnt is i Have to display the Basic Layout and have to provide the other fields in the "Columnset" in Change Layout which will be displayed when u clcik the Change Layout button in the ALV Grid Output screen. so that user can select based on their usage.
Please Very Urgent.
Thanks,
Gopi.

You can try this ... which field you dont want to show in the fieldcatalog you can use
fieldcat-fieldname = 'F1'.
fieldcat-no_out = 'X'
( suppose F1 field you dont want to show).
But it will appear when user click on the change layout button.
regards
shiba prasad dutta

Pavilion DV& screen changing colors

When turning on the laptop, the screen changes colors (red, green, gray, blue, etc) before coming on. It took almost 25 minutes for it to stop and then finally get the sign on screen.
What could be the problem? The laptop is about 3 years old.
If it need to be repaired, where would i go (Staples? BestBuy?)
Is it something I could fix myself?
TIA

@harperhp ,
Hello and thank you for posting on the HP support forum. Generally when you experience this issue it is due to a failure of the graphics card.
Does this happen if you try and boot into safe mode?
Entering Safe Mode (Windows 7)
Please post back if you can get into safe mode without this issue. If you have the same problem going into safe mode then you will want to contact HP phone support for repair options. You may not be able to get the parts through third party vendors.
Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.
http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
Thank you again for posting and have a great day.
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
D5GR
I work on behalf of HP

Probelm in change layout

I have created one query zmaterial. When i display ALV output it is displaying corectly. but when i got to change layout, in the description of the change layout some text is displaying in english and some in spanish.. please let me know the problem?
Regadrs,
zub

Hi,
please check the links and create a) a useful subject and b) a useful question, thank you.
[FAQ's, intros and memorable discussions in the ABAP General Forum|FAQ's, intros and memorable discussions in the ABAP General Forum;
[How to post code in SCN, and some things NOT to do...|How to post code in SCN, and some things NOT to do...;
[Please read "The Forum Rules of Engagement" before posting! HOT NEWS!! |Please read "The Forum Rules of Engagement" before posting! HOT NEWS!!;
Regards
Clemens

How to Change Layout for Detail iview.

Hi KM Gurus
I need to know , where to change the Layout set for Detail Iview.
Briefly saying....
1. In KM under /documents ,i have a Folder by the name "MY_FOLDER"
2. On click of the "Detail" wedge -
> we get by default the screen of layout similar to [View -->Overview ]
All i am looking is , instead of Overview, i want the Feedback layout as default on click of the "Detail" wedge of Folder.
Note : take a note on MY_FOLDER ---> Details --> View --> Overview / Feedback..
Any pointer on this would be highly appreicated...
Thanks

Hi Kumar.
An Overview is hardcoded as default (initial) screen of the Details Dialog Box.
Thereby, out of the box KM Configuration allows you to:
1.
define which areas appear in the standard overview in the right-hand screen area. You can also change the sequence of the areas. For example, you can always display feedback at the very top, and hide public comments. For more information, see [Overview in the Details Dialog Box|http://help.sap.com/saphelp_nw04s/helpdata/en/bd/f6ece7e98f6b42bd5756dad5a7f6eb/content.htm]
2.
use an alternative Details dialog box in place of the standard Details dialog box. For more information, see [Alternative Details Dialog Box.|http://help.sap.com/saphelp_nw04s/helpdata/en/45/c51dec75112e97e10000000a155369/content.htm]
Best regards,
Aliaksandr Zhukau

How to change layout for list display in background

Hi All,
I want to change layout for the list display of tcode fbl1n when i execute in background. is there anyway to select our own layout when i execute in background. When i execute in foreground we can change the layout by selecting change layout button, but how it possible when in backgroung, is there any way please let me know.
Thanks in advance.
Regards,
Vishal

Hi,
Create a list variant by executing the program and changing the layout and saving..
Then use the "Layout" parameter in the selection screen and give the variant you created earlier...
Then while executing in background the list variant will be pickedup accordingly (given in the selection screen)..
Hope this helps...
THanks,
Naren
Message was edited by: Narendran Muthukumaran

How to change layout of report S_ALR_87012083?

Hi everybody,
    How to change layout of report S_ALR_87012083 except change output control at selection screen ?
    For example,I need a list that there have vendor no. at every line of open item,and I don't need Total liabilities for every vendor.
Thanks a lot for any help.

Hi yu liang,
                 You can find vendor list having Vendor No. & without showing total liability for every vendor.
after executing the report,
1.You need to select "change layout (ctrl+F8)",
a small window comes, it has two part -> column content & hidden fields.
then u select "Vendor" from hidden field & move it to column content.
2. at column content there is a column named "Total". u need to remove check for your column name "amount".
now select "copy" button or enter. u will find the req. report.
u can save it also by ur name.
hope its helpful to u.......
plz, reward points as a way of thanks if helpful...

T-code: FBL1N - Change Layout , Select Layout and Save Layout

hi all,
T-code: FBL1N - Change Layout , Select Layout and Save Layout
3 of the layout was grey out and does not allow me to choose.
Anyone can help?
Thanks.
Joo

Hi KK,
Pls follow the steps below:
1. In the SAP Screen where u get the Change layout icon is grey out.
2. Pls type /nSU53.
3. After that pls open a new session.
4. Pls type SUIM
5. Now, select the "ROLES"
6. Enter your SAP ID and the T-code and click execute
7. The roles will displayed and kindly double click it.
8. Go to the authorization object tab
9. Select display authorization object (Bottom left)
10.Select FIND and enter the authorization object where you can get from /nSU53. The authorization object is start with F_*.
11.Now, click on the display and you can see the authorization object is missing.
12.You can sent the screen shot and request the SAP FICO Functional Team to maintain it in the SAP System.
Assign points if useful
Thanks.
Joo

Changing Layout and RFC used in MSS Attendance Overview iview

Hi There,
We are using HTMLB based MSS iviews and need to change layout and information on Attendance overview screen. We got required PAR file and i can create a project based on this PAR as well.
Now i see so many errors due to missing import, even com.sapportals.html* based import statements are indicated as error..
If i have missed out something during import of this par file, how can i correct it now.
Thanks a lot for your suggestions.
Rgds

thansk Prakash,
Finally directed them to server files.. and it did the job )
Rgds
Edited by: Sudhir on Oct 13, 2008 10:17 AM

GL Posting Screen - Change Layout

Similar Messages

Maybe you are looking for