Dolphin-emu Warning - iCCP: known incorrect sRGB profile

I get this message when I start dolphin-emu and when I start a rom. It does not seem to affect the game in any real way that I can tell. I figured I could just rebuild dolphin-emu from abs and maybe that would fix the error but it wouldn't build. It was failing on building "audiocommon". This error just started coming up recently after the updates yesterday. I can't figure this one out. Here is yesterdays updates:
[2013-05-07 16:24] [PACMAN] upgraded alsa-lib (1.0.27-1 -> 1.0.27-2)
[2013-05-07 16:24] [ALPM] warning: /usr/lib/avahi/service-types.db installed as /usr/lib/avahi/service-types.db.pacnew
[2013-05-07 16:24] [PACMAN] upgraded avahi (0.6.31-6 -> 0.6.31-7)
[2013-05-07 16:24] [PACMAN] upgraded libpng (1.5.15-1 -> 1.6.2-3)
[2013-05-07 16:24] [PACMAN] upgraded cairo (1.12.14-3 -> 1.12.14-4)
[2013-05-07 16:24] [PACMAN] upgraded cairomm (1.10.0-2 -> 1.10.0-3)
[2013-05-07 16:24] [PACMAN] upgraded libwebp (0.3.0-1 -> 0.3.0-3)
[2013-05-07 16:24] [PACMAN] upgraded chromium (26.0.1410.63-1 -> 26.0.1410.63-2)
[2013-05-07 16:24] [PACMAN] upgraded imagemagick (6.8.4.10-1 -> 6.8.5.3-1)
[2013-05-07 16:24] [PACMAN] upgraded dvdauthor (0.7.1-4 -> 0.7.1-5)
[2013-05-07 16:24] [PACMAN] upgraded feh (2.9.1-1 -> 2.9.2-1)
[2013-05-07 16:24] [PACMAN] upgraded ffmpegthumbnailer (2.0.8-2 -> 2.0.8-3)
[2013-05-07 16:24] [ALPM-SCRIPTLET] gtk-update-icon-cache: error while loading shared libraries: libpng15.so.15: cannot open shared object file: No such file or directory
[2013-05-07 16:24] [PACMAN] upgraded firefox (20.0.1-2 -> 20.0.1-5)
[2013-05-07 16:24] [ALPM-SCRIPTLET] g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: libpng15.so.15: cannot open shared object file: No such file or directory
[2013-05-07 16:24] [PACMAN] upgraded gdk-pixbuf2 (2.28.1-1 -> 2.28.1-2)
[2013-05-07 16:24] [PACMAN] upgraded gegl (0.2.0-7 -> 0.2.0-8)
[2013-05-07 16:24] [PACMAN] upgraded lib32-libpng (1.5.15-1 -> 1.6.2-1)
[2013-05-07 16:24] [PACMAN] upgraded lib32-cairo (1.12.14-3 -> 1.12.14-4)
[2013-05-07 16:24] [PACMAN] upgraded lib32-pango (1.34.0-1 -> 1.34.0-2)
[2013-05-07 16:24] [PACMAN] upgraded lib32-gdk-pixbuf2 (2.28.1-1 -> 2.28.1-2)
[2013-05-07 16:24] [PACMAN] upgraded lib32-gtk2 (2.24.17-1 -> 2.24.17-2)
[2013-05-07 16:24] [PACMAN] upgraded gens-gs (2.16.7-2 -> 2.16.7-4)
[2013-05-07 16:24] [ALPM-SCRIPTLET] g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: libpng15.so.15: cannot open shared object file: No such file or directory
[2013-05-07 16:24] [PACMAN] upgraded libwmf (0.2.8.4-9 -> 0.2.8.4-10)
[2013-05-07 16:24] [PACMAN] upgraded librsvg (2.37.0-1 -> 2.37.0-2)
[2013-05-07 16:24] [PACMAN] upgraded gimp (2.8.4-1 -> 2.8.4-2)
[2013-05-07 16:24] [PACMAN] upgraded gstreamer0.10-bad (0.10.23-3 -> 0.10.23-4)
[2013-05-07 16:24] [PACMAN] upgraded mjpegtools (2.0.0-2 -> 2.0.0-3)
[2013-05-07 16:24] [PACMAN] upgraded gstreamer0.10-bad-plugins (0.10.23-3 -> 0.10.23-4)
[2013-05-07 16:24] [PACMAN] upgraded gstreamer0.10-good (0.10.31-1 -> 0.10.31-3)
[2013-05-07 16:24] [PACMAN] upgraded imlib2 (1.4.5-2 -> 1.4.5-4)
[2013-05-07 16:24] [PACMAN] upgraded poppler (0.22.3-2 -> 0.22.3-3)
[2013-05-07 16:24] [PACMAN] upgraded poppler-glib (0.22.3-2 -> 0.22.3-3)
[2013-05-07 16:24] [PACMAN] upgraded inkscape (0.48.4-6 -> 0.48.4-7)
[2013-05-07 16:24] [PACMAN] upgraded iproute2 (3.8.0-1 -> 3.9.0-1)
[2013-05-07 16:24] [PACMAN] upgraded qt4 (4.8.4-16 -> 4.8.4-17)
[2013-05-07 16:25] [PACMAN] upgraded keepassx (0.4.3-4 -> 0.4.3-5)
[2013-05-07 16:25] [PACMAN] upgraded libreoffice-en-US (4.0.2-3 -> 4.0.2-4)
[2013-05-07 16:25] [PACMAN] upgraded libreoffice-common (4.0.2-3 -> 4.0.2-4)
[2013-05-07 16:25] [PACMAN] upgraded libreoffice-calc (4.0.2-3 -> 4.0.2-4)
[2013-05-07 16:25] [PACMAN] upgraded libreoffice-gnome (4.0.2-3 -> 4.0.2-4)
[2013-05-07 16:25] [PACMAN] upgraded libreoffice-writer (4.0.2-3 -> 4.0.2-4)
[2013-05-07 16:25] [PACMAN] upgraded libwbclient (4.0.5-1 -> 4.0.5-2)
[2013-05-07 16:25] [PACMAN] upgraded linux-firmware (20121118-1 -> 20130430-1)
[2013-05-07 16:25] [PACMAN] upgraded logrotate (3.8.3-1 -> 3.8.4-1)
[2013-05-07 16:25] [PACMAN] upgraded smbclient (4.0.5-1 -> 4.0.5-2)
[2013-05-07 16:25] [PACMAN] upgraded mencoder (35920-1 -> 35920-2)
[2013-05-07 16:25] [PACMAN] upgraded mkinitcpio (0.13.0-1 -> 0.14.0-1)
[2013-05-07 16:25] [PACMAN] upgraded mplayer (35920-1 -> 35920-2)
[2013-05-07 16:25] [PACMAN] upgraded mupen64plus (1.99.5-4 -> 1.99.5-6)
[2013-05-07 16:25] [PACMAN] upgraded ntp (4.2.6.p5-13 -> 4.2.6.p5-14)
[2013-05-07 16:25] [PACMAN] upgraded poppler-qt (0.22.3-2 -> 0.22.3-3)
[2013-05-07 16:25] [PACMAN] upgraded qtwebkit (2.3.1-1 -> 2.3.1-2)
[2013-05-07 16:25] [PACMAN] upgraded sdl_image (1.2.12-2 -> 1.2.12-3)
[2013-05-07 16:25] [PACMAN] upgraded thunderbird (17.0.5-1 -> 17.0.5-2)
[2013-05-07 16:25] [PACMAN] upgraded tumbler (0.1.27-2 -> 0.1.29-1)
[2013-05-07 16:25] [PACMAN] upgraded virtualbox (4.2.12-1 -> 4.2.12-2)
[2013-05-07 16:25] [PACMAN] upgraded wv (1.2.9-1 -> 1.2.9-2)
[2013-05-07 16:25] [PACMAN] upgraded wxgtk (2.8.12.1-4 -> 2.8.12.1-5)
[2013-05-07 16:25] [PACMAN] upgraded wxgtk2.9 (2.9.4-2 -> 2.9.4-3)
[2013-05-07 16:25] [PACMAN] upgraded zsnes (1.51-16 -> 1.51-17)
[2013-05-07 16:25] [PACMAN] Running 'pacman -Syuw --noconfirm'
[2013-05-07 16:25] [PACMAN] synchronizing package lists
[2013-05-07 16:25] [PACMAN] starting full system upgrade
[2013-05-07 16:25] [PACMAN] Running 'pacman -Su'
[2013-05-07 16:25] [PACMAN] starting full system upgrade
[2013-05-07 16:35] [PACMAN] Running 'pacman -Syu'
[2013-05-07 16:35] [PACMAN] synchronizing package lists
[2013-05-07 16:35] [PACMAN] starting full system upgrade
[2013-05-07 16:40] [PACMAN] Running 'pacman -S imagemagick'
[2013-05-07 16:40] [PACMAN] reinstalled imagemagick (6.8.5.3-1)
[2013-05-07 16:51] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/libpng-1.5.15-1-x86_64.pkg.tar.xz'
[2013-05-07 16:51] [PACMAN] downgraded libpng (1.6.2-3 -> 1.5.15-1)
[2013-05-07 16:52] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/lib32-libpng-1.5.15-1-x86_64.pkg.tar.xz'
[2013-05-07 16:52] [PACMAN] downgraded lib32-libpng (1.6.2-1 -> 1.5.15-1)
[2013-05-07 16:52] [PACMAN] Running 'pacman -Syu'
[2013-05-07 16:52] [PACMAN] synchronizing package lists
[2013-05-07 16:52] [PACMAN] starting full system upgrade
[2013-05-07 16:53] [ALPM-SCRIPTLET] gtk-update-icon-cache: error while loading shared libraries: libpng16.so.16: cannot open shared object file: No such file or directory
[2013-05-07 16:53] [PACMAN] upgraded gnome-icon-theme-symbolic (3.8.0.1-1 -> 3.8.0.1-2)
[2013-05-07 16:53] [PACMAN] upgraded libpng (1.5.15-1 -> 1.6.2-3)
[2013-05-07 16:53] [PACMAN] upgraded lib32-libpng (1.5.15-1 -> 1.6.2-1)
[2013-05-07 18:45] [PACMAN] Running 'pacman -Syu'
[2013-05-07 18:45] [PACMAN] synchronizing package lists
[2013-05-07 18:47] [PACMAN] Running 'pacman -Syuw --noconfirm'
[2013-05-07 18:47] [PACMAN] synchronizing package lists
[2013-05-07 18:47] [PACMAN] starting full system upgrade
[2013-05-07 18:47] [PACMAN] Running 'pacman -Su'
[2013-05-07 18:47] [PACMAN] starting full system upgrade
[2013-05-07 19:51] [PACMAN] Running 'pacman -S gdk-pixbuf2'
[2013-05-07 19:51] [PACMAN] reinstalled gdk-pixbuf2 (2.28.1-2)
[2013-05-07 19:55] [PACMAN] Running 'pacman -S dolphin-emu'
[2013-05-07 19:55] [PACMAN] reinstalled dolphin-emu (1:3.5-3)
[2013-05-07 20:11] [PACMAN] Running 'pacman -S cairo cairomm lib32-cairo'
[2013-05-07 20:11] [PACMAN] reinstalled cairo (1.12.14-4)
[2013-05-07 20:11] [PACMAN] reinstalled cairomm (1.10.0-3)
[2013-05-07 20:11] [PACMAN] reinstalled lib32-cairo (1.12.14-4)
[2013-05-07 23:35] [PACMAN] Running 'pacman -Syuw --noconfirm'
[2013-05-07 23:35] [PACMAN] synchronizing package lists
[2013-05-07 23:35] [PACMAN] starting full system upgrade
[2013-05-07 23:35] [PACMAN] Running 'pacman -Su'
[2013-05-07 23:35] [PACMAN] starting full system upgrade
[2013-05-07 23:36] [PACMAN] Running 'pacman -S cmake glproto opencl-headers'
[2013-05-07 23:37] [PACMAN] installed cmake (2.8.10.2-5)
[2013-05-07 23:37] [PACMAN] installed glproto (1.4.16-1)
[2013-05-07 23:37] [PACMAN] installed opencl-headers (1:1.1.20110526-1)
I tried reinstalling a few packages at the end there. No luck. Here is "ldd `which dolphin-emu`" :
linux-vdso.so.1 (0x00007fff337fe000)
liblzo2.so.2 => /usr/lib/liblzo2.so.2 (0x00007f0c725e4000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f0c723ce000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f0c7217f000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00007f0c71ecd000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00007f0c718a0000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f0c71567000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f0c7135d000)
libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0x00007f0c710c5000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f0c70ea9000)
libwx_gtk2u_core-2.9.so.4 => /usr/lib/libwx_gtk2u_core-2.9.so.4 (0x00007f0c7067b000)
libwx_gtk2u_aui-2.9.so.4 => /usr/lib/libwx_gtk2u_aui-2.9.so.4 (0x00007f0c703e8000)
libwx_gtk2u_adv-2.9.so.4 => /usr/lib/libwx_gtk2u_adv-2.9.so.4 (0x00007f0c6fff8000)
libwx_baseu-2.9.so.4 => /usr/lib/libwx_baseu-2.9.so.4 (0x00007f0c6fb61000)
libbluetooth.so.3 => /usr/lib/libbluetooth.so.3 (0x00007f0c6f944000)
libportaudio.so.2 => /usr/lib/libportaudio.so.2 (0x00007f0c6f715000)
libCg.so => /usr/lib/libCg.so (0x00007f0c6e23c000)
libCgGL.so => /usr/lib/libCgGL.so (0x00007f0c72875000)
libGLEW.so.1.9 => /usr/lib/libGLEW.so.1.9 (0x00007f0c6dfb6000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f0c6ddb2000)
libGLU.so.1 => /usr/lib/libGLU.so.1 (0x00007f0c6db33000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f0c6d810000)
libavcodec.so.54 => /usr/lib/libavcodec.so.54 (0x00007f0c6c894000)
libavformat.so.54 => /usr/lib/libavformat.so.54 (0x00007f0c6c52c000)
libswscale.so.2 => /usr/lib/libswscale.so.2 (0x00007f0c6c2d8000)
libavutil.so.52 => /usr/lib/libavutil.so.52 (0x00007f0c6c0a4000)
libasound.so.2 => /usr/lib/libasound.so.2 (0x00007f0c6bdad000)
libao.so.4 => /usr/lib/libao.so.4 (0x00007f0c6bba4000)
libopenal.so.1 => /usr/lib/libopenal.so.1 (0x00007f0c6b94c000)
libpulse.so.0 => /usr/lib/libpulse.so.0 (0x00007f0c6b702000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f0c6b3fe000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f0c6b100000)
libgomp.so.1 => /usr/lib/libgomp.so.1 (0x00007f0c6aef2000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f0c6ab45000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f0c6a847000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f0c6a5e4000)
libffi.so.6 => /usr/lib/libffi.so.6 (0x00007f0c6a3dc000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00007f0c6a1cf000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00007f0c69f84000)
libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f0c69c2a000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f0c699ee000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f0c697e3000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00007f0c695e0000)
libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f0c693d0000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f0c691c6000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f0c68fc3000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f0c68dc0000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f0c68bb9000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00007f0c68996000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f0c68675000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f0c68462000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f0c6825e000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00007f0c6803b000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00007f0c67e26000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f0c67c07000)
/lib64/ld-linux-x86-64.so.2 (0x00007f0c72805000)
libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x00007f0c67a01000)
libSM.so.6 => /usr/lib/libSM.so.6 (0x00007f0c677f9000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f0c675c4000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f0c67373000)
libtiff.so.5 => /usr/lib/libtiff.so.5 (0x00007f0c67100000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f0c66eea000)
libjack.so.0 => /usr/lib/libjack.so.0 (0x00007f0c66ccd000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007f0c66ac5000)
libXmu.so.6 => /usr/lib/libXmu.so.6 (0x00007f0c668ab000)
libnvidia-tls.so.313.30 => /usr/lib/libnvidia-tls.so.313.30 (0x00007f0c666a8000)
libnvidia-glcore.so.313.30 => /usr/lib/libnvidia-glcore.so.313.30 (0x00007f0c641a5000)
libxvidcore.so.4 => /usr/lib/libxvidcore.so.4 (0x00007f0c63e8d000)
libx264.so.129 => /usr/lib/libx264.so.129 (0x00007f0c63b3e000)
libvpx.so.1 => /usr/lib/libvpx.so.1 (0x00007f0c6389e000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00007f0c633cf000)
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f0c631a2000)
libtheoraenc.so.1 => /usr/lib/libtheoraenc.so.1 (0x00007f0c62f65000)
libtheoradec.so.1 => /usr/lib/libtheoradec.so.1 (0x00007f0c62d4a000)
libspeex.so.1 => /usr/lib/libspeex.so.1 (0x00007f0c62b31000)
libschroedinger-1.0.so.0 => /usr/lib/libschroedinger-1.0.so.0 (0x00007f0c62866000)
libopus.so.0 => /usr/lib/libopus.so.0 (0x00007f0c62625000)
libopenjpeg.so.1 => /usr/lib/libopenjpeg.so.1 (0x00007f0c623fd000)
libopencore-amrwb.so.0 => /usr/lib/libopencore-amrwb.so.0 (0x00007f0c621e9000)
libopencore-amrnb.so.0 => /usr/lib/libopencore-amrnb.so.0 (0x00007f0c61fbf000)
libmp3lame.so.0 => /usr/lib/libmp3lame.so.0 (0x00007f0c61d48000)
libgsm.so.1 => /usr/lib/libgsm.so.1 (0x00007f0c61b3d000)
librtmp.so.0 => /usr/lib/librtmp.so.0 (0x00007f0c61921000)
libmodplug.so.1 => /usr/lib/libmodplug.so.1 (0x00007f0c61650000)
libbluray.so.1 => /usr/lib/libbluray.so.1 (0x00007f0c61422000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f0c61212000)
libjson.so.0 => /usr/lib/libjson.so.0 (0x00007f0c61008000)
libpulsecommon-3.0.so => /usr/lib/pulseaudio/libpulsecommon-3.0.so (0x00007f0c60da0000)
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f0c60b59000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007f0c60957000)
libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f0c606c3000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f0c60423000)
libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f0c6020c000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f0c5ffe2000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f0c5fd4a000)
libEGL.so.1 => /usr/lib/libEGL.so.1 (0x00007f0c5fb27000)
libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00007f0c5f924000)
libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f0c5f71a000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f0c5f516000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f0c5f310000)
libICE.so.6 => /usr/lib/libICE.so.6 (0x00007f0c5f0f4000)
libuuid.so.1 => /usr/lib/libuuid.so.1 (0x00007f0c5eeef000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f0c5eccc000)
libXt.so.6 => /usr/lib/libXt.so.6 (0x00007f0c5ea66000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f0c5e860000)
liborc-0.4.so.0 => /usr/lib/liborc-0.4.so.0 (0x00007f0c5e5dd000)
libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0x00007f0c5e371000)
libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007f0c5df67000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f0c5dc0b000)
libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x00007f0c5d9a5000)
libasyncns.so.0 => /usr/lib/libasyncns.so.0 (0x00007f0c5d79f000)
libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f0c5d580000)
libicule.so.51 => /usr/lib/libicule.so.51 (0x00007f0c5d335000)
libicuuc.so.51 => /usr/lib/libicuuc.so.51 (0x00007f0c5cfbf000)
libicudata.so.51 => /usr/lib/libicudata.so.51 (0x00007f0c5b877000)
libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007f0c5b675000)
libxcb-dri2.so.0 => /usr/lib/libxcb-dri2.so.0 (0x00007f0c5b470000)
libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0x00007f0c5b269000)
libxcb-shape.so.0 => /usr/lib/libxcb-shape.so.0 (0x00007f0c5b065000)
libwayland-client.so.0 => /usr/lib/libwayland-client.so.0 (0x00007f0c5ae59000)
libwayland-server.so.0 => /usr/lib/libwayland-server.so.0 (0x00007f0c5ac47000)
libgbm.so.1 => /usr/lib/libgbm.so.1 (0x00007f0c5aa41000)
libglapi.so.0 => /usr/lib/libglapi.so.0 (0x00007f0c5a81b000)
libudev.so.1 => /usr/lib/libudev.so.1 (0x00007f0c5a609000)
libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f0c5a3fd000)
libFLAC.so.8 => /usr/lib/libFLAC.so.8 (0x00007f0c5a1b2000)
libnsl.so.1 => /usr/lib/libnsl.so.1 (0x00007f0c59f9a000)
I tried building dolphin-emu-git from the aur and while that package will build it still shows the error. So the problem must lie somewhere else. Is anyone else experiencing this problem?

