[argyllcms] Re: Location of profiles on Linux

  • From: "David H. Vree" <david.h.vree@xxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Fri, 14 Nov 2008 14:45:18 -0500

Graeme Gill wrote:
David H. Vree wrote:

Upon running the command "dispwin -I Dell_2407.icc" I found that it put the profile into "~/.local/share/color/icc/devices/display" instead. Figuring that maybe I needed to run it as root, I did. However it put the profile into "/root/.local/share/color/icc/devices/display". Is this expected behavior? What am I doing wrong?

You probably want to specify the profile scope:

ie. -Sl to get local scope

[ I'll fix the doco to note that both Linux and Vista support
  local and user scope. ]
So sorry I missed this. Must have read that page 50 times, but never really took notice of that. In any event, I tried running dispwin -S l -I Dell_2407.icc both as myself and as root. In both cases it faults with the following output:

XRandR 1.2 is faulty - falling back to older extensions
About to open dispwin object on the display
About to install 'Dell_2407_WPF_20081113.icc' as display's default profile
*** glibc detected *** dispwin: free(): invalid next size (fast): 0x08cc44f0 ***
======= Backtrace: =========
======= Memory map: ========
08048000-080bb000 r-xp 00000000 fe:00 1452549 /opt/Argyll_V1.0.3/bin/dispwin 080bb000-080c3000 rw-p 00073000 fe:00 1452549 /opt/Argyll_V1.0.3/bin/dispwin
080c3000-080c4000 rw-p 080c3000 00:00 0
08cbc000-08cdd000 rw-p 08cbc000 00:00 0          [heap]
b7c00000-b7c21000 rw-p b7c00000 00:00 0
b7c21000-b7d00000 ---p b7c21000 00:00 0
b7d52000-b7d5f000 r-xp 00000000 fe:00 310095     /lib/libgcc_s.so.1
b7d5f000-b7d60000 r--p 0000c000 fe:00 310095     /lib/libgcc_s.so.1
b7d60000-b7d61000 rw-p 0000d000 fe:00 310095     /lib/libgcc_s.so.1
b7d71000-b7d72000 rw-p b7d71000 00:00 0
b7d72000-b7d7a000 r-xp 00000000 fe:00 681294 /usr/lib/libXrender.so.1.3.0 b7d7a000-b7d7b000 r--p 00007000 fe:00 681294 /usr/lib/libXrender.so.1.3.0 b7d7b000-b7d7c000 rw-p 00008000 fe:00 681294 /usr/lib/libXrender.so.1.3.0
b7d7c000-b7d7d000 rw-p b7d7c000 00:00 0
b7d7d000-b7d94000 r-xp 00000000 fe:00 680909     /usr/lib/libxcb.so.1.0.0
b7d94000-b7d95000 r--p 00016000 fe:00 680909     /usr/lib/libxcb.so.1.0.0
b7d95000-b7d96000 rw-p 00017000 fe:00 680909     /usr/lib/libxcb.so.1.0.0
b7d96000-b7d97000 r-xp 00000000 fe:00 680911 /usr/lib/libxcb-xlib.so.0.0.0 b7d97000-b7d98000 r--p 00000000 fe:00 680911 /usr/lib/libxcb-xlib.so.0.0.0 b7d98000-b7d99000 rw-p 00001000 fe:00 680911 /usr/lib/libxcb-xlib.so.0.0.0 b7d99000-b7ef1000 r-xp 00000000 fe:00 310228 /lib/tls/i686/cmov/libc-2.8.90.so b7ef1000-b7ef3000 r--p 00158000 fe:00 310228 /lib/tls/i686/cmov/libc-2.8.90.so b7ef3000-b7ef4000 rw-p 0015a000 fe:00 310228 /lib/tls/i686/cmov/libc-2.8.90.so
b7ef4000-b7ef7000 rw-p b7ef4000 00:00 0
b7ef7000-b7f0c000 r-xp 00000000 fe:00 310246 /lib/tls/i686/cmov/libpthread-2.8.90.so b7f0c000-b7f0d000 r--p 00014000 fe:00 310246 /lib/tls/i686/cmov/libpthread-2.8.90.so b7f0d000-b7f0e000 rw-p 00015000 fe:00 310246 /lib/tls/i686/cmov/libpthread-2.8.90.so
b7f0e000-b7f10000 rw-p b7f0e000 00:00 0
b7f10000-b7f34000 r-xp 00000000 fe:00 310234 /lib/tls/i686/cmov/libm-2.8.90.so b7f34000-b7f35000 r--p 00023000 fe:00 310234 /lib/tls/i686/cmov/libm-2.8.90.so b7f35000-b7f36000 rw-p 00024000 fe:00 310234 /lib/tls/i686/cmov/libm-2.8.90.so
b7f36000-b7f38000 r-xp 00000000 fe:00 681945     /usr/lib/libXss.so.1.0.0
b7f38000-b7f3a000 rw-p 00001000 fe:00 681945     /usr/lib/libXss.so.1.0.0
b7f3a000-b7f3b000 rw-p b7f3a000 00:00 0
b7f3b000-b7f3f000 r-xp 00000000 fe:00 680907     /usr/lib/libXdmcp.so.6.0.0
b7f3f000-b7f40000 rw-p 00003000 fe:00 680907     /usr/lib/libXdmcp.so.6.0.0
b7f40000-b7f42000 r-xp 00000000 fe:00 680905     /usr/lib/libXau.so.6.0.0
b7f42000-b7f43000 rw-p 00001000 fe:00 680905     /usr/lib/libXau.so.6.0.0
b7f43000-b7f48000 r-xp 00000000 fe:00 681338     /usr/lib/libXrandr.so.2.1.0
b7f48000-b7f49000 r--p 00005000 fe:00 681338     /usr/lib/libXrandr.so.2.1.0
b7f49000-b7f4a000 rw-p 00006000 fe:00 681338     /usr/lib/libXrandr.so.2.1.0
b7f4a000-b7f4c000 r-xp 00000000 fe:00 681336 /usr/lib/libXinerama.so.1.0.0 b7f4c000-b7f4d000 rw-p 00001000 fe:00 681336 /usr/lib/libXinerama.so.1.0.0 b7f4d000-b7f51000 r-xp 00000000 fe:00 680921 /usr/lib/libXxf86vm.so.1.0.0 b7f51000-b7f52000 r--p 00003000 fe:00 680921 /usr/lib/libXxf86vm.so.1.0.0 b7f52000-b7f53000 rw-p 00004000 fe:00 680921 /usr/lib/libXxf86vm.so.1.0.0
b7f53000-b7f60000 r-xp 00000000 fe:00 680919     /usr/lib/libXext.so.6.4.0
b7f60000-b7f62000 rw-p 0000c000 fe:00 680919     /usr/lib/libXext.so.6.4.0
b7f62000-b7f63000 rw-p b7f62000 00:00 0
b7f63000-b804e000 r-xp 00000000 fe:00 680913     /usr/lib/libX11.so.6.2.0
b804e000-b804f000 r--p 000ea000 fe:00 68091Aborted

How can I find out if my system is able to get the display EDID. If it helps, I have an nVidia GE Force Go 7400 card and when I run the proprietary nvidia-settings program it tells me everything about the display. However, I did notice that whenever I run an ArgyllCMS command I get the following error:

"XRandR 1.2 is faulty - falling back to older extensions"

Does Argyll use XRandR to get the EDID info...or does it use some other method?

It will try to get the EDID from the server atoms. I'm not sure if there
is any easy way of knowing if the EDID is being used, or the fallback
of the server name. Looking through the JSON files that are created,
to see what identifier is being used is one way.

I have no JSON files in my user scope (i.e. ~/.local/...../display). Should I have? Because of the above error I have nothing in my machine (local) scope, but I'll check there once we figure out why dispwin crashed.

Other related posts: