Issue with Color Management and Print Module

The is a repost per request from a comment on Julieanne Kost's blog...
Having sticky output settings can be useful but now that LR has a color managed workflow, it introduces some problems. For example, if a Proof Copy is created and edited to a particular profile, then that copy is taken into the Print Module, if the output profile that has “stuck” from the previous job does not match you have a problem. It would be nice if the behavior for proof copies would be to automatically match the editing profile or at least warn of a mismatch. And while it is nice to be able to create a Saved Print with all the output parameters, it would be helpful to be able to create saved sets of “Print Job” settings assuming that they will be consistent for a particular printer/ink/paper combination (and whatever “Print Adjustment” you have found to your liking) then easily applied to any image being prepared for output. Perhaps a “save setting” selection under the “Print to:” menu.

So what you propose is the templates are proof copy sensitive and if they are setup for profile A but the proof copy describes profile B, then everything but the template defined profile is honored? I could get behind that idea (but what if one selects multiple VC’s with differing profiles and goes into Print?).
That's pretty much it. It does get complicated quickly as you look at multiple VCs or (and I think we need to start making the distinction between proof copies and ordinary virtual copies) if you bring a mixture of PCs and VCs into the print module. I would suggest that the default behavior be to set output profile of the PC as defined in the PC and retain the "sticky" behavior for ordinary VCs.
I also think that having the ability to save a "Print Copy" may change what we need out of the templates and perhaps their overall function should be re-evaluated.
The VC name should show you the profile used for soft proofing if you have the overlay on. That helps too. My concern are those who work with these VC’s and the text overlay is off.
I'm not getting that behavior. The only place the copy name shows up in the print module is in the filmstrip header. Maybe I have a preference set wrong somewhere... Still, I'd rather the software take care of making the match rather than having to double check to make sure I haven't inadvertently changed the profile somehow (i.e. clicking on a template just to see how it would look on another size paper).