Hi all,
(before anything, I'm talking about PlayOnLinux, not Dolphin. I'm putting this here since it's the same underlying issue and I've seen other related posts redirected to this one — also, it's my first post so do tell me if I'm doing anything out of place)
PlayOnLinux has the same issue, and it's complicated further by two factors: it uses third-party resources for icons (for instance, a "IDAT: […]" warning is caused by Steam's icon, not by POL itself) and it doesn't use the .png extension for them, so you can't search for them easily. It's not something upstream can fix, and I got fed up with the warning pop-ups so I came with a fix that should work with any bad PNG files, regardless of the program managing them, PlayOnLinux or Dolphin or VirtualBox or anything else.
Ensure you have ImageMagick installed then in a terminal, go to the directory you assume is causing these warnings and:
TP=`mktemp -d`; find . -exec file {} \; | grep PNG | sed 's/: .*//' | while read pngf; do identify "$pngf" 2>&1 >&-; done | sed 's/.*`\(.*\)'"'.*/\1/" | while read badf; do mkdir -p "$TP/`dirname \"$badf\"`"; convert "$badf" "$TP/$badf" 2>&-; mv "$TP/$badf" "$badf"; done; rm -r "$TP"
Just to be sure, I'd suggest running this beforehand:
TP=`mktemp -d`; find . -exec file {} \; | grep PNG | sed 's/: .*//' | while read pngf; do identify "$pngf" 2>&1 >&-; done | sed 's/.*`\(.*\)'"'.*/\1/" | while read badf; do mkdir -p "$TP/`dirname \"$badf\"`"; convert "$badf" "$TP/$badf" 2>&-; echo mv \""$TP/$badf"\" \""$badf"\"; done
It's the same batch, except the only potentially destructive command, mv, is echoed (with args quoted) and the temp dir is not removed in the end. Read the output to ensure my command isn't flawed (the file moves look good). You should also check if the files in $TP look the same than their original.
Here's the detail:
TP=`mktemp -d` # make a temp dir for the fixed files
find . -exec file {} \; | # get the real type of any files inside the current directory (disregarding the extension)
grep PNG | # filter those which are not PNG
sed 's/: .*//' | # extract the filename from `file` output
while read pngf; do # for each PNG file
identify "$pngf" 2>&1 >&- # check if the file is alright: discard stdout and keep stderr, which should contain the filename of the files to fix
done |
sed 's/.*`\(.*\)'"'.*/\1/" | # extract the filename from the warning
while read badf; do # for each file to fix
mkdir -p "$TP/`dirname \"$badf\"`" # if necessary, create a similar subtree inside the temp dir
convert "$badf" "$TP/$badf" 2>&- # create a fixed copy of the file in the temp dir (discard stderr as it will give the same warning as `identify` above)
mv "$TP/$badf" "$badf" # overwrite the bad file with the fixed file
done
rm -r "$TP" # delete the temp dir
Of course, 1. this command comes with absolutely no warranty, 2. please do not run it if you do not understand it (especially if you intend to fix files owned by root), 3. it's probably possible to simplify / optimize it.

