Changing layout in /SAPAPO/OM16

Hello All,
I wanted to use the report /SAPAPO/OM16 to find out the planned orders without source of supply.
But here after excuting the report in the output I wanted to change the layout of the output. This can be done but there is no way I can save the layout.
There is option of saying the layout, but it is not working.
If anybody is aware, please let me know the same.
Thanks,
Rajesh

Hello Senthil,
if you want to extend the selection of the /SAPAPO/OM16 you can implement note
Hinweis 1598890 - Erweiterung der Selektionsmöglichkeiten in der /SAPAPO/OM16
and start transaction /SAPAPO/OM19 as described in the note and execute REGENERATE in the command field to compile the new /SAPAPO/OM16 selection screen.
Best Regards,
Guido Berning

Similar Messages

  • CRM 7.0 Change Layout in Pop-Up's

    Hi Guru's,
    i want to change the layout of a pop-up window.
    That is the "normal" way to change layouts:
    Open the Object what i want to change (in web ui), click with the mouse on the configuration-button. The technical details displayed, also the component name. Then i go in IMG BP WD Workbench and change the layout.
    That works, i've done it much a lot.
    But in pop-up's i can't click on a configuration-button. The button does not exist in pop-up's.
    Example:
    Logon Web UI, open an Opportunity, fill up the needed data and save. Then go on the Button "Follow-Up".
    A pop-up window displayed. And this pop-up window, i want to change the layout (not only for me, i know i can do it with the button personally).
    I hope somebody can give me a solution.
    Thanks a lot and greetings
    Tanja

    Now i know the answer:
    F2-ALT-SHIFT > View Hierarchy Info > here you can find the component
    Additional Goodies:
    F2-ALT-SHIFT-CTRL > Shortcut Info
    F2 > Field Info
    F2-ALT > Conditional breakpoints
    F7-CTRL-SHIFT > Performance Tracker
    F2-ALT-CTRL > System Info

  • 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.
    That’s 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

  • Hide Change Layout Button in ALV report o/p for MB52 Tcode

    Hi,
    Is it possible to Hide Change Layout Button in ALV output for Report MB52 using authoriztaion.
    We have created a layout in which we are hiding some coloumns which the user should not see.
    But if the change layout button is active then the user can add those coloumns to output.
    Is this possible through authorizations. I want to avoid doing any chnages to the std sap program.
    Thanks & Regards,
    Fawaz

    Check the object S_ALV_LAYO

  • 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

  • Changing layout into excel sheet.

    Hi experts's,
    In a ALV report (not OOP's concept) i want to display changing layout fields in EXCEL sheet. please send if you have sample program.
    please suggest how to solve this problem.
    Thanks and regard
    pavan.

    Hi experts's,
    In a ALV report (not OOP's concept) i want to display changing layout fields in EXCEL sheet. please send if you have sample program.
    please suggest how to solve this problem.
    Thanks and regard
    pavan.

  • HT1040 trying to make an ibook and have 800 photos, want format of 8 photos/page, but default is not that- "create" the initial book from iphoto "album" it loads less than 800 pics and then when i change layout i have blanks.

    trying to make an ibook and have 800 photos, want format of 8 photos/page, but default is not that- "create" the initial book from iphoto "album" it loads less than 800 pics and then when i change layout i have blanks.
    if i clear the book so that it is all blanks and then try to load in the pictures i have it loses the chronology of the pictures that i had established in the album.
    is there a way to import photos into an ibook template and keep the original order of the photos without having to do them one at a time?
    also, is there a way to insert a photo rather than just dragging it? i have tried the cut and paste funciton but it doesn't seem to work, the target site doesn't seem to register with iphoto.
    many thanks for your help.

    Photos are added to book in chronological order.  So if you want to add them to a book in the order you have placed them manually in an album do the following:
    1 - select all the photos in the album.
    2 - use the Photos ➙ Batch Change ➙ Date menu option as shown here. Select any date and add 1 minute between photos.
    3 - select just one photo from the album and create a book from it.
    4 - in the book click on the Options button ➙ Book Settings button and make sure the checkbox for Auto-layout pages is unchecked.
    5 - drag the album with your book photos onto the book icon and they will be imported into the Photos tray of the book in your pre-determined order but not into the pages themselves.
    OT

  • The Visible attribute on alv grid column is not changed after Change Layout

    Setup:
    I have a program that displays output in an ALV grid (using cl_salv_table).
    The ALV grid is displayed within a custom control on a subscreen.
    I have 4 subscreens being used on a tabstrip control.  So I have 4 ALV grids total (one on each subscreen).
    On each ALV grid, I have set the set_layout_change function to true so that the user can hide and unhide columns etc. on each grid via the button on the alv grid toolbar.
    I also allow the user to dowload the contents of all 4 grids to excel.  To do this I have a custom button that when clicked goes to each ALV grid - gets the column metadata (via cl_salv_columns_table-get() ) and checks the visibility to determine if the column should be downloaded or not (via cl_salv_column-is_visible() ) to excel.
    The Problem:
    As I said I have 4 grids being displayed via a tab control.  Let's say the user is on tab 1 and unhides some columns on the alv grid 1 via the Change Layout... button.  And then the user navigates to tab 2.  If they click the download button at that point - when the download code is run and it checks the visibility of the columns on alv grid 1 - the changes that were made via the Change Layout... button have not synchronized yet.  When I call is_visible() for a column that was unhid it still comes back as false. 
    The only way I have found to remedy this is to make the user click on a button on the alv grid's toolbar before navigating to a different tab to force the synchronization between the changes made and the backend column metadata.  However, this is not the best option and requires training for the user that they have to do this for the download to work correctly. 
    The Question:
    1) why is the Change Layout... button not automatically synchronizing the changes it made to the back end?  Is there a way to make it do this?
    2) OR, is there a way that I can force the synchronization within the code and not force the user to click a button on the alv grid?  If there is a way to force the synchronization - where do I put that code?  As far as I can tell, when I switch between tabs - I am unable to catch that action in my PAI events.
    Thanks in advance for any help.

    I was able to resolve this issue with a satisfactory solution.
    In my program I had a local class definition to handle the grids' events.  When the synchronization wasn't working I only had two events defined: for link_click and added_functions. 
    I created another definition for event after_salv_function:
                   on_after_salv_function for event after_salv_function of cl_salv_events importing e_salv_function
    There is no code in the method implementation - but adding this event handler now causes a synchronization to occur after the Change Layout is done.

  • 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

  • Changing labels in /sapapo/sdp94.

    Hi,
      Changing labels in /sapapo/sdp94.
       I want to change the labels in /sapapo/sdp94 for the same i found an exit EXIT_/SAPAPO/SAPLMCP2_006 (APODM006).
       Problem is the control is not reaching the EXIT; i set up a breakpoint over there but still it doesn't reach there.
    Thanks
    AP

    Hello, make sure you activated the user-exits properly. Then you set a BP at FM /SAPAPO/MC_PERDY_GET in SE37 in below coding:
    * User-Exit?
      if i_perly eq 'U'.
    *   Evtl. wurde keine PERID mitgegeben:
        if i_perid is initial.
          call function '/SAPAPO/MC_PERIODE_ZUM_DATUM'
                   exporting
                      idate   = i_vontg
                      iperkz  = i_perkz
                      iperiv  = i_periv
                   importing
                      eperid  = i_perid.
        endif.
        call customer-function '006'
             exporting
                  i_vontg = i_vontg
                  i_bistg = i_bistg
                  i_perkz = i_perkz
                  i_periv = i_periv
                  i_perid = i_perid
             importing
                  e_perdy = e_perdy.
    If the user-exit is applied OK, it will jump into your customizing coding at statement [call customer-function '006']

  • Reg: how to change layout in report writer

    HI all,
    how to change layout in report painter?
    regards
    JK Rao

    Hi everybody,
    I have a report painter using transaction ke30 and I want to change the header layout.
    Now it looks like that
    |_________|_________|
    But i want to add another header row above this row, so it will look like:
    |_________________________|
    |___________|_____________|
    Does anyone know the answer?
    Thanks a lot for your response
    Edited by: Vo Duy Pho on May 24, 2010 10:29 AM
    Edited by: Vo Duy Pho on May 24, 2010 10:37 AM

  • Change layout of Adhoc query output list for Custom infotype

    Hi All,
    The fields in the Infoset query output on a custom infotype are aligned with the fields u2018payment typeu2019 and u2018amountu2019 appearing repeatedly(in columns) as declared in the Infotype and the output will be a long horizontal list.
    Instead, the requirement is that the output list should show vertically so that If I choose u2018Payment Typeu2019 and u2018Amountu2019 as output fields, it will show a long vertical list as in the case of a standard infotype (IT0008).
    Also, this way enables user to use Payment Type as a selection criteria so as to just pulling the needed payment type. When we use IT0008 in the infoset it works fine but in custom IT it does not work.
    Any pointers/suggestions on how we can achieve this would be helpful.

    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...

  • Why does FireFox change layout/settings during upgrades without asking ?

    Just upgraded to Firefox 18 (windows 7 desktop). Why does Firefox change layouts/settings without asking the user if he wants it or not???
    I am getting sick of those changes. I want to have at the google main page the options (as before) to search in all languages, or pages from a certain language or pages in a certain language (of course depening of the google address; f.i. at google.de for german languages, google.fr for french languages etc).
    In the latest Firefox 17 it was working as I wanted and described before: when I visited www.google.de/firefox of www.google.fr/firefox. Now those 3 options (under the search bar) are gone and I do not want to operate by clicking on the advanced search button. Those things should be visible under the search bar again.
    Also my STARTPAGE was GONE/DELETED after the update !!! Grrrrr.... Updating is OK but mozilla should not change user configured items !!!!!!!
    The above described problem has nothing to do with the google website.

    By the way, do Firefox and IE use the same proxy settings? You can view Firefox's here:
    orange Firefox button (or Tools menu) > Options > Advanced > "Network" mini-tab > "Settings" button
    The default is "Use system proxy settings".

  • Problem in changing layout of ALV to excel

    Hello everyone,
    I have developed an ALV program, wherein I need to show the graphs for the same.
    For this, I need my data in excel format, so that I can write some macros ,and do the further processing on it(I am using an appraoch I found on SDN, "Report with graph").
    I got to know, that I need <b>SAP R/3: Add On:Interactive Excel</b>.
    I asked the BASIS guys to install it, but even after installing it, I am unable to view the data in Excel layout, when I do Change LAyout->View->Microsoft Excel.
    Could anyone let me know if there is any other setting which is required to view the data in excel?On the excel side, we can change the security level(Tools->Macro->Security) to either low, medium or high.
    Is there any such provision in SAP?
    Kindly suggest your answers, as it is important for me to get the data in excel.
    Points will be rewarded.
    Thanks and regards,
    Prerna

    Hi,
    I have already tried what you have just mentioned.
    I searched the entire SDN, for this, and this was one of the replies   
    But still we don't get the data(Even you didn't get it, right?).
    when we change the layout to excel(Excel Inplace), there are 2 sheets by default:-
    Rawheader and Rawdata.The data comes in RAwheader sheet.
    But there is some setting on the BASIS side, which need to be done, in order for it to work.
    I have asked my BASIS colleagues and some of my senior consultants to look into the same.
    They will let me know.
    I would also suggest you try your program on another PC.
    I will let you know as soon as I get any replies from my colleagues.
    Thanks and regards,
    Prerna

Maybe you are looking for