Similar Messages

  • How can I access my parents iCloud account remotely to assist with photo management and printing?

    How can I access my parents iCloud account remotely to assist with photo management and printing?

    I tried that without any luck. I was hoping I could get Apple to reset it for me or delete the account so I could recreate it or at least tell me what is listed as my birth date, the security question answer.

  • Issue with Color Fills and Multiply?

    Hi,
    I use Photoshop 7.0, and yesterday I started having an issue with Color Fills.
    (You may actually have to Say I have a black-and white lineart on the background layer, such as
    this. I double-click on the background layer to make it edit-able.
    I click on the Color Fill button, choose solid color, then pick any color (say we use bright red). I go back to the lineart, move the Color Fill layer to underneath the lineart layer, and fill the Color Fill with black. Normally, it would just create white, however for me it has pink/light red. The same thing also happens for patterns and gradients; it leaves a very faded version of the color on the picture.
    I didn't change any options or settings, however my little brother was playing around with Photoshop, and he may have changed something. Can anyone tell me how to get it so that there is no pink or faded color there?
    Thanks in advance.

    One quick way to fix this is to hold down crtl-alt-shift while Photoshop
    starts up, and reset your prefs to their factory defaults. This will not
    lose any of your work.
    The other way is to look through your various settings. Top of the list is
    whether your new files are being created in RGB or CMYK mode. It should be
    RGB.

  • Issue with Cash Management and liquidity forecast report

    Hello folks,
    I am working with cash management and liquidity forecast reports. While running the report for Cash management, as I drill down to planning levels and induvidual GL accounts for the bank accounts, the figures for GL acounts in report does not tally with actual GL balances. As I drill down to last level, it shows the GL balance display which is different from the values in the report. Can anyone tell me why it does not pick up certain values. I find that certain document type "DZ" values are not picked up by the report. Any suggestions?
    Also, I would like to know is there any way to cross check the values in Liquidity forecast report for sales orders, purchase orders and requisitons through any other report in MM and SD. Would appreciate if someone can respond to mu query.
    Thanks in advance,
    -NK-

    In se38, look for programs starting with RFFD*; there are a few for reconciliation of cash management with SD/MM/GL etc.

  • Issues with colour management when printing since resetting cs5

    I have recently reset my CS5 so that I could attempt to restore my auto color and auto tone options. Since doing this, my color management is very off when printing.  The images are darker, and more saturated than usual, as well as significant colour shifting.  I have tried various printer and computer settings and tests, recalibrating my monitor and printer, and attempting troubleshooting with articles online. I have also tried resetting photoshop again, thinking that I may have thrown off the settings when trying to fix my auto color options. I have also run nozzle and print head checks, and everything has come up fine. I am pretty sure there is something wrong with the photoshop side of the printing. I am kind of at my wits end as I am running out of ideas to resolve this issue.  I am a windows user, and I am printing on a Canon ipf8100.  Please help!

    u are probably not getting much help on this unless you post screenshot of your process (starting with File> Print window)
    remember, Photoshop can print a document correct regardless of how it looks on the monitor (and vice versa: Photoshop can display a document correct regardless of how it prints)
    i recommend getting a known target like the WhackedRGB.jpg and see where the problem is occuring (in Photoshop color management settings, on the monitor, on the printer or both)...

  • Issues with color panel and other windows on right side of flash

    Ok the issue I'm having with flash is that the windows on the right side of my flash window do not snap up when I collapse a window. I am attaching a screen shot to better explain this issue.
    As you can see I have the color panel collapsed up, when I expand this panel and it goes down everything shifts down. however when I collapse it back up a huge gap is left behind in CS5.5 as is displayed in screen shot number 2. In CS4 I never had this problem. I could expand and collapse panels as I saw fit with no problems what so ever. Everytime now that I expand a panel and collapse it, the library or other panels do not move up with the collapsing. This causes a workspace issue. and forces me to drag up the library via the black line that is just above it but below the align panel so that I have better access to my library or properties panel for when I'm working. I find this highly annoying and would like it if there could be a fix produced to make it so this collapsing issue can be fixed and I don't have to waste time dragging up the library/properties panel everytime I need to access stuff in my library when I have a huge list of graphics I'm going through.
    Thanks
    h_cline2

    I already tried that, first thing I thought of before coming to the forums for a solution.
    Thanks anyways.
    Any other ideas?

  • Adobe Reader 9.1.3 Issues with browser viewing and printing

    I have several users reporting issues after upgrading to Adobe Reader 9.1.3
    Issue #1:  User tries to open a PDF on a bank website using Adobe 9.1.3 but receives an error stating file could not be found.  Adobe 9 was uninstalled and Adobe 6 re-installed.  The file on the bank website was then viewable without issue.
    Issue #2:  Different user successfully opens pdf on a different bank website, but is unable to print while viewing in browser using Adobe 9.1.3.  User had to save file to desktop and reopen locally to print from Adobe 9.1.3.   Uninstalling 9.1.3 and re-installing Adobe 6 allowed them to print from the browser successfully.
    Issue #3:  turning off "View in Browser" causes the error "File cannot be found" when trying to view a PDF on a website.  This appears to be happening on sites external to our network, but not on internal sites.  Turning on "View in Browser" corrects the problem.
    Any assistance that can be provided would be greatly appreciated!

    To clarify my previous post, I had already seen http://forums.adobe.com/message/1770581 .  I mentioned in my post that I get the message "Preview not supported" when I click the Preview button from the print dialog in Adobe Reader, and thus concluded that the "Preview" workaround discussed in that thread wasn't helping me.
    However, re-reading that post, they were talking about using the Mac "Preview" application to print the pdf file.  Like every other application (other than Reader) I have tried, the Mac's Preview application prints just fine, and is another workaround.
    The only program that doesn't print for me is Adobe Reader.
    BTW, I also have an Intel chip in my MacBook Pro.
    Re-installing Leopard, as suggested by one post in that thread, is not a reasonable option for this problem.
    In fact, since Preview allows me to view and print .pdf's , my solution is probably just going to be not to use Adobe Reader.  In fact, had I not been new to the Mac, I would have known that I didn't need Adobe Reader at all.
    However, I'm glad this happened, in the sense that I use CS3 on the PC, and had considered moving to CS4 on the Mac.  However, since Adobe apparently hasn't figured out how to get printing to work on a Mac from their flagship product (!), I will be sure to do a lot of testing of CS4 before considering buying the upgrade.

  • Color management and printer dialog

    When I print from PS CS-3 to my Epson R1800 printer I check "Photoshop Manages Color." I immediately get a question, "Did you disable color management in the printer dialog?" I am unable to find where I do this. Can anyone help?

    The paths vary from printer-to-printer or even driver-to-driver for the same printer, but should resemble each other. So, for whatever it's worth, I disable this function for my Epson 1280 via:
    Page Setup > Printer > Properties > Custom > Advanced. There, under "Color Management", I activate the radio button "No Color Adjustment" which I have come to realize means no color management by the PRINTER, without restricting color management by Photoshop. Do you find a similar route for your 1800?

  • Colour Management Issue with PS CS3 and Leopard 10.5.2

    Hi Everyone,
    Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
    My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
    Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
    Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
    Any ideas?
    Thanks.

    >It was working perfectly in Tiger with the monitor profile.
    You were lucky.
    the monitor profile is so Photoshop can display your images correctly.
    the working space is Adobe RGB, sRGB, BruceRGB, ect... these are all known color spaces so when the file goes to another computer there is a consistent color space for reference. If you use your monitor profile as a working space then nobody else knows what is going on with your file.
    when you print you need to use the printer profile for the type of paper you are printing on this is supplied by the printer manufacturer. you can also have custom profiles made.
    you need to read up on color management:
    http://www.gballard.net/psd.html
    http://digitaldog.net/

  • I am trying to print a color photo on my MacBook Pro from iPhoto (not using Photoshop) using Epson 2200 printer, and everything I do in the Color Matching and Print Settings results in a photo with a pink cast to it. What am I doing wrong?

    I am trying to print a color photo on my MacBook Pro from iPhoto (not using Photoshop) using Epson 2200 printer, and everything I do in the Color Matching and Print Settings results in a photo with a pink cast to it. What am I doing wrong?

    Have you checked the ink cartridges and made sure the nozzles are clear? Are you able to print from outside of iPhoto with the correct color?
    Try the following: make temporary copy of the library and do the following:
    1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
         User/Home()/Library/ Preferences folder.
    2 - delete iPhoto's cache file, Cache.db, that is located in your
         User/Home()/Library/Caches/com.apple.iPhoto folder. 
    3 - launch iPhoto and try again.
    NOTE: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding down the Option key when launching iPhoto.  You'll also have to reset the iPhoto's various preferences.
    OT

  • Issue with MacBook Air and nouveau

    Hi.
    I've installed Arch Linux on MacBook Air with Nvidia 320M videocard. Proprietary nvidia driver does not work at all and nouveau has video artefacts (photo attached because screenshot pictures haven't any problems): horizontal noisy black lines and wrong colors on the left two thirds of screen.
    /var/log/Xorg.0.log
    [ 4.374]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 4.374]
    X.Org X Server 1.11.99.903 (1.12.0 RC 3)
    Release Date: 2012-02-11
    [ 4.374] X Protocol Version 11, Revision 0
    [ 4.374] Build Operating System: Linux 3.2.6-2-ARCH x86_64
    [ 4.374] Current Operating System: Linux nikimac 3.2.6-2-ARCH #1 SMP PREEMPT Thu Feb 16 10:10:02 CET 2012 x86_64
    [ 4.374] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/disk/by-uuid/639277e8-a2f3-4313-b3e6-81eeb1453e85 ro init=/bin/systemd quiet
    [ 4.374] Build Date: 18 February 2012 05:06:59PM
    [ 4.374]
    [ 4.374] Current version of pixman: 0.24.4
    [ 4.374] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4.374] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4.374] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 21 16:55:39 2012
    [ 4.380] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4.382] (==) No Layout section. Using the first Screen section.
    [ 4.382] (==) No screen section available. Using defaults.
    [ 4.382] (**) |-->Screen "Default Screen Section" (0)
    [ 4.382] (**) | |-->Monitor "<default monitor>"
    [ 4.382] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 4.382] (==) Automatically adding devices
    [ 4.382] (==) Automatically enabling devices
    [ 4.392] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 4.393] Entry deleted from font path.
    [ 4.402] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 4.402] Entry deleted from font path.
    [ 4.402] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 4.402] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 4.402] Entry deleted from font path.
    [ 4.402] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 4.402] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 4.402] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 4.402] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 4.402] (II) Loader magic: 0x7cf1e0
    [ 4.402] (II) Module ABI versions:
    [ 4.402] X.Org ANSI C Emulation: 0.4
    [ 4.402] X.Org Video Driver: 12.0
    [ 4.402] X.Org XInput driver : 16.0
    [ 4.402] X.Org Server Extension : 6.0
    [ 4.404] (--) PCI:*(0:2:0:0) 10de:08a3:106b:00d3 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00001000/128, BIOS @ 0x????????/131072
    [ 4.404] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 4.404] (II) LoadModule: "extmod"
    [ 4.414] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 4.415] (II) Module extmod: vendor="X.Org Foundation"
    [ 4.415] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.415] Module class: X.Org Server Extension
    [ 4.415] ABI class: X.Org Server Extension, version 6.0
    [ 4.415] (II) Loading extension MIT-SCREEN-SAVER
    [ 4.415] (II) Loading extension XFree86-VidModeExtension
    [ 4.415] (II) Loading extension XFree86-DGA
    [ 4.415] (II) Loading extension DPMS
    [ 4.415] (II) Loading extension XVideo
    [ 4.415] (II) Loading extension XVideo-MotionCompensation
    [ 4.415] (II) Loading extension X-Resource
    [ 4.415] (II) LoadModule: "dbe"
    [ 4.415] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 4.416] (II) Module dbe: vendor="X.Org Foundation"
    [ 4.416] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.416] Module class: X.Org Server Extension
    [ 4.416] ABI class: X.Org Server Extension, version 6.0
    [ 4.416] (II) Loading extension DOUBLE-BUFFER
    [ 4.416] (II) LoadModule: "glx"
    [ 4.416] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 4.419] (II) Module glx: vendor="X.Org Foundation"
    [ 4.419] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.419] ABI class: X.Org Server Extension, version 6.0
    [ 4.419] (==) AIGLX enabled
    [ 4.419] (II) Loading extension GLX
    [ 4.420] (II) LoadModule: "record"
    [ 4.420] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 4.420] (II) Module record: vendor="X.Org Foundation"
    [ 4.420] compiled for 1.11.99.903, module version = 1.13.0
    [ 4.420] Module class: X.Org Server Extension
    [ 4.420] ABI class: X.Org Server Extension, version 6.0
    [ 4.420] (II) Loading extension RECORD
    [ 4.420] (II) LoadModule: "dri"
    [ 4.421] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 4.422] (II) Module dri: vendor="X.Org Foundation"
    [ 4.422] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.422] ABI class: X.Org Server Extension, version 6.0
    [ 4.422] (II) Loading extension XFree86-DRI
    [ 4.422] (II) LoadModule: "dri2"
    [ 4.423] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 4.425] (II) Module dri2: vendor="X.Org Foundation"
    [ 4.425] compiled for 1.11.99.903, module version = 1.2.0
    [ 4.425] ABI class: X.Org Server Extension, version 6.0
    [ 4.425] (II) Loading extension DRI2
    [ 4.425] (==) Matched nouveau as autoconfigured driver 0
    [ 4.425] (==) Matched nvidia as autoconfigured driver 1
    [ 4.425] (==) Matched nv as autoconfigured driver 2
    [ 4.425] (==) Matched vesa as autoconfigured driver 3
    [ 4.425] (==) Matched fbdev as autoconfigured driver 4
    [ 4.425] (==) Assigned the driver to the xf86ConfigLayout
    [ 4.425] (II) LoadModule: "nouveau"
    [ 4.425] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 4.429] (II) Module nouveau: vendor="X.Org Foundation"
    [ 4.429] compiled for 1.11.99.902, module version = 0.0.16
    [ 4.429] Module class: X.Org Video Driver
    [ 4.429] ABI class: X.Org Video Driver, version 12.0
    [ 4.429] (II) LoadModule: "nvidia"
    [ 4.429] (WW) Warning, couldn't open module nvidia
    [ 4.429] (II) UnloadModule: "nvidia"
    [ 4.429] (II) Unloading nvidia
    [ 4.429] (EE) Failed to load module "nvidia" (module does not exist, 0)
    [ 4.429] (II) LoadModule: "nv"
    [ 4.429] (WW) Warning, couldn't open module nv
    [ 4.429] (II) UnloadModule: "nv"
    [ 4.429] (II) Unloading nv
    [ 4.429] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 4.429] (II) LoadModule: "vesa"
    [ 4.429] (WW) Warning, couldn't open module vesa
    [ 4.429] (II) UnloadModule: "vesa"
    [ 4.429] (II) Unloading vesa
    [ 4.429] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 4.430] (II) LoadModule: "fbdev"
    [ 4.430] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 4.431] (II) Module fbdev: vendor="X.Org Foundation"
    [ 4.431] compiled for 1.11.99.903, module version = 0.4.2
    [ 4.431] ABI class: X.Org Video Driver, version 12.0
    [ 4.431] (II) NOUVEAU driver
    [ 4.431] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 4.431] RIVA TNT (NV04)
    [ 4.431] RIVA TNT2 (NV05)
    [ 4.431] GeForce 256 (NV10)
    [ 4.431] GeForce 2 (NV11, NV15)
    [ 4.431] GeForce 4MX (NV17, NV18)
    [ 4.431] GeForce 3 (NV20)
    [ 4.431] GeForce 4Ti (NV25, NV28)
    [ 4.431] GeForce FX (NV3x)
    [ 4.431] GeForce 6 (NV4x)
    [ 4.432] GeForce 7 (G7x)
    [ 4.432] GeForce 8 (G8x)
    [ 4.432] GeForce GTX 200 (NVA0)
    [ 4.432] GeForce GTX 400 (NVC0)
    [ 4.432] (II) FBDEV: driver for framebuffer: fbdev
    [ 4.432] (++) using VT number 7
    [ 4.437] drmOpenDevice: node name is /dev/dri/card0
    [ 5.343] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
    [ 5.343] drmOpenDevice: node name is /dev/dri/card0
    [ 5.343] drmOpenDevice: open result is 7, (OK)
    [ 5.343] drmOpenByBusid: drmOpenMinor returns 7
    [ 5.343] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
    [ 5.343] (II) [drm] nouveau interface version: 0.0.16
    [ 5.343] (WW) Falling back to old probe method for fbdev
    [ 5.343] (II) Loading sub module "fbdevhw"
    [ 5.343] (II) LoadModule: "fbdevhw"
    [ 5.343] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 5.344] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 5.344] compiled for 1.11.99.903, module version = 0.0.2
    [ 5.344] ABI class: X.Org Video Driver, version 12.0
    [ 5.344] (II) Loading sub module "dri"
    [ 5.344] (II) LoadModule: "dri"
    [ 5.344] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 5.344] (II) Module dri: vendor="X.Org Foundation"
    [ 5.344] compiled for 1.11.99.903, module version = 1.0.0
    [ 5.344] ABI class: X.Org Server Extension, version 6.0
    [ 5.344] (II) NOUVEAU(0): Loaded DRI module
    [ 5.344] drmOpenDevice: node name is /dev/dri/card0
    [ 5.344] drmOpenDevice: open result is 8, (OK)
    [ 5.344] drmOpenDevice: node name is /dev/dri/card0
    [ 5.344] drmOpenDevice: open result is 8, (OK)
    [ 5.344] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
    [ 5.344] drmOpenDevice: node name is /dev/dri/card0
    [ 5.344] drmOpenDevice: open result is 8, (OK)
    [ 5.344] drmOpenByBusid: drmOpenMinor returns 8
    [ 5.344] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
    [ 5.344] (II) [drm] DRM interface version 1.4
    [ 5.344] (II) [drm] DRM open master succeeded.
    [ 5.344] (--) NOUVEAU(0): Chipset: "NVIDIA NVaf"
    [ 5.344] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 5.344] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 5.344] (==) NOUVEAU(0): RGB weight 888
    [ 5.344] (==) NOUVEAU(0): Default visual is TrueColor
    [ 5.344] (==) NOUVEAU(0): Using HW cursor
    [ 5.344] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 5.345] (==) NOUVEAU(0): Page flipping enabled
    [ 5.379] (II) NOUVEAU(0): Output eDP-1 has no monitor section
    [ 5.540] (II) NOUVEAU(0): Output DP-1 has no monitor section
    [ 5.559] (II) NOUVEAU(0): EDID for output eDP-1
    [ 5.559] (II) NOUVEAU(0): Manufacturer: APP Model: 9cdf Serial#: 0
    [ 5.559] (II) NOUVEAU(0): Year: 2010 Week: 35
    [ 5.559] (II) NOUVEAU(0): EDID Version: 1.3
    [ 5.559] (II) NOUVEAU(0): Digital Display Input
    [ 5.559] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 29 vert.: 18
    [ 5.559] (II) NOUVEAU(0): Gamma: 2.20
    [ 5.559] (II) NOUVEAU(0): No DPMS capabilities specified
    [ 5.559] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 5.559] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 5.559] (II) NOUVEAU(0): redX: 0.593 redY: 0.342 greenX: 0.331 greenY: 0.573
    [ 5.559] (II) NOUVEAU(0): blueX: 0.152 blueY: 0.133 whiteX: 0.313 whiteY: 0.329
    [ 5.559] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 5.559] (II) NOUVEAU(0): Supported detailed timing:
    [ 5.559] (II) NOUVEAU(0): clock: 91.5 MHz Image Size: 286 x 179 mm
    [ 5.559] (II) NOUVEAU(0): h_active: 1440 h_sync: 1504 h_sync_end 1546 h_blank_end 1652 h_border: 0
    [ 5.559] (II) NOUVEAU(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 926 v_border: 0
    [ 5.559] (II) NOUVEAU(0): Unknown vendor-specific block 1
    [ 5.559] (II) NOUVEAU(0): LP133WP1-TPA1
    [ 5.559] (II) NOUVEAU(0): Monitor name: Color LCD
    [ 5.559] (II) NOUVEAU(0): EDID (in hex):
    [ 5.559] (II) NOUVEAU(0): 00ffffffffffff000610df9c00000000
    [ 5.559] (II) NOUVEAU(0): 23140103801d12780aef059757549227
    [ 5.559] (II) NOUVEAU(0): 22505400000001010101010101010101
    [ 5.559] (II) NOUVEAU(0): 010101010101c223a0d450841a30402a
    [ 5.559] (II) NOUVEAU(0): 36001eb3100000180000000100061030
    [ 5.559] (II) NOUVEAU(0): 00000000000000000a20000000fe004c
    [ 5.559] (II) NOUVEAU(0): 503133335750312d54504131000000fc
    [ 5.559] (II) NOUVEAU(0): 00436f6c6f72204c43440a202020001f
    [ 5.559] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 5.559] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 5.559] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 5.559] (II) NOUVEAU(0): Printing probed modes for output eDP-1
    [ 5.559] (II) NOUVEAU(0): Modeline "1440x900"x59.8 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 5.559] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
    [ 5.559] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
    [ 5.559] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
    [ 5.720] (II) NOUVEAU(0): EDID for output DP-1
    [ 5.720] (II) NOUVEAU(0): Output eDP-1 connected
    [ 5.720] (II) NOUVEAU(0): Output DP-1 disconnected
    [ 5.720] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 5.720] (II) NOUVEAU(0): Output eDP-1 using initial mode 1440x900
    [ 5.720] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 5.720] (--) NOUVEAU(0): Virtual size is 1440x900 (pitch 0)
    [ 5.720] (**) NOUVEAU(0): Driver mode "1440x900": 91.5 MHz (scaled from 0.0 MHz), 55.4 kHz, 59.8 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "1440x900"x59.8 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 5.720] (**) NOUVEAU(0): Driver mode "1152x864": 81.8 MHz (scaled from 0.0 MHz), 53.8 kHz, 60.0 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "800x600": 38.2 MHz (scaled from 0.0 MHz), 37.4 kHz, 59.9 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "640x480": 23.8 MHz (scaled from 0.0 MHz), 29.7 kHz, 59.4 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "720x400": 22.2 MHz (scaled from 0.0 MHz), 24.8 kHz, 59.6 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "640x400": 20.0 MHz (scaled from 0.0 MHz), 25.0 kHz, 60.0 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "640x350": 17.5 MHz (scaled from 0.0 MHz), 21.9 kHz, 59.8 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
    [ 5.720] (**) NOUVEAU(0): Display dimensions: (290, 180) mm
    [ 5.720] (**) NOUVEAU(0): DPI set to (126, 127)
    [ 5.720] (II) Loading sub module "fb"
    [ 5.720] (II) LoadModule: "fb"
    [ 5.720] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 5.721] (II) Module fb: vendor="X.Org Foundation"
    [ 5.721] compiled for 1.11.99.903, module version = 1.0.0
    [ 5.721] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.721] (II) Loading sub module "exa"
    [ 5.721] (II) LoadModule: "exa"
    [ 5.722] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 5.722] (II) Module exa: vendor="X.Org Foundation"
    [ 5.722] compiled for 1.11.99.903, module version = 2.5.0
    [ 5.722] ABI class: X.Org Video Driver, version 12.0
    [ 5.722] (II) Loading sub module "shadowfb"
    [ 5.722] (II) LoadModule: "shadowfb"
    [ 5.722] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 5.723] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 5.723] compiled for 1.11.99.903, module version = 1.0.0
    [ 5.723] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.723] (II) UnloadModule: "fbdev"
    [ 5.723] (II) Unloading fbdev
    [ 5.723] (II) UnloadSubModule: "fbdevhw"
    [ 5.723] (II) Unloading fbdevhw
    [ 5.723] (--) Depth 24 pixmap format is 32 bpp
    [ 5.728] (II) NOUVEAU(0): Opened GPU channel 2
    [ 5.728] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 5.728] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 5.728] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 5.729] (II) NOUVEAU(0): GART: 64MiB available
    [ 5.736] (II) NOUVEAU(0): GART: Allocated 16MiB as a scratch buffer
    [ 5.738] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 5.738] (II) EXA(0): Driver registered support for the following operations:
    [ 5.738] (II) Solid
    [ 5.738] (II) Copy
    [ 5.738] (II) Composite (RENDER acceleration)
    [ 5.738] (II) UploadToScreen
    [ 5.738] (II) DownloadFromScreen
    [ 5.738] (==) NOUVEAU(0): Backing store disabled
    [ 5.738] (==) NOUVEAU(0): Silken mouse enabled
    [ 5.738] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 5.738] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 5.738] (==) NOUVEAU(0): DPMS enabled
    [ 5.738] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 5.738] (--) RandR disabled
    [ 5.738] (II) Initializing built-in extension Generic Event Extension
    [ 5.738] (II) Initializing built-in extension SHAPE
    [ 5.738] (II) Initializing built-in extension MIT-SHM
    [ 5.738] (II) Initializing built-in extension XInputExtension
    [ 5.738] (II) Initializing built-in extension XTEST
    [ 5.738] (II) Initializing built-in extension BIG-REQUESTS
    [ 5.738] (II) Initializing built-in extension SYNC
    [ 5.738] (II) Initializing built-in extension XKEYBOARD
    [ 5.738] (II) Initializing built-in extension XC-MISC
    [ 5.738] (II) Initializing built-in extension SECURITY
    [ 5.738] (II) Initializing built-in extension XINERAMA
    [ 5.738] (II) Initializing built-in extension XFIXES
    [ 5.738] (II) Initializing built-in extension RENDER
    [ 5.738] (II) Initializing built-in extension RANDR
    [ 5.738] (II) Initializing built-in extension COMPOSITE
    [ 5.738] (II) Initializing built-in extension DAMAGE
    [ 5.799] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 5.799] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 5.799] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 5.799] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 5.800] (II) AIGLX: Loaded and initialized nouveau
    [ 5.800] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 5.805] (II) NOUVEAU(0): NVEnterVT is called.
    [ 6.217] (II) NOUVEAU(0): Setting screen physical size to 381 x 238
    [ 6.217] resize called 1440 900
    [ 6.272] (II) XKB: Reusing cached keymap
    [ 6.274] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 6.274] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.274] (II) LoadModule: "evdev"
    [ 6.274] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 6.275] (II) Module evdev: vendor="X.Org Foundation"
    [ 6.275] compiled for 1.11.99.902, module version = 2.6.99
    [ 6.275] Module class: X.Org XInput Driver
    [ 6.275] ABI class: X.Org XInput driver, version 16.0
    [ 6.275] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.275] Option "XkbRules" "evdev"
    [ 6.275] Option "XkbModel" "evdev"
    [ 6.275] Option "XkbLayout" "us"
    [ 6.275] Option "_source" "server/udev"
    [ 6.275] Option "name" "Power Button"
    [ 6.275] Option "path" "/dev/input/event3"
    [ 6.275] Option "device" "/dev/input/event3"
    [ 6.275] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 6.275] Option "driver" "evdev"
    [ 6.275] (**) Power Button: always reports core events
    [ 6.275] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 6.275] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.275] (--) evdev: Power Button: Found keys
    [ 6.275] (II) evdev: Power Button: Configuring as keyboard
    [ 6.275] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 6.275] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 6.275] (**) Option "xkb_rules" "evdev"
    [ 6.275] (**) Option "xkb_model" "evdev"
    [ 6.275] (**) Option "xkb_layout" "us"
    [ 6.301] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
    [ 6.301] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 6.301] (II) Using input driver 'evdev' for 'Video Bus'
    [ 6.301] Option "XkbRules" "evdev"
    [ 6.301] Option "XkbModel" "evdev"
    [ 6.301] Option "XkbLayout" "us"
    [ 6.301] Option "_source" "server/udev"
    [ 6.301] Option "name" "Video Bus"
    [ 6.301] Option "path" "/dev/input/event4"
    [ 6.301] Option "device" "/dev/input/event4"
    [ 6.301] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:2b/LNXVIDEO:00/input/input4/event4"
    [ 6.301] Option "driver" "evdev"
    [ 6.301] (**) Video Bus: always reports core events
    [ 6.301] (**) evdev: Video Bus: Device: "/dev/input/event4"
    [ 6.301] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 6.301] (--) evdev: Video Bus: Found keys
    [ 6.301] (II) evdev: Video Bus: Configuring as keyboard
    [ 6.301] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:2b/LNXVIDEO:00/input/input4/event4"
    [ 6.301] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 6.301] (**) Option "xkb_rules" "evdev"
    [ 6.301] (**) Option "xkb_model" "evdev"
    [ 6.301] (**) Option "xkb_layout" "us"
    [ 6.301] (II) XKB: Reusing cached keymap
    [ 6.301] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 6.302] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.302] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.302] Option "XkbRules" "evdev"
    [ 6.302] Option "XkbModel" "evdev"
    [ 6.302] Option "XkbLayout" "us"
    [ 6.302] Option "_source" "server/udev"
    [ 6.302] Option "name" "Power Button"
    [ 6.302] Option "path" "/dev/input/event1"
    [ 6.302] Option "device" "/dev/input/event1"
    [ 6.302] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 6.302] Option "driver" "evdev"
    [ 6.302] (**) Power Button: always reports core events
    [ 6.302] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 6.302] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.302] (--) evdev: Power Button: Found keys
    [ 6.302] (II) evdev: Power Button: Configuring as keyboard
    [ 6.302] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 6.302] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 6.302] (**) Option "xkb_rules" "evdev"
    [ 6.302] (**) Option "xkb_model" "evdev"
    [ 6.302] (**) Option "xkb_layout" "us"
    [ 6.302] (II) XKB: Reusing cached keymap
    [ 6.302] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
    [ 6.302] (II) No input driver specified, ignoring this device.
    [ 6.302] (II) This device may have been added with another device file.
    [ 6.302] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 6.302] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 6.302] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 6.302] Option "XkbRules" "evdev"
    [ 6.303] Option "XkbModel" "evdev"
    [ 6.303] Option "XkbLayout" "us"
    [ 6.303] Option "_source" "server/udev"
    [ 6.303] Option "name" "Sleep Button"
    [ 6.303] Option "path" "/dev/input/event2"
    [ 6.303] Option "device" "/dev/input/event2"
    [ 6.303] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2/event2"
    [ 6.303] Option "driver" "evdev"
    [ 6.303] (**) Sleep Button: always reports core events
    [ 6.303] (**) evdev: Sleep Button: Device: "/dev/input/event2"
    [ 6.303] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 6.303] (--) evdev: Sleep Button: Found keys
    [ 6.303] (II) evdev: Sleep Button: Configuring as keyboard
    [ 6.303] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2/event2"
    [ 6.303] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 6.303] (**) Option "xkb_rules" "evdev"
    [ 6.303] (**) Option "xkb_model" "evdev"
    [ 6.303] (**) Option "xkb_layout" "us"
    [ 6.303] (II) XKB: Reusing cached keymap
    [ 6.303] (II) config/udev: Adding input device Apple Inc. Apple Internal Keyboard / Trackpad (/dev/input/event10)
    [ 6.303] (**) Apple Inc. Apple Internal Keyboard / Trackpad: Applying InputClass "evdev keyboard catchall"
    [ 6.303] (II) Using input driver 'evdev' for 'Apple Inc. Apple Internal Keyboard / Trackpad'
    [ 6.303] Option "XkbRules" "evdev"
    [ 6.303] Option "XkbModel" "evdev"
    [ 6.303] Option "XkbLayout" "us"
    [ 6.303] Option "_source" "server/udev"
    [ 6.303] Option "name" "Apple Inc. Apple Internal Keyboard / Trackpad"
    [ 6.303] Option "path" "/dev/input/event10"
    [ 6.303] Option "device" "/dev/input/event10"
    [ 6.303] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/input/input10/event10"
    [ 6.304] Option "driver" "evdev"
    [ 6.304] (**) Apple Inc. Apple Internal Keyboard / Trackpad: always reports core events
    [ 6.304] (**) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Device: "/dev/input/event10"
    [ 6.304] (--) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Vendor 0x5ac Product 0x240
    [ 6.304] (--) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Found keys
    [ 6.304] (II) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Configuring as keyboard
    [ 6.304] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/input/input10/event10"
    [ 6.304] (II) XINPUT: Adding extended input device "Apple Inc. Apple Internal Keyboard / Trackpad" (type: KEYBOARD, id 10)
    [ 6.304] (**) Option "xkb_rules" "evdev"
    [ 6.304] (**) Option "xkb_model" "evdev"
    [ 6.304] (**) Option "xkb_layout" "us"
    [ 6.304] (II) XKB: Reusing cached keymap
    [ 6.304] (II) config/udev: Adding input device bcm5974 (/dev/input/event6)
    [ 6.304] (**) bcm5974: Applying InputClass "evdev touchpad catchall"
    [ 6.304] (**) bcm5974: Applying InputClass "Multitouch Touchpad"
    [ 6.304] (II) LoadModule: "multitouch"
    [ 6.304] (II) Loading /usr/lib/xorg/modules/input/multitouch.so
    [ 6.305] (II) Module multitouch: vendor="X.Org Foundation"
    [ 6.305] compiled for 1.11.99.903, module version = 0.1.0
    [ 6.305] Module class: X.Org XInput Driver
    [ 6.305] ABI class: X.Org XInput driver, version 16.0
    [ 6.305] (II) Using input driver 'multitouch' for 'bcm5974'
    [ 6.305] Option "_source" "server/udev"
    [ 6.305] Option "name" "bcm5974"
    [ 6.305] Option "path" "/dev/input/event6"
    [ 6.305] Option "device" "/dev/input/event6"
    [ 6.305] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/event6"
    [ 6.305] Option "driver" "multitouch"
    [ 6.305] (**) bcm5974: always reports core events
    [ 6.306] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/event6"
    [ 6.306] (II) XINPUT: Adding extended input device "bcm5974" (type: TOUCHPAD, id 11)
    [ 6.306] (II) device control: init
    [ 6.306] (**) Option "Device" "/dev/input/event6"
    [ 6.311] (II) multitouch: devname: bcm5974
    [ 6.311] (II) multitouch: devid: 5ac 240 1
    [ 6.311] (II) multitouch: caps: left mtdata ibt
    [ 6.311] (II) multitouch: 0: min: 0 max: 2048
    [ 6.311] (II) multitouch: 1: min: 0 max: 2048
    [ 6.311] (II) multitouch: 2: min: 0 max: 2048
    [ 6.311] (II) multitouch: 3: min: 0 max: 2048
    [ 6.311] (II) multitouch: 4: min: -16384 max: 16384
    [ 6.311] (II) multitouch: 5: min: -4620 max: 5140
    [ 6.311] (II) multitouch: 6: min: -150 max: 6600
    [ 6.336] (II) pointer_control
    [ 6.336] (**) bcm5974: (accel) keeping acceleration scheme 1
    [ 6.336] (II) pointer_property
    [ 6.336] (II) pointer_property
    [ 6.336] (**) bcm5974: (accel) acceleration profile 0
    [ 6.336] (II) pointer_property
    [ 6.336] (II) pointer_property
    [ 6.336] (**) bcm5974: (accel) acceleration factor: 2.000
    [ 6.336] (**) bcm5974: (accel) acceleration threshold: 4
    [ 6.337] (II) device control: on
    [ 6.337] (**) Option "Device" "/dev/input/event6"
    [ 6.342] (II) pointer_property
    [ 6.342] (II) pointer_property
    [ 6.342] (II) config/udev: Adding input device bcm5974 (/dev/input/mouse0)
    [ 6.342] (**) bcm5974: Applying InputClass "Multitouch Touchpad"
    [ 6.342] (II) Using input driver 'multitouch' for 'bcm5974'
    [ 6.342] Option "_source" "server/udev"
    [ 6.342] Option "name" "bcm5974"
    [ 6.342] Option "path" "/dev/input/mouse0"
    [ 6.342] Option "device" "/dev/input/mouse0"
    [ 6.342] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/mouse0"
    [ 6.342] Option "driver" "multitouch"
    [ 6.342] (**) bcm5974: always reports core events
    [ 6.342] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/mouse0"
    [ 6.342] (II) XINPUT: Adding extended input device "bcm5974" (type: TOUCHPAD, id 12)
    [ 6.342] (II) device control: init
    [ 6.342] (**) Option "Device" "/dev/input/mouse0"
    [ 6.342] (EE) multitouch: cannot configure device
    [ 6.342] (EE) Couldn't init device "bcm5974"
    [ 6.342] (II) UnloadModule: "multitouch"
    [ 6.342] (II) config/udev: Adding input device Built-in iSight (/dev/input/event9)
    [ 6.342] (**) Built-in iSight: Applying InputClass "evdev keyboard catchall"
    [ 6.342] (II) Using input driver 'evdev' for 'Built-in iSight'
    [ 6.342] Option "XkbRules" "evdev"
    [ 6.343] Option "XkbModel" "evdev"
    [ 6.343] Option "XkbLayout" "us"
    [ 6.343] Option "_source" "server/udev"
    [ 6.343] Option "name" "Built-in iSight"
    [ 6.343] Option "path" "/dev/input/event9"
    [ 6.343] Option "device" "/dev/input/event9"
    [ 6.343] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.1/usb1/1-6/1-6:1.0/input/input9/event9"
    [ 6.343] Option "driver" "evdev"
    [ 6.343] (**) Built-in iSight: always reports core events
    [ 6.343] (**) evdev: Built-in iSight: Device: "/dev/input/event9"
    [ 6.343] (--) evdev: Built-in iSight: Vendor 0x5ac Product 0x850a
    [ 6.343] (--) evdev: Built-in iSight: Found keys
    [ 6.343] (II) evdev: Built-in iSight: Configuring as keyboard
    [ 6.343] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.1/usb1/1-6/1-6:1.0/input/input9/event9"
    [ 6.343] (II) XINPUT: Adding extended input device "Built-in iSight" (type: KEYBOARD, id 12)
    [ 6.343] (**) Option "xkb_rules" "evdev"
    [ 6.343] (**) Option "xkb_model" "evdev"
    [ 6.343] (**) Option "xkb_layout" "us"
    [ 6.343] (II) XKB: Reusing cached keymap
    [ 6.343] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event7)
    [ 6.343] (II) No input driver specified, ignoring this device.
    [ 6.343] (II) This device may have been added with another device file.
    [ 6.343] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event8)
    [ 6.343] (II) No input driver specified, ignoring this device.
    [ 6.343] (II) This device may have been added with another device file.
    [ 6.344] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event11)
    [ 6.344] (II) No input driver specified, ignoring this device.
    [ 6.344] (II) This device may have been added with another device file.
    [ 6.344] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
    [ 6.344] (II) No input driver specified, ignoring this device.
    [ 6.344] (II) This device may have been added with another device file.
    [ 6.369] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 6.369] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 6.369] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 7.550] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 7.550] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 7.550] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 7.754] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 7.754] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 7.754] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 7.963] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 7.963] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 7.963] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 8.165] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 8.165] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 8.165] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 8.364] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 8.364] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 8.364] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.133] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.133] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.133] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.359] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.359] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.359] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.560] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.560] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.560] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.760] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.760] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.760] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.961] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.961] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.961] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 17.159] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 17.159] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 17.159] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 18.008] (II) pointer_control
    [ 18.830] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 18.830] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 18.830] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    nvidiafb works fine, but it has no dri and has problems with suspend.
    How to resolve this problem with nouveau? Is it crtc-related or not? Playing with xrandr does not have any effect (except resolution change).
    Last edited by nikicat (2012-02-22 15:00:18)

    I had an issue with my MBA seeing my HP printer and could find no good reason for the issue.  In the end I deleted the printers WiFi connection and then turned around and set it up on my WiFi network all over again.  My MBA now finds the printer every time.  Okay ...so I don't actually know why it didn't work the first time, but it does now.  Again, there was no apparent issue with either the HP printer or the MBA being connected to WiFi in the first place, but something different must have occurred in software/hardware the second time. 

  • CS5 Color Calibration and Printing Problems vs. CS3

    We are migrating from CS3 to CS5, and i'm working on getting the printing right.
    We are on MacPro towers, 10.6.6, with LaCie LCD Monitors and an Epson 2200.  Calibration on monitors and printer done by EyeOne Pro and Profilemaker Pro.
    Printing:  In CS3, creating the profile was done by printing the appropriate Eye One testchart.  It gets opened with 'no color management', and is printed out with 'no color management'.  This way, the testfile is being printed as the printer prints, with no tweaks.  The color adjustment controls (brightness, saturation, cyan, magenta, etc) within the Epson driver are set to Zero.  Then, this print is scanned in, using the Eye One, and you get the profile of the printer.
    Now, when printing actual files, 'Photoshop Manages Colors' is utilized, and the created Profile from Eye One is selected.
    We have had great luck with this, matching screen to print.  If a slight tweak is needed, then we could use the Epson color adjustment controls to modify slightly.
    Again, we've had great prints consistently for years using this method.
    Now comes CS5...
    Printing.  Trying to use our existing profile...
    When 'Photoshop Manages Colors' and the Profile are selected, now the Epson color adjustment controls are greyed out.  So, we lose out on the 'tweaking' possibilities.  I'm a fan of profiles, but now i have absolutely no control after the fact.
    Trying to create a new profile....
    'No Color Management' is not longer available as an option in 'Color Handling'.  So, now i can't even print out the baseline testchart without adding some sort of profile to it?  If i would choose 'Printer Manages Color' for this testpage, I would normally set the Epson Color Adjustments to Zero to get this baseline print for profiling.  But now, If I would do that, it's only going to be greyed out when i go back in and let Photoshop manage the colors.  Sheesh...
    To make matters worse...
    I pull up the same testchart in CS3 AND CS5.  We are on a calibrated monitor, using North American Prepress presets on both programs.  Same monitor, same color settings, same file.  AND the testchart looks different in each program.  Similar, but definite differences in shades.  Eyedropper readings are the same for both programs.
    So, CS5 is even rendering color differently on screen, and i have little or no way to create my custom profile or control my printer?  Sheesh....
    Any help or direction is appreciated.
    Rich

    thanks for the input.
    I will look at the links you recommended.  When 'Compensate for Scene-Referred Profiles' is unchecked in CS5, the monitors match.  I'll need to do some research to see that that 'compensation' is, and what's happening.
    As for the 'not considered a good color managed workflow'...
    That's fine.  But I would consider a good managed workflow using a calibrated monitor, and using a profile that matches the printer and substrate being used, right?  When i plug in the canned printer profile in CS5, i get unsatisfactory results.  With that 'correct' workflow, there is no way to modify what is ending up on the printed page.  You get what you get.
    Even if i back up to CS3, create a custom profile with the Eye One, run Colorsync/Profile all the way through, and eliminate the Epson Color Adjustments, I'm still obeying a 'correct' workflow, but what if my prints are slightly too Cyan?  Or slightly too open/light?  (granted, Profilemaker Pro does have a profile 'editor', but it's convoluted and extremely difficult to use.  I've never gotten good results with it.)
    If you have no way to do small adjustments at the back end on the printer, and it's been 'profiled' correctly, and the prints don't match calibrated screen with proper color spaces.... 
    uh....then what do you do?  which one is right?  The screen or the printer? 
    I've had hundreds of images over the years go from screen to client (or press if we were controlling the print phase of the job), which then got printed, and have had basically 'zero' client issues with color.  We have great color here on screen, from capture into post production.
    But when my client wants a proof, in house, they want to see what they've been seeing all day in the studio and in post.  How am I supposed to adjust my prints if a 'proper color managed workflow' isn't giving me matching proofs?
    I sincerely appreciate the input here.  I'm just frustrated, because even if my 'workflow' isn't technically correct, it's not without merits and I've had excellent consistent results that just 'worked'.  Now, i've got to find a new method within CS5.

  • Need help with color management

    I am looking for someone to help me.  Please!
    I am looking for help with Photoshop/printer not printing correct colors.
    I have: Windows 7, Photoshop CS5, Photoshop Elements, HP Pavillion Laptop, new Okidata C530dn color laser printer
    Previously I had a Canon Pixma MP620 and a gentleman from another forum gave me the correct settings for printing on photo paper and colors were perfect.  I now have a OKIdata C530dn color laser and have started a business printing business cards and greeting cards, etc., and I do advertisements on a freelance basis.
    I will be working a lot with cardstock or cover stock 65-110 lbs paper.  I have an old OKIdata 2024e at work, and the colors are much better with that printer than my new personal one.  I have tried matching the settings of that printer to mine to no avail.  I have finally gotten the color close, but not quite.  When I print on my Canon injet the colors match and print perfectly.
    I have tried every setting variation that I can think of to get the color correct with my new OKIdata.  I have to get the colors correct or my new business will go under because I can't match colors for my customers.  I am a self taught Photoshoper and a novice so please bear with me.
    Using Okidata PCL.  Also have PS
    Color settings in Photoshop:
    North America General Purpose 2
    sRGB 2.1
    U.S. Web Coated Swop v2
    Dot gain 20 %
    Dot gain 20 %
    Preserve embeded profile
    Preserve embeded profile
    Preserve embeded profile
    engine: Adobe (ACE)
    Relative Colormetric
    Tried RGB color mode and CMYK color mode, no difference
    Printer settings:
    Photoshop manages colors
    sRGB 2.1 Printer profile
    Relative Colormetric
    Print setup:
    Letter
    Multipurpose tray
    Weight: printer settings-default  (when I used heavy setting for cardstock it printed green instead of the color light blue, so that was a start to the right color)
    Job Options:
    Hight Quality
    Color: No color matching
    Printer preferences in Printer properties:
    Color management
    Device: Display 1 generic PnP monitor AMD M88og with ATI Mobility Radeon HD4200
    ICC Profiles: Generic PnP Monitor (default)
    Advanced:
    Windows Color System Defaults:
    everything under this tab is set at System Default
    I have gotten the color close, but colors are dull. I have tried an adjustment layer and setting the saturation higher, but that doesn't help.  I know my laptop is showing the right colors, (calibrated) because I am still printing to the Canon with cardstock and the colors are perfect using the same settings above.
    Tried printing in PSE and it gave me an error that it was not a post script printer.  Installed ps driver, still getting errors and it wouldn't print.
    I would appreciate any help you could give me before I run out of toner and have to buy the expensive toners, or just slit my wrists j/k  LOL
    Thanks!  JS

    You need an ICC profile for your printer.  Chromix has an excellent service at http://www2.chromix.com/colorvalet/ which will do this calibration for you.  You download some software they provide, then print a test file on the exact same paper you are using for your cards.  Then send the output to them and they will calibrate the colors with their equipment and send you the ICC profile file.  Once you have it, you'll be able to print accurate colors.
    There are other services out there that may cost less, but I do not know how reputable they are.  Chromix is a good business I've worked with many times.
    If you are trying to run a business and you don't understand color management yet, you may be in for a lot of trouble.  Please get the book "Real World Color Management" available at http://www.colorremedies.com/realworldcolor/ and it will save you a ton of money and headaches.

  • 'The monitor profile "LCD color management and conversion" PSE6

    Does anyone know how to correct this?  I can find older posts  but they date back too far.  Where they say to go and what do has changed since.
    The monitor profile LCD color management and conversion appears to be defective.  Please rerun your monitor calibration software.
    Everything dispalys in a cream color background and nothing prints correct color.  I have PSE6.

    todls1:
    I'm guessing this message appears when you start the PSE6 Editor?
    If so, what you should select is Ignore, and check the box to not show the message again. (Alternatively, you can remove the profile. If you wish to do this, tell me what edition of Windows you have and I can provide instructions.)
    Essentially, you have a profile installed for your computer's monitor, either installed automatically by Windows Updates, it came with your computer, or it was installed with a driver (or piece of software) for your monitor.
    This type of profile is "generic" and does not contain color calibration information.
    Elements looks for profiles assigned to your monitor, because if the profile was created as part of a color calibration process, then that profile contains information that will help Elements to ensure that the colors you see on the screen are accurate.
    Color is a complicated topic, especially when you introduce computer monitors, but suffice it to say that each monitor has various things that can make it display the same image in a way that's different from every other monitor. These things can include age of the monitor, the specific settings (e.g. contrast, brightness, etc.) of the monitor, and the lighting conditions in the room. When you calibrate a monitor using specialized calibration hardware/software, the calibration software creates a profile that tells programs on your computer (like Elements) about all these factors and how to compensate for them to ensure everything is displayed correctly.
    Sorry for what may seem a long-winded explanation, but just understand that using the "generic" profile instead of one created by specialized calibration equipment has caused colors to appear incorrectly in Elements and are likely contributing to the problem when printing. This is why you should select Ignore.

  • Turn off color management in printer driver?

    Hello folks:
    When I select an icc color profile in Aperture 3 in the Print dialog box, a warning pops up that says "Turn off Color Management in the Printer Driver." I have an Epson R2880, but for the life of me I cannot find a way to turn it off in the driver. Any thoughts? The Epson Printer Utility is also of no help.
    Thank you!
    --David

    Understanding that I have not actually used ColorJunki:
    -- A printer is always going to have something manage color. Either an ICC profile at the application level, or the printer driver.
    -- The warning is poorly worded. It means "Turn off the PRINTER color management and let Colorsync manage colors." Thus on the greyed out screen you will see that Colorsync is selected.
    -- To use a printer profiler you normally print a target sheet. Your software should tell you what settings to use.
    -- Next you read the target sheet and the profiler makes you an ICC profile of your printer/paper combination. (The same process that Canon, Epson, Red River, Illford, et al. follow.)
    -- You can now use your new, ColorMunki created ICC profile to soft proof your image as you adjust it and, finally,
    -- You use that same profile to print. (Remember, the profile is specific to a printer/paper combination and you will still have to set Quality/Media correctly for the paper.)
    By selecting the correct ICC profile on the first print screen, you automatically kill printer color management and, with a bit of luck, a good profile, and clement atmospheric conditions, you will actually get a good print.
    Trust me on this, I have been getting great prints from Aperture for years. My only gripe is that AP3 no longer lets me at the color options which I used to tweak for my cheap and cheerful Costco paper.

Maybe you are looking for

  • Changing Invoice Numbers in AP

    When we run the Supplier Merge Program any Invoices that have duplicate Invoice Numbers are not automatically merged! What we need to do is to change the original Invoice number and then run the Merge program once again. We have enabled the Allow Adj

  • How to maintain EXIF information when exporting

    I've recently posted 2 photos on Flickr, afterhaving edited them in LR5.  Suddenly, might EXIF information is not showing under Addition Info.  I haven't altered anything in my Flickr settings.  Someone has suggested it could my export settings in LR

  • Flash version of Windows Media Player

    Anyone know where you can get a flash player like the one on this site?? http://www.jeejuh.com/ The player is awesome, i've seen it on a few sites making me think that you can buy it rather than it being custom made. Thanks :-)

  • I cannot get apps on my iPad two.

    I need help with my Apple ID and apps. One problem is that I try to download an app, but it says I did not use my Apple ID in the iTunes Store. I press review, then it says that it timed out. My second problem is that I can't access my Apple ID for M

  • Settlement of Refurbishment Order?

    Dear SAPIENTS, I have created Refurbishment  and processed the refurbishment order and now when i am going to settle the maintenance order its giving me the error Final delivery not entered for the order. It is not technically completed . But I have