Similar Messages

  • Pcsx2 display problem - incorrect sRGB, ELF does not have a path

    > screenshot
    I don't really know what's going on - runing official pcsx2 repo for i686 architecture.
    Few problems noticed:
    [wx] iCCP: known incorrect sRGB profile
    HLE Notice: ELF does not have a path.
    EE/iR5900-32 Recompiler Reset
    Bios Found: Europe v02.00(14/06/2004) Console
    BIOS rom1 module not found, skipping...
    BIOS rom2 module not found, skipping...
    BIOS erom module not found, skipping...
    Full output: http://pastebin.com/sTS0xthD
    I've tried removing nvidia package with dependencies and installing it again, and same thing occured.
    Last edited by defm03 (2013-07-04 16:20:22)

    dysong2 wrote:
    I have just installed the latest Java for Mac OS X 10.5 Update 4 and all the color has disappeared from my display, hence everything is in black and white.
    When i log in or restart I have full color so it is only a software problem.
    It is not clear at exactly what point you have no colour. You say you have no colour
    then you say you have colour after you login or restart.
    Dave

  • WARNING: No "known good" pasword found in LDAP

    I'm trying to get windows client (EAP-PEAP MSCHAPv2) to authenticate through freeRadius. I have eDirectory as user store. I've configured universal password and assigned the policy to respective OUs in eDir. I configured universal password policy to allow to retrieve cleartet password by users and "radmin" account, as per Novell docs. iManager RADIUS plugin is also installed, eDir RADIUS schema is extended, radius profile is applied to some users for testing (although no radius attributes are specified in that Radius profile, as Novell docs don't mention anything about it).
    However, is looks like eDirectory is still not returning user's clear-text password in its LDAP reply to freeRadus server, the following warning appears in radius debug log: (WARNING: No "known good" password found in LDAP).
    I followed this Novell guide to setup eDir and freeRadius: https://www.netiq.com/documentation/...ata/front.html
    Here is my radius ldap config:
    ldap TEST {
    server = "192.168.1.1"
    port = 636
    identity = "cn=radmin,ou=USERS,o=TEST"
    password = "password"
    basedn = "ou=USERS,o=TEST"
    filter = "(uid=%{%{Stripped-User-Name}:-%{User-Name}})"
    #base_filter = "(objectclass=radiusprofile)"
    auto_header = yes
    ldap_connections_number = 5
    timeout = 4
    timelimit = 3
    net_timeout = 1
    tls {
    # start_tls = yes
    tls_mode = yes
    cacertfile = /etc/raddb/certs/test-tree.b64
    dictionary_mapping = ${confdir}/ldap.attrmap
    password_attribute = nspmPassword
    edir_account_policy_check = no
    set_auth_type = no
    # access_attr = dialupAccess
    keepalive {
    idle = 60
    probes = 3
    interval = 3
    #END
    Any suggestions on fixing the problem are welcomed. Thanks in advance.

    log doesn't seem display any errors, also I notices that the "nspm password" is is mentioned twice. As far as I know the n="nspm password" attribute is the clear text password. Also From the log i can see that all attributes are the request from radius, would be good to see actual eDir ldap reply in the log, including reply attributes. Any suggestions?
    4269549312 LDAP: Work info status: Total:2 Peak:0 Busy:0
    4211123968 LDAP: New TLS connection 0x8d5c00 from 192.168.1.52:54349, monitor = 0xffffffffe5102700, index = 1
    3843041024 LDAP: Monitor 0xffffffffe5102700 initiating TLS handshake on connection 0x8d5c00
    4205860608 LDAP: DoTLSHandshake on connection 0x8d5c00
    4205860608 LDAP: BIO ctrl called with unknown cmd 7
    4205860608 LDAP: Completed TLS handshake on connection 0x8d5c00
    3821344512 LDAP: DoBind on connection 0x8d5c00
    3821344512 LDAP: Bind name:cn=radmin,ou=USERS,o=TEST, version:3, authentication:simple
    3821344512 AUTH: [000080c4] <.radmin.USERS.TEST.TEST-TREE.> LocalLoginRequest. Error success, conn: 8.
    3821344512 LDAP: Sending operation result 0:"":"" to connection 0x8d5c00
    4222703360 LDAP: DoSearch on connection 0x8d5c00
    4222703360 LDAP: Search request:
    base: "ou=USERS,o=TEST"
    scope:2 dereference:0 sizelimit:0 timelimit:3 attrsonly:1
    filter: "(uid=radmin)"
    attribute: "nspmPassword"
    attribute: "radiusNASIpAddress"
    attribute: "radiusExpiration"
    attribute: "acctFlags"
    attribute: "userPassword"
    attribute: "dBCSPwd"
    attribute: "sambaNtPassword"
    attribute: "sambaLmPassword"
    attribute: "ntPassword"
    attribute: "lmPassword"
    attribute: "radiusCallingStationId"
    attribute: "radiusCalledStationId"
    attribute: "radiusSimultaneousUse"
    attribute: "radiusAuthType"
    attribute: "radiusCheckItem"
    attribute: "radiusTunnelPrivateGroupId"
    attribute: "radiusTunnelMediumType"
    attribute: "radiusTunnelType"
    attribute: "radiusReplyMessage"
    attribute: "radiusLoginLATPort"
    attribute: "radiusPortLimit"
    attribute: "radiusFramedAppleTalkZone"
    attribute: "radiusFramedAppleTalkNetwork"
    attribute: "radiusFramedAppleTalkLink"
    attribute: "radiusLoginLATGroup"
    attribute: "radiusLoginLATNode"
    attribute: "radiusLoginLATService"
    attribute: "radiusTerminationAction"
    attribute: "radiusIdleTimeout"
    attribute: "radiusSessionTimeout"
    attribute: "radiusClass"
    attribute: "radiusFramedIPXNetwork"
    attribute: "radiusCallbackId"
    attribute: "radiusCallbackNumber"
    attribute: "radiusLoginTCPPort"
    attribute: "radiusLoginService"
    attribute: "radiusLoginIPHost"
    attribute: "radiusFramedCompression"
    attribute: "radiusFramedMTU"
    attribute: "radiusFilterId"
    attribute: "radiusFramedRouting"
    attribute: "radiusFramedRoute"
    attribute: "radiusFramedIPNetmask"
    attribute: "radiusFramedIPAddress"
    attribute: "radiusFramedProtocol"
    attribute: "radiusServiceType"
    attribute: "radiusReplyItem"
    attribute: "nspmPassword"
    4222703360 AUTH: Starting SEV calculation for conn 8, entry .radmin.USERS.TEST.TEST-TREE..
    4222703360 AUTH: 1 GlobalGetSEV.
    4222703360 AUTH: 4 GlobalGetSEV succeeded.
    4222703360 AUTH: SEV calculation complete for conn 8, (0:0 s:ms).
    4222703360 LDAP: Sending search result entry "cn=radmin,ou=USERS,o=TEST" to connection 0x8d5c00
    4222703360 LDAP: Sending operation result 0:"":"" to connection 0x8d5c00
    4219545344 AUTH: UpdateLoginAttributesThread page 1 processed 1 login in 1 milliseconds

  • Colors off in Preview when viewing JPG's with sRGB profiles

    I have a 30" Dell monitor and my display preferences are set to use the calibrated profile for it. When I view JPGs images in any color managed application such as Preview the colors are horribly off. They are kind of dull, unsaturated, pale. JPG's that don't have sRGB profiles show up fine.
    I can fix the problem in photoshop by opening the image and then doing a save for web which strips the profile information off of the jpg.
    If I use sRGB as my monitor's profile colors are consistent across all applications but the problem is the colors are really bad. Extremely over contrasty and very dark.
    What's going on with my color profiles?

    Hi topmodelphotography ..
    If you're keen about running the right profiles - please don't mess up the way you do. The sRGB profile that you're using is showing a narrower color space (value 0-16 of blacks are out). The sRGB profile is mainly used for consumer monitors in the cheap end where contrast conditions are worse that expensive and professional displays to present contents in a similar way across manufacturers. If you should use any predefined color profile, please use Adobe (1998) profiling.
    best practive is calibrating your monitor with a good calibrator and use these profiles.
    In System Preferences you should set up the calibrated profile and the same goes for all Adobe apps under Color Settings.
    Useful reading concerning Color Profiles:
    http://kb.adobe.com/selfservice/viewContent.do?externalId=321382&sliceId=1
    Your issue with Preview is most likely due to erroneous setup in System Settings. otherwise try and disable Dithering in Preview.
    And don't use Save for Web if you intend to keep at least a minor part of your colors in your images. Use TIFF's where possible (without 'upgrading' images from compressed formats such as JPEG's, GIF's, etc.)
    useful reading about Image compression:
    http://en.wikipedia.org/wiki/Image_compression
    Hope this answers some of you questions.

  • Asign sRGB profile on import from memory card?

    Can I have the Mac automatically assign the sRGB profile to the images I import into iPhoto. They all come in as Camera RGB now.
    Typically I take my memory card out of the camera and plug it into a memory card reader and then automatically import into iPhoto. This works great except that all the photos are assigned the Camera RGB color profile instead of the sRGB profile.
    Is there a way to configure ColorSync or iPhoto to automatically assign the sRGB profile instead of Camera RGB to the imported images?

    Can I have the Mac automatically assign the sRGB profile to the images I import into iPhoto. They all come in as Camera RGB now.
    Is there a way to configure ColorSync or iPhoto to automatically assign the sRGB profile instead of Camera RGB to the imported images?
    Can you set the preferences in your camera to create images with the sRGB profile? If so, that would be the easiest way, I think.
    Jerry

  • Do images imported to Keynote retain their previous color profile? In other words, if the Keynote presentation will be shown using an sRGB profile projector, should the images be converted to sRGB prior to importing?

    Do images imported to Keynote retain their previous color profile? In other words, if the Keynote presentation will be shown using an sRGB profile projector, should the images be converted to sRGB prior to importing or can they be batch adjusted in Keynote?

    While I feel your comment doesn't directly address my question, why I am worrying is this.
    This presentation is to a camera club. Color is important. Images shown in meetings are projected by an sRGB color profile projector. Most serious photographers us a color profile with a bigger space than sRGB (typically RGB1998). If you project an RGB1998 image on an sRGB projector the colors go to crap. More precisely they become dull and lifeless. Thus, I am trying to determine whether I need to convert the images I plan to put into my Keynote to sRGB and boost the saturation PRIOR to importing them or whether Keynote has a way to do this as part of the software.
    Jerry

  • Open untagged JPEG with external editor, then be attached with sRGB profile

    Hi there,
    I wonder why I open untagged JPEG with "external editor" (Photoshop CS) , then the JPEG will be attached with sRGB profile. Of course my color setting on photoshop is "Use the embedded profile".
    I think sRGB is the default RGB space of colorsync utility , because the profile is also sRGB when you check "Add Colorsync Profile" on iPhoto 6.
    Anyway , I want to set up total Adobe RGB workflow , so does anybody know how to change sRGB profile to Adobe RGB profile when opening untagged JPEG directly with external editor?

    Thank you for your reply , Lloyd.
    I am sorry , but I noticed my misunderstanding message.
    As you know , you can change raw and other image files to tiff or psd for external editor. You can select that on the preference. At this situation , if you pass nontagged image file to external editor , then automatically sRGB profile is attached.
    I don't think this is related to export preset for JPEG file.

  • Image processor and web gallery untagging sRGB profiles

    When I image process a batch of files (mixture of raws and psds) the resulting files have an untagged RGB colour space even though the 'convert to sRGB' is ticked in the processor dialogue. This also happens to my images when I create a web gallery, even when I start the script using sRGB profiled jpegs in the first place. Any suggestions as to why this is happening? Thanks, Matt

    I am slightly confused by what you said...
    without exporting the photos separate first.
    Do you mean change to sRGB while still in Aperture? The answer would be no. The images get changed to sRGB on export. However, you do not have to export the images separately from the gallery. When you create the gallery, the images and html get created all together. So, what you do is change the export presets you are using for the web to have sRGB in the color space profile.

  • Which sRGB Profile to use (HP sRGB Profile, ICC BPC, ICCnoBPC, or no profile)?

    Hi everyone,
    May I ask something of you guys? I have a question that no one can seem to answer.
    I don't know which is the best profile to use--the HP sRGB Profile, the ICC sRGB BPC, the ICC sRGB with no BPC, or no profile (just colorspace tagged as sRGB).
    They are all sRGB_IEC61966-2, but the HP sRGB one that is native to older versions of CS (and possibly newer ones?) does not state whether it is BPC or nonBPC.
    I have noted several things (and I know little of color profiles, so please excuse my ignorance):
    1) Firefox displays all the profiles the same way, except noBPC is shown with lighter blacks
    2) Adobe seems to represent the sRGB BPC and the HP sRGB similarly?
    3) Some people suggest using no profile, merely tagging the metadata to say sRGB
    4) The ICC website says that most V2 color profiles on the www are black scaled; other sites seem to say its the opposite: that BPC is a new thing to most people who save sRGB V2.....
    5) BPC = Black scaling.
    Help ! I'm completely at a loss for what is the most future-proofed means to do this. Each road seems to have a disadvantage.
    Any help would be great
    Tod

    I'm dropping in kind of late, here, and I haven't read the thread thoroughly, but I thought I would add a few cents worth about why you might want to choose certain profiles.
    It's important to start with this: 
    Your choices of color profiles to use for the various functions in your system and for publishing images MUST be made individually, based on how you want to work, and what you anticipate the recipients of your images need. 
    Understand that there is no "one size fits all" answer, which is why you're given configuration choices.  It's important to actually understand color-management to make the proper choices, and many people fail to take the time to do so.
    Document Color Profiles
    For general web publishing, many folks think it's a good idea to publish images in the sRGB color space and with an embedded sRGB profile.  This is because many browsers didn't used to do color management, and Windows in general assumes sRGB.  Even today, not all browsers do proper color management, and sRGB is just assumed in some cases.  If you are serious about web publishing, you probably want to learn just what Internet Explorer, FireFox, Safari, Chrome, and a number of others (and in all their various versions) actually DO regarding color-management, and knowing your intended audience make your own intelligent choices.
    I'll add that as the browser landscape changes (and it is always changing), any "rule of thumb" about which profile to use for web publishing probably needs to be re-evaluated again at intervals in the future.
    For sending images to family or friends electronically, pretty much the same thing applies as with web publishing.  Assuming a user is looking at the image you just sent him/her in Outlook or another mail client, the app may or may not be doing color management, and sRGB image data is probably most likely to be interpreted without problems.  However, you may know something about your recipient's color capabilities and make a different choice.
    For sending images to print houses, quite often they want "standard" sRGB images as well.  However, if they DO offer wide gamut printing, limiting your images to sRGB will mean you won't get all the advantages of their full color depth and your prints may look a bit dull compared to what they could look like.  Don't assume; find out from them what their recommendations are for document color profile.  Again, details matter, and the more you know the better choices you can make.
    Working Color Profiles
    What color spaces you choose to work in in Photoshop have something to do with the results you want to make, and also something to do with the workflow you're willing to adopt.  It may be that you prefer to work on color images in sRGB so that he RGB values you manipulate all through your processing will be the very same ones you provide in your published output images.  Or you may prefer to work with images of the widest possible gamut because you have need to print or otherwise publish your images with a wider gamut than sRGB.  You could even start work with a wide gamut profile (e.g., ProPhoto RGB) for the advantages in maintaining all your images' fidelity, then ultimately publish sRGB - you just have to be sure and make the proper conversion at some point in the workflow.
    It's important to note that Photoshop's Color Settings define your preferences - i.e., how you want Photoshop to handle things (or set defaults or just let you know) when there are choices.  Personally, I like to check all the boxes so that I will be asked if an image isn't in my preferred color space.
    Also note that the Camera Raw plug-in offers a choice of output color space that's separate from the main Photoshop settings.
    Device Color Profiles
    Your display system can be calibrated and profiled.  Calibration generally describes the process of manipulating the output signals so that they are generally the right brightnesses - the response of your display is its Gamma, which should be close to 2.2 on a PC.  Once calibration is achieved, profiling a monitor is generally a matter of sending a bunch of different RGB values to it, seeing what it displays, measuring the difference between that and the ideal color, and setting up to make the proper corrections for future image displays.
    You associate a monitor profile with your monitor using the operating system, even though the operating system only helps with color-management when applications request it.  You may wish to create a monitor profile that matches your monitor's display characteristics - there are devices that come with software and procedures to help you do this, and there are even ways you can do a rough job visually without a device.  This allows Photoshop and other color-managed applications to perform conversions to accurately represent colors from a document with its own profile on your monitor.
    However, you have to understand that not every application on your system is color-managed, and you might actually be looking at RGB values expressed in a document color space and displayed on your monitor without transformation.  Also some transformations are done with shallow data and can introduce noise.  Perhaps you want to minimize the difference because there are tools you like that don't do color-management, or because you know that Internet Explorer 9 assumes your monitor displays sRGB.  It's normal that color-managed and non-color-managed applications can show the very same images differently on a calibrated and profiled system.  This confuses many folks
    Note that the Windows default monitor profile is sRGB IEC61966-2.1.  Depending on your monitor, there can be advantages to making your display respond similarly to sRGB and just using sRGB for your monitor profile.
    Many local printers can be profiled as well.  There are devices to allow you to do this.  However, some printers are "factory calibrated" and expect you to deliver the data in a particular profile - e.g., sRGB. 
    Moreover, there are configuration options to allow you to choose where to do color management during printing.  Photoshop, for example, provides a Color Management section in their Print dialog, and if you drill down to the printer driver's dialogs you may find that there are settings there as well.  You'll need to discover the best combination of these settings for your particular print needs.  Some combinations may work equally well, while you may find some have subtle advantages.  Not long ago I did a whole series of prints in which I manipulated the settings to go through all the different combinations with my HP printer, then critically compared the results.  I found that instructing Photoshop to do a conversion to the print driver's standard sRGB input profile, and disabling color management in the print drivers entirely gave me the best results.
    Summary
    At the end of the day we're doing all this because: You'd like to be able to work on a document, print it and have the colors look as you expect, publish it online and have most people see it as you intended, and send it to others and have them see it as you did.
    No conclusions or direct advice here; I'm just giving you some things to think about when making your color-management choices.
    -Noel

  • [SOLVED] dolphin-emu doesn't build

    I am trying to install dolphin-emu from AUR and when I do, it fails to build and I get the error message:
    CMake Error at CMakeLists.txt:235 (message):
    GLU is required but not found
    Note: It does find libGL.so
    I tried manually cloning the git repo and I get the same error when trying to build it.
    I have spend hours searching Google to no avail.  I have freeglut, nvidia-utils, etc all installed.  I found a fix for Ubuntu which was to install the freeglut3-dev package, but that doesn't seem to exist on Arch (or maybe it is just installed with freeglut?)
    Any ideas?  Thanks!
    Last edited by DanB91 (2012-11-26 14:31:44)

    Pajaro wrote:
    they seem to say here that you have to set OPENGL_INCLUDE_DIR
    http://code.google.com/p/dolphin-emu/wiki/Linux_Build
    Thanks for the reply!  The comment you seem to be referring to doesn't seem to be the problem, though.  CMake can find the OpenGL directory and the OpenGL library (libGL.so).
    Last edited by DanB91 (2012-11-19 00:47:49)

  • Aperture srgb profile issues

    Hi!
    I've a really bad issue with the Aperture sRGB export profile.
    Tell me if there's a fix before I switch to Lightroom: when I export an image (working on a 16Bit TIFF) with strong red colors from Aperture to a .jpg file with sRGB profile, my "red" colors turn to a pale orange, messing up my whole balance. Meanwhile, if I do the same thing on , let say, DxO Optics Pro, or Photoshop, and I export THE SAME IMAGE with the SAME jpg quality and resolution, the REDS remain unaltered.
    This thing happened with A LOT of my photos and now I did this export test with different software and the result has been shocking.
    What's wrong with the sRGB Aperture export profile?!
    Please help or let me know if it is bugged and I cannot rely on something with unpredictable or wrong results.
    Thanks

    All sRGB profiles are generic. In fact, all ICC profiles are platform independent. What would be different between the two are the monitors themselves and/or the monitor profiles.

  • SRGB profile missing - CS4

    CS4, OSX 10.6.2
    I have to upload book cover images to Amazon, and they require an sRGB color profile. It's automated and won't post without this profile (past experience).
    CS4 only has sRGB-IEC61966-2.1, NOT sRGB. CS2 had both.
    Is there a way to locate the sRGB in CS2, and place it into CS4? And if so is that okay to do?
    Otherwise, I've attached a screen capture of CS2's "simplified sRGB Profile" and am wondering if I make this and call it sRGB, if it will work.
    THought I'd ask before I try, because Amazon doesn't let you know if it doesn't work, it simply doesn't post, if you check after a couple of days or more.
    I'm sure they had their reasons, but I wish Adobe hadn't omitted sRGB.
    thanks

    Thanks for responding, Chris.
    CS2 had both profiles as default; they came with the app, I didn't add anything.
    The two apparently have different specs. i.e. If you have a doc with either profile and go EDIT>Convert to Profile, then for Destination space go up to custom RGB, each will offer a "simplified" version, with different numbers/specs. This seems to imply that the 'regular' versions would also have different numbers. This is what I have based my querie on. They must be different because CS2 had both. Plus the fact that Amazon rejected previous files without sRGB. So my original querie still stands. Perhaps sRGB isn't the original, but I still need to get it into CS4, if possible.
    I couldn't find where Adobe stores these profiles on the computer. If I could I'd try what I mentioned in the original post.

  • Recommended sRGB profile for export - use in browsers

    Is there any recommended sRGB profile for use in internet presentation? Below you find the same picture displayed in chrome (left) and internet explorer (right). Colors look quite different, the chrome version appears to be much more natural, the saturation of the ie-version seems to be higher. I know that color management capabilities of different browsers are different. Is there ICC profile recommended that does not show these effects?
    The picture was generated using the LR export function. File Format JPEG, Colorspace sRGB.

    I see you have a wide gamut monitor...which means the first thing you must learn is to forget IE and deny its very existence . It's useless.
    There is only one sRGB, that's not your problem. The problem is IE not converting that sRGB source profile to the monitor profile for display.
    They botched it completely with IE. Instead of a normal color management chain - converting source data to your monitor profile - IE converts everything to sRGB and passes that on to the display. What a brilliant idea that was...this way they made absolutely sure, with 100% certainty, that it will never display correctly - especially vividly demonstrated on a wide gamut monitor. Yes, that was sarcasm.
    A wide gamut display requires fully color managed software to work as intended. You also need a valid monitor profile for that software to use. These are absolute requirements, no exceptions.
    You need a web browser with full color management in all scenarios. The only one that qualifies is Firefox, with color management set to mode 1. This assigns sRGB to all untagged material, honors all embedded profiles, and converts that to your monitor profile for display. No other browser delivers on all counts.

  • Adobe Photoshop CS3 Image Processor not converting files to sRGB Profile

    I have been experiencing a problem with Photoshop CS3 Image Processor no longer converting profiles to sRGB.   It converts all of the files from Camera Raw to JPEG, but not sRGB as well.  I used to be able to batch convert an entire folder of RAW images to JPEG, sRGB through the Image Processor.
    My Photoshop CS3 Working Space is Adobe RGB (1998).  I need to convert an entire folder of images selected in Bridge to sRGB working space in order to publish a photo album from one of the on-line publishing companies.  I can open each individual Camera Raw file in Photoshop and convert each to JPEG, sRGB, but this takes a tremendous amount of time.
    The following procedure has worked for me in the past, but for some reason no longer works:
    I select the images in the desired Bridge CS3 folder.  Upper tool bar, "Tools" > "Photoshop" > "Image Processor".  In Image Processor:
    Section 1 - ""Process files from Bridge only (11)"  Whether or not I place a checkmark by "Open first image to apply settings", it makes no difference in the outcome.
    Section 2:  "Save in same location"
    Section 3 - "Checkmark by "Save as JPEG, quality 12".  Also a checkmark by "Convert Profile to sRGB"
    Section 4 - Checkmark by "Include ICC Profile"
    I replaced my iMac one month ago and reinstalled Photoshop CS3, but this Image Processor problem had been occurring even with my old computer.
    Not sure if you need this information:
    I'm currently on Mac OS X Version 10.6.4
    Processor:  2.93 Ghz Intel Core i7
    Memory:  8 GB 1333 Mhz DDR3
    I don't know if it's related,  Photoshop CS3 on my old computer was running in Rosetta.  I don't know if it's running in Rosetta now, the name does not appear when Photoshop boots up.  How do I get it to run in Rosetta again?

    Heh heh heh.  It's always true that we find the answer just after making public our problems, which in turn we did after trying to find the problems ourselves for hours.
    Thanks for following up with the answer.
    -Noel

  • Epson R2400 Possible incorrect default profile causing issues reported

    I'm based in the UK and I'm currently testing the 6.12 driver with my 2400 on Leopard. Tests have been done on clean installs of LR1.3.1 and CS3 on 10.4.10, 10.5 and 10.5.1 on both a Intel and G5-based Macs.
    The main issue that I have spotted, and believe to be the cause of many of the issues reported so far is as follows. If you check, via the Colorsync utility, the default assigned profile for the R2400 after installing the driver onto a clean 10.5 or 10.5.1 system you'll find that it is set to "SPR2400 Premium Glossy" rather than "SPR2400 Epson Standard".
    I have always known the Epson drivers for many Epson printers to use the "Epson Standard" profile as default and therefore believe that the wrong default profile is set by the installer and this in turn creates a kind of double-profiling effect when an application tries to manage the colour rather than the driver.
    This particular issue only causes problems when printing via Lightroom, that is to say that I can print from Photoshop 10.0.1(CS3) using the correct custom profile and managing the colour through Photoshop along with turning off colour management in the Epson driver just as we always have in prior versions.
    This default profile can not, to my knowledge, be changed by the user. Please note that I'm also using custom profiles created in-house which requires us to use the application-managed print route rather than the driver-managed route.
    I'm actually in the middle of discussing this issue with both Adobe (via techsupport email) and Epson UK (by phone but not getting much success) as I have had no success with the new driver and Lightroom but also intermittently with InDesign and Photoshop (both CS3 versions with latest updates. For the time being I'm back on 10.4.10 with LR1.3.1 and CS3 with no problems.
    I'm hoping that Jeff Schewe, Ian Lyons or someone with the right contacts can raise this issue further with Adobe and Epson and get them to resolve this issue. I have read both Ian and Jeff's posts and would like to thank them (and others) for their help in explaining some of the reasons for the issues but along the same path they really are the people we look to for answers at times like these. Hope this may provide some help to solve at least some of the issues we're seeing.
    Jason Hicking - Replica Imaging Limited, UK

    Dave
    You're describing pretty much what I'm seeing here with the UK version in the UK so it looks like I was right about the default profile being set differently from previous drivers.
    Could you describe step-by-step how you setup Lightroom and the driver settings used when you get good prints using your profiles? I'm interested for comparison with my own workflow.
    If I understand correctly from past information and experience the Standard profile if used when the colour management is turned off in the driver and acts a kind of null transform so therefore any other choice of profile as default would appear to suggest that we are asking Lightroom to colour manage the image using the profile we select in the application but then the driver is using a second profile (Premium Glossy) when colour management is turned off in the driver where previously it would be using the Standard profile which does not affect the data passed from the application.
    It's still weird to me that I can get good prints from Photoshop using the driver and profiles under Leopard but, from what I've read by Jeff Schewe, this could be down to the new print pipeline being used by Lightroom. Not pointing the finger anywhere but just making an observation.
    John
    With all due respect you solution of using the standard Epson profile and papers doesn't work for those of us who need to use custom profiles for third party papers, even before the third party inks are introduced into the equation. For example when printing on Ilford papers I would still need to specify Ilford's profile for the R2400 even when I'm using Epsons inks and this would still give problems.
    Also we've been using the third-party (Lyson PhotoChrome) inks with a range of printers including the R2400 and 7600 for well over 5 years and had no issues before when using Lightroom or Photoshop (or any other application for that matter), the problems only arise when using 10.5.
    I'm not sure were the suggestion to delete "both sets of drivers" from leading as I've not got two drivers, that is to say that each install has been done on a clean OS before testing. I actually have an external drive with four partitions for each type of Mac (G5 or Intel). Each drive has a clean install of 10.4.8, 10.4.10, 10.5 and 10.5.1 so that we can "roll back" our internal drive any any point in the testing by simply cloning the OS we need on to the internal drive and then start again, installing just the drivers and apps we want to test.
    Hope we can find some more information out from Epson as to the actual reason for the different defaults even if this just clears any confusion about what it is actually doing during different workflows. I'll keep the forum informed with anything I find out but would still like Ian to post the settings from that the people that he knows are getting good results.
    Cheers for now
    Jason

Maybe you are looking for