Problem adding Photos, changing layout

I'm trying to create a Book and when I change layout or want to change the picture, the page goes blank and can't add/change photos or layout?

Since the new library worked OK indicates that your orignal library is damaged to the point that it's not repairable. We've tried all of the fixes we know about.
This may be your next step which would mean recreating the book from scratch:
Starting over from scratch with new library
Start over with a new library and import the Originals (iPhoto 09 and earlier) or the Masters (iPhoto 11) folder from your original library as follows:
1. Open the library package like this.
2. Launch iPhoto with the Option key held down and, when asked, select the option to create a new library.
3. Drag the subfolders of the Originals (iPhoto 09 and earlier) or the Masters (iPhoto 11) folder from the open iPhoto Library package into the open iPhoto window a few at a time.
This will create a new library with the same Events (but not necessarily the same Event names) as the original library but will not keep the metadata, albums, books slideshows and other projects.
Note:  your current library will be left untouched for further attempts at a fix if so desired.

Similar Messages

  • PodCast: problem adding photos to the Podcast Track!

    Hi all,
    I was just making my 1st podcast when I encountered a strange problem: I wanted to drag&drop photos from the media browser but not all of them worked!
    Some photos could be dropped without a problem (instatntly visible by the green + ball sticking to the mouse pointer) while with others this green + icon doesn't appear and the photo won't drop into the Podcast Track.
    I consulted the GB Help but to no avail.
    However, I observed the following: all my photos in portrait format work and all my photos in landscape format don't work.
    The photos are taken with my DSLR camera and have a resolution of 3008x2000 pixel.
    So, together with the portrait/landscape observation: could it be that 2000 pixel by 2000 pixel is the max size of a photo so that it can be dropped onto the Podcast Track?
    A double click on a photo in the media browser doesn't open GB's own little photo editor (opposed to when you double click on a photo in the markers track list) so one can't crop the photos within GB.
    So, do I need to crop the landscape 3008x2000 images in iPhoto (or any other sim. app.) first?
    Any comments?
    Thanks a lot & cheers from Germany,
    Stefan.

    Hey Stefan,
    A couple of potential issues here. First off you may be right that there's some type of file size limit issue, either because there's a max filesize built-in, or because since you're able to "scale" your photos for display within the chapter/markers area, maybe GB wants a file it knows it can work with reasonably.
    Secondly, I'd be wary of putting lots of large photos in your cast, as that may contribute to giant file sizes on export. The one thing you might want to test is to see what GB does with the photos when you've selected the Preferences>Export>Set Artwork to recommended size for Podcasts check box.
    Or maybe try unchecking that box (if you have it checked now) and then see if a big photo can then be brought in.
    What I've been doing with large photos is exporting them from iPhoto at a smaller scale, then importing them into a new album, or in the case of images from the web, just adding them to iPhoto and scaling them in GB in the chapter markers area. I also use Photoshop to "pre-scale" but I wouldn't think it was necessary just for a Podcast.
    Hopefully this helps.

  • Adding photo to layout

    I'm creating a photobook with Photoshop 9.  I've chosen a layout for my page but the layout only contains 5 pictures and I want to add another picture to the layout.  How do I do that?

      You should be able to drag another photo up from the project bin on to the same page. Use the move tool to position it with the other five. Click in the middle of any photo on the page whilst the move tool is selected and use the corner handles of the bounding box to re-size if necessary.
     

  • Problem adding photos to a photo template page

    I am using iWeb 3.0.4. After selecting a Photo template page I tried to drag an iPhoto event from Media sidebar that has 32 photos in it to the photo place holder on the page. Only 9 of the photos were transferred. Trying to drag any other photos, even a single photo, caused a text box with the name of the photo in it to be placed on the page and the Inspector window to open with the Link tab active.
    Does anyone have any ideas on why or what to do?

    Your library is damaged and my not be able to be totally recovered, i.e. recover albums, slideshows, etc. along with the photos.
    If the original files for your photos are inside the library package (even if iPhoto can't display them) the following should create a new library with all of your photos. 
    Start over from scratch with new library
    Start over with a new library and import the Originals (iPhoto 09 and earlier) or the Masters (iPhoto 11) folder from your original library as follows:
    1.  Move the existing library folder to the desktop.
    2. Open the library package like this.
    Click to view full size
    3. Launch iPhoto and, when asked, select the option to create a new library.
    4. Drag the Originals (iPhoto 09 and earlier) or the Masters (iPhoto 11) folder from the iPhoto Library on the desktop into the open iPhoto window.
    Click to view full size
    This will create a new library with the same Events as the original library but will not keep the metadata, albums, books slideshows and other projects.  Check it out carefully to see if all of your photos are represented in it.
    Your current library will still be available for further fix attempts.

  • Problem: adding soundtrack changes colors

    When I ad a separate soundtrack to a QT movie (exported slideshow from keynote) and save the new combination as an independent QT movie, the colors of the movie change dramatically. Lighter and less contrast. Does anyone know what could be the reason and how it can be avoided ?

    The following seems to work. Main difference is the explicit setting of a contentPane to the frame, and only playing with the contentPane in the constructor.
    Note that your code is commiting some of the Capital Sins of GUI Writing:
    - harcoding colors for large areas
    - hardcoding size for main windows
    - not making main windows resizeable
    The first two should really be in some Properties file. I can't find any excuse for the third.
    public class CookBook1 extends JFrame
         public CookBook1()
              super("Cookbook program thingy");
              JPanel cp=new JPanel();
              setContentPane(cp);
              cp.setLayout(new BorderLayout());
              cp.setMinimumSize(new Dimension(800,600));
              cp.setPreferredSize(new Dimension(800,600));
              cp.setBackground(new Color(164, 199, 235));
              makeMenus();
    // makeMenus() snipped since it the same as yours
         ////////////////////MAIN/////////////////////
         public static void main(String[] args)
              //CookBook1.consoleMenuProgram();
              CookBook1 window = new CookBook1();
              window.setVisible(true);
              window.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
              window.setResizable(false);
              window.pack();

  • Problem adding photos

    I'm trying to use a poster template in pages.  I want to add my own photos instead of the
    placeholder photos.  When I click media to show my photos so I can dray and drop them,
    iPhoto comes up full screen instead of in a column on the right side of my screen. 
    I can't drag and drop photos because it is full screen and covers my template. 
    How do I get my photos in a column on the right side of the screen?

    BW,
    Click the Green Ball in the upper left corner of the Media Browser Window to resize it. Or, grab an edge and resize manually.
    Jerry

  • 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

  • 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/

  • Calendar theme editing?  Changing layout of Calendar photo's.

    I want to rearrange photos on calendar in a slightly rotated layout. That is not perfectly vertical or horizontal. I want to lay them on the calendar in MY arragnement rather than the canned layouts from Apple.
    Is there anyway to rotate photos just a little off horizontal/vertical?
    Is there a way to create MY own Calendar theme?
    Are there other Calendar themes available?

    MacFire21:
    Welcome to the Apple Discussions. What theme are you using and which layout?
    The answer to all of your questions is no. BUT, if you choose a one photo/page layout you can create a collage of the photos you want in the location you want and save as a 4:3 ratio image file an use that. That would take a 3rd party editor however. There is a free one, Seashore, that can do the job. If you plan on doing a lot of advanced editing I recommend Photoshop Elements. It's, IMO, the best consumer editor out there. Here's an example so some of the advanced editing you can do with it.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.

  • [svn:osmf:] 14023: Updating OSMFPlayer to the changed layout APIs, adding a comment, and fixing MediaContainer from ignoring its constructor argument.

    Revision: 14023
    Revision: 14023
    Author:   [email protected]
    Date:     2010-02-07 07:54:38 -0800 (Sun, 07 Feb 2010)
    Log Message:
    Updating OSMFPlayer to the changed layout APIs, adding a comment, and fixing MediaContainer from ignoring its constructor argument.
    Modified Paths:
        osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as
        osmf/trunk/framework/OSMF/org/osmf/containers/MediaContainer.as
        osmf/trunk/framework/OSMF/org/osmf/layout/LayoutTargetSprite.as

  • I have an IPad 2,I have previously had no problem sending photos by email.But now for some reason photos I send are not successfully been sent. I'm not sure if I have changed a setting by mistake. Is there a particular Setting I should be concentrating on

    I would be very appreciative if anyone could give me some advice!I have an IPad 2,I have previosly had no problem sending photos by email.But now for some reason photos I send are not successfully been sent. I'm not sure if I have changed a setting by mistake. Is there a particular Setting I should be concentrating on to making it successfully work again?Cheers!I look forward to hearing back from you!Aussie Fella!

    is this how you send your photo?
                            Tap a photo, album, or event to select it.                    
                            Tap > Email.                                            
                            Confirm or change the photos you want to share by tapping an option.                       
                                  Select all the photos in an album or event: Tap All.                                                        
                                  Select a range of photos: Tap Choose, tap Range, tap the first and last photos in the range, and tap Next.                                                        
                            Type the address of the recipient, add a message, and tap Send.

  • 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

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

  • Change layout controller for permissions in details command

    How can we change layout controller for permissions shown when you select any repository > details > settings > permissions. here only 5 users are shown in the table i wanted to change the layout to see if i can display more than 5 rows but i can not seem to find the iView corresponding to this pop up screen. Any ideas?

    Hi Firasath,
    In the end, this is a modification of the standard, and there are several ways to do such things (and to avoid problems with it, for example when upgrading your installation).
    As this is a complex task, I won't say this and that is the right direction. That's really an individual decision for each customer. I know customers who really have a lot of modifications (and they enjoy their extended functionality), others I know who never ever would touch the SAP code. And many ways are in between...
    Just for a very fast shot (but not advised as a "clean" way), you could decompile the class itself, make it compilable as a Java project consisting of one class (extending the compile classpath to fit the classes needs), do the change, exchange the original class within the JAR by your modified version and restart the portal (for exchanging WinRAR for example can be used very easily).
    A more clean approach would be to import the original PAR as a portal project, decompile the class in question, remove it from the compiled JARs (which have to be added manually into the PAR structure), recompile and redeploy (within the same original namespace).
    A more complicated approach is to try to create a new PAR within a new namespace, so that in the end you are not modifying the original component but just "steal" code from the original component and deploy it independently. But this needs most experience.
    Not understood everything in detail?! In this case, sorry, but: It's really an absolute non-trivial task which only should be done by people having the experience to understand these lines more or less in a second...
    Hope it helps
    Detlev

  • Problem inserting photos in Imovie project

    i have what seems an unusual problem inserting photos into one of my projects. some photos insert fine however others that are dragged into the project dont appear when the video is played. the bar does however appear above the video clip showing that the photo has been inserted and the duration can be toggled.
    i then tried inserting the same photo into another short project and it worked fine?!
    has anyone come across this? would really appreciate your help as trying to put together a video clip for a wedding which is taking place in a few days!!
    many thanks

    I have also tried deleting the com.apple.imovie.plist ... I don't have one to delete ??  And, I tried repairing disk permissions with disk utility ... no change. I have also tried changing the title of the project.  These same pictures can be added into any other project ... I'm going CRAZY!

Maybe you are looking for

  • UCCX 9.0(2) XML question

    I'm teaching myself about SOAP and XML responses for an upcoming project for a self-service application. We have UCCE/ICM UCCX/IPIVR premium licenses. I used the excellent article by Gergely (https://supportforums.cisco.com/document/97736/uccx-8x-rea

  • Import running slow since last days.

    I have a issue where Oracle 9i database import is running very slow since last couple of days. The process used to be completed in 5 hours every day. But since last two days it is taking 10 to 15 hours to complete. I have checked the data-file size,

  • Cannot login in OEM.

    Hi, After installing Oracle9i recently on server, I found that I could not login in Oracle Enterprise Manager. By comparing services in the new and old installation, I found that a service named "OracleOraHome90ManagementServer" is not listed in the

  • When saving a document, pages unexpectedly quit three times in a row.  Any idea why?

    When I was saving a document I previously duplicated, Pages unexpectedly quit three times in a row.  Ideas?

  • Please solve "com.collaxa.cube.engine.EngineException"

    iam using Oracle Soa11g Weblogic 10.3 i use one bpel,mediator,File adapter.Test service is successful but in the instance it shows recover needed <exception class="com.collaxa.cube.engine.EngineException"> Global retry rollback fault thrown. The curr