From pmjdebruijn at pcode.nl Tue Nov 10 18:35:36 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 10 Nov 2009 19:35:36 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: <1257878136.9870.4.camel@goliath> Hi, I have a HP Photosmart C6280 (all-in-one), which is connected via HP JetDirect (Ethernet). Currently it is not being detected by GNOME Color Manager, while I can print, and XSane does recognize the scanner... I'm assuming this is because currently only USB connected devices are checked? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From hughsient at gmail.com Tue Nov 10 18:42:39 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 18:42:39 +0000 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) In-Reply-To: <1257878136.9870.4.camel@goliath> References: <1257878136.9870.4.camel@goliath> Message-ID: <15e53e180911101042k5746e765i185677d1957e3198@mail.gmail.com> 2009/11/10 Pascal de Bruijn : > I have a HP Photosmart C6280 (all-in-one), which is connected via HP > JetDirect (Ethernet). > Currently it is not being detected by GNOME Color Manager, while I can > print, and XSane does recognize the scanner... > I'm assuming this is because currently only USB connected devices are > checked? Correct. How does xsane recognise the scanner? At the moment we're just checking USB printers that use hplip and scanners that are matched with libsane. If you can work out how to identify the device using a property in udev, then it's an easy add. I'm not sure how the ethernet printing and scanning stuff actually works right now. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 19:35:48 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 20:35:48 +0100 Subject: A small bug Message-ID: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> I'm stumbled over this when I interrupted a profile creation. My target profile name was the same as set before with gcm-prefs. I ended up with the entire gcm-prefs gui blocked. Se attached screenshoot. I have reproduced it and attached a log file. If I do a "head -c 100 /dev/random > i1.icc" where i1.icc is my gcm-prefs chosen profile I got this messages in log: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected **************************************************** With a large file like this: "head -c 500 /dev/random > i1.icc" I got: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-log.txt.zip Type: application/zip Size: 2093 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: corrupt.png Type: image/png Size: 20741 bytes Desc: not available URL: From hughsient at gmail.com Tue Nov 10 20:08:28 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 20:08:28 +0000 Subject: A small bug In-Reply-To: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> Message-ID: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> 2009/11/10 Lars Tore Gustavsen : > I have reproduced it and attached a log file. > If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my > gcm-prefs chosen profile I got this messages in log: Can you try with git now please. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 21:35:09 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 22:35:09 +0100 Subject: A small bug In-Reply-To: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> Message-ID: <58497f010911101335g317529bev8f1e48d780e3ab5d@mail.gmail.com> On Tue, Nov 10, 2009 at 9:08 PM, Richard Hughes wrote: > 2009/11/10 Lars Tore Gustavsen : >> I have reproduced it and attached a log file. >> If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my >> gcm-prefs chosen profile I got this messages in log: > > Can you try with git now please. Thanks. > > Richard. > It works very well, thank you. Lars Tore From lars.tore at mulebakken.net Wed Nov 11 11:51:06 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 12:51:06 +0100 Subject: Bluish.icc Message-ID: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> The icc profile include with gnome-color-manager is very nice to test if everything works. However it advertise itself as "sRGB IEC61966-2-1" I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: bluish.icc Type: application/octet-stream Size: 3962 bytes Desc: not available URL: From hughsient at gmail.com Wed Nov 11 11:59:55 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 11:59:55 +0000 Subject: Bluish.icc In-Reply-To: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> Message-ID: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> 2009/11/11 Lars Tore Gustavsen : > I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Committed, thanks. Richard. From fred at crozat.net Wed Nov 11 12:53:41 2009 From: fred at crozat.net (Frederic Crozat) Date: Wed, 11 Nov 2009 13:53:41 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> Message-ID: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> 2009/11/11 Richard Hughes : > 2009/11/11 Lars Tore Gustavsen : >> I have edited the attached profile and it now reads "bluish test" in gcm-prefs. > > Committed, thanks. In the same idea, it could be interesting to bundle a "test" jpg or png image in gnome-color-manager which would be only visible (or display correctly) when ICC profiles are correctly handled by applications. I use either http://1reflet.skynetblogs.be/post/6632777/profil-colorimetrique-utilisateur-firefox (sorry it is in french, flower is supposed to be displayed in yellow, not pink) or http://www.color.org/version4html.xalter I don't the license of those images are compatible with free software but creating similar images would be useful. WDYT ? -- Frederic Crozat From hughsient at gmail.com Wed Nov 11 13:12:09 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 13:12:09 +0000 Subject: Bluish.icc In-Reply-To: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> Message-ID: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> 2009/11/11 Frederic Crozat : > I don't the license of those images are compatible with free software > but creating similar images would be useful. > WDYT ? I think it's a good idea, although the licence would have to be CC_BY_SA or something like that to be allowed in gcm. Can anybody find suitably licensed example photographs? We also want the gamma checker images, but alas, these have to be free too. Richard. From anders at brander.dk Wed Nov 11 13:43:43 2009 From: anders at brander.dk (Anders Brander) Date: Wed, 11 Nov 2009 14:43:43 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> Message-ID: <1257947023.29790.3.camel@smutogtab> Hi, On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > 2009/11/11 Frederic Crozat : > > I don't the license of those images are compatible with free software > > but creating similar images would be useful. > > WDYT ? > > I think it's a good idea, although the licence would have to be > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > suitably licensed example photographs? We also want the gamma checker > images, but alas, these have to be free too. I'm not sure what is meant here. If we need an image to test whether an ICC profile is respected, one could create an image with swapped red/green channels - and then embed a ICC-profile undoing that. It would be obvious if the profile is respected or not when viewing the image. Well... /Anders Brander From hughsient at gmail.com Wed Nov 11 14:38:15 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 14:38:15 +0000 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> 2009/11/11 Anders Brander : > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. Yes, I think that would be a good idea for testing purposes. Richard. From lars.tore at mulebakken.net Wed Nov 11 16:58:23 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 17:58:23 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> Message-ID: <58497f010911110858x42131154p3217ff2015f60f45@mail.gmail.com> On Wed, Nov 11, 2009 at 3:38 PM, Richard Hughes wrote: > 2009/11/11 Anders Brander : >> I'm not sure what is meant here. If we need an image to test whether an >> ICC profile is respected, one could create an image with swapped >> red/green channels - and then embed a ICC-profile undoing that. It would >> be obvious if the profile is respected or not when viewing the image. > > Yes, I think that would be a good idea for testing purposes. > > Richard. I often play with "dispwin -V profilename" to check correct loading of the clut. So that's another idea. Lars Tore Gustavsen From pmjdebruijn at pcode.nl Wed Nov 11 17:26:04 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 11 Nov 2009 18:26:04 +0100 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <1257960364.6073.7.camel@goliath> On Wed, 2009-11-11 at 14:43 +0100, Anders Brander wrote: > Hi, > > On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > > 2009/11/11 Frederic Crozat : > > > I don't the license of those images are compatible with free software > > > but creating similar images would be useful. > > > WDYT ? > > > > I think it's a good idea, although the licence would have to be > > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > > suitably licensed example photographs? We also want the gamma checker > > images, but alas, these have to be free too. > > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. We can have two purposes for the image: 1. See if the profile is loaded properly at all 2. See if the profile is in the right ballpark (regarding accuracy) While the following image surely isn't CC licensed, something similar to this would be just perfect: http://www.smugmug.com/help/calibration-1400.mg -- http://blog.pcode.nl/ http://photos.pcode.nl/ From memolus at googlemail.com Thu Nov 12 19:56:09 2009 From: memolus at googlemail.com (memolus at googlemail.com) Date: Thu, 12 Nov 2009 20:56:09 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: 2009/11/10 Richard Hughes : > Correct. How does xsane recognise the scanner? At the moment we're > just checking USB printers that use hplip and scanners that are > matched with libsane. If you can work out how to identify the device > using a property in udev, then it's an easy add. I'm not sure how the > ethernet printing and scanning stuff actually works right now. Thanks. I don't know how deep you know the details about the network support of hplip, but here's what I know, as an introduction: The printer and the scanner is identified by an URI "hp:/net/Photosmart_C6200_series?ip=192.168.0.2" (fax has hpfax:/ instead of hp:/) in cups and sane ("Photosmart_C6200_series:Photosmart_C6200_series?ip=192.168.0.2") using the hplip driver, and treated as an local device. Normal network printers have URIs like "socket://printer:9100". It's detectable using Zeroconf (dnssd://photosmart c6200 series [d44b9e]._pdl-datastream._tcp.local/) and UPnP, cause HP supports Mac and Windows. Actually automatic detection of hp photosmart all-in-one devices in system-config-printer-gnome is broken, but automatic detection works using gnome-cups-manager und sane. From lars.tore at mulebakken.net Fri Nov 13 16:38:42 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Fri, 13 Nov 2009 17:38:42 +0100 Subject: Fighting with the screensaver. Message-ID: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> First I wonder if I'm the only person now who fights with the lut deletion with gnome-screensaver. It almost look like it is fixed, but I have still have this problem with ubuntu 9.10. https://bugzilla.gnome.org/show_bug.cgi?id=342850 Should I expect the color manager to take care of this on it own? Like running some kind of services? When I use dispwin from the argyll package I normally take care of this with a desktop file in the autostart folder with an exec line like this. Exec=/bin/bash -c ? gnome-screensaver-command ?exit; dispwin -L;gnome-screensaver? I recently tried gcm on an xubuntu (xface)box and it worked very well, but I guess the reason was it used xscreensaver instead of gnome-screensaver. From fred at crozat.net Fri Nov 13 16:46:36 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 17:46:36 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> 2009/11/13 Lars Tore Gustavsen : > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally ?take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > ?dispwin -L;gnome-screensaver? gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in it) needs to be fixed to correctly save LUT before fading gamma at screensaver startup and restore it when it quits. I haven't found time to investigate before 2.28 was released :( -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 16:50:16 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 16:50:16 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> Message-ID: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> 2009/11/13 Frederic Crozat : > gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in > it) needs to be fixed to correctly save LUT before fading gamma at > screensaver startup and restore it when it quits. Or, gnome-screensaver could just call gcm-apply which resets everything as well. Richard. From pmjdebruijn at pcode.nl Fri Nov 13 16:56:50 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 13 Nov 2009 17:56:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <4c2c37f90911130856m5fdcd776vbc8e9b84a934d011@mail.gmail.com> On Fri, Nov 13, 2009 at 5:50 PM, Richard Hughes wrote: > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. While these are all solutions, the short term workaround is simply to not use a screensaver, and only have display power saving enabled :) I know it's lame... but screensavers don't have any real function any more, or do they? Regards, Pascal de Bruijn From fred at crozat.net Fri Nov 13 21:05:10 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:05:10 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. That would imply a dependency on gcm, which is not a really good idea. I really think gnome-screensaver should restore LUT after the fading (after all, I also want the pictures used for slideshow in screensaver to be correctly color managed ;) -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 21:12:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 21:12:34 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> Message-ID: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> 2009/11/13 Frederic Crozat : > That would imply a dependency on gcm, which is not a really good idea. Sure, but the sort of dependency where it doesn't matter if gcm-apply doesn't exist... > I really think gnome-screensaver should restore LUT after the fading > (after all, I also want the pictures used for slideshow in screensaver > to be correctly color managed ;) That is true. Richard. From fred at crozat.net Fri Nov 13 21:25:59 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:25:59 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> Message-ID: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> That would imply a dependency on gcm, which is not a really good idea. > > Sure, but the sort of dependency where it doesn't matter if gcm-apply > doesn't exist... It does if people uses dispwin manually (or anything else to change LUT) ;) -- Frederic Crozat From amluto at gmail.com Fri Nov 13 21:56:42 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Fri, 13 Nov 2009 16:56:42 -0500 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> Message-ID: On Fri, Nov 13, 2009 at 4:25 PM, Frederic Crozat wrote: > 2009/11/13 Richard Hughes : >> 2009/11/13 Frederic Crozat : >>> That would imply a dependency on gcm, which is not a really good idea. >> >> Sure, but the sort of dependency where it doesn't matter if gcm-apply >> doesn't exist... > > It does if people uses dispwin manually (or anything else to change LUT) ;) ISTM that gnome-screensaver would ideally just not touch the LUT. These days we have compositing, or even just taking a screen shot and fading to black with RENDER, for that. --Andy > > -- > Frederic Crozat > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pmjdebruijn at pcode.nl Sat Nov 14 18:23:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 14 Nov 2009 19:23:51 +0100 Subject: Standby also seems to reset the VideoLUT/crtc Message-ID: <1258223031.9981.3.camel@goliath> Hi, Similarly as discussed in "Re: Fighting with the screensaver." it also seems putting your laptop to sleep (standby) seems to reset the VideoLUT/xrandr crtc's... Can anybody test and confirm this... I have a Intel X4500MHD graphics chip, however, if I'm not mistaken the driver card/driver actually doesn't have anything to do with this, with the vcgt tag is applied via Xorg/xrandr. Or am I wrong about this? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From compiz at sukimashita.com Sat Nov 14 19:19:20 2009 From: compiz at sukimashita.com (Martin S.) Date: Sat, 14 Nov 2009 20:19:20 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <1258226360.12545.10.camel@mirell> On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 This is somewhat old. I remember working on that bug myself as it was annoying for both gnome-screensaver and xscreensaver if I had profiles set. However, the issue was clearly fixed and I did't see this anymore on a range of systems since then (nvidia, intel mostly). > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > dispwin -L;gnome-screensaver? This is not the right solution afaik. Applications should not fiddle with the color profile settings unless they are created to do just that. If you are sure gnome-screensaver causes it please file a bug. gnome-screensaver must respect the LUT settings here (the code apparently does already...). As noted above, this works fine on a couple of systems I tested for 2.28. What gfx driver do you use and which component versions (xorg, driver, gnome-screensaver? --- Martin S. From amluto at gmail.com Sat Nov 14 19:54:41 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sat, 14 Nov 2009 14:54:41 -0500 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: On my system, whatever xorg-xserver version F11 used interacted badly with intel to cause all kinds of things to reset the LUTs. For example, resuming, switching VTs, and even starting glxgears or okular (!). This has been fixed upstream and in F12. --Andy On Sat, Nov 14, 2009 at 2:19 PM, Martin S. wrote: > On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: >> First I wonder if I'm the only person now who fights with the lut >> deletion with gnome-screensaver. >> It almost look like it is fixed, but I have still have this problem >> with ubuntu 9.10. >> https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > This is somewhat old. I remember working on that bug myself as it was > annoying for both gnome-screensaver and xscreensaver if I had profiles > set. > > However, the issue was clearly fixed and I did't see this anymore on a > range of systems since then (nvidia, intel mostly). > >> Should I expect the color manager to take care of this on it own? Like >> running some kind of services? >> When I use dispwin from the argyll package I normally ?take care of >> this with a desktop file in the autostart folder with an exec line >> like this. >> Exec=/bin/bash -c ? gnome-screensaver-command ?exit; >> ?dispwin -L;gnome-screensaver? > > This is not the right solution afaik. Applications should not fiddle > with the color profile settings unless they are created to do just that. > > If you are sure gnome-screensaver causes it please file a bug. > gnome-screensaver must respect the LUT settings here (the code > apparently does already...). > > As noted above, this works fine on a couple of systems I tested for > 2.28. > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > > --- Martin S. > > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list From compiz at sukimashita.com Sun Nov 15 02:04:29 2009 From: compiz at sukimashita.com (Martin S.) Date: Sun, 15 Nov 2009 03:04:29 +0100 Subject: [PATCH] Enable adding xrandr devices with no EDID Message-ID: <1258250669.25043.1.camel@mirell> Devices without EDID information or bad XRANDR implementations work again and get standard properties set. This restores functionality that existed before a recent change and allows me to assign color profiles on the broken nvidia xrandr implementation again. --- Martin S. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Enable-adding-xrandr-devices-with-no-EDID.patch Type: text/x-patch Size: 1874 bytes Desc: not available URL: From hughsient at gmail.com Sun Nov 15 15:03:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:03:32 +0000 Subject: [PATCH] Enable adding xrandr devices with no EDID In-Reply-To: <1258250669.25043.1.camel@mirell> References: <1258250669.25043.1.camel@mirell> Message-ID: <15e53e180911150703r28ba9e0dm9a1fbf760b2ab6ea@mail.gmail.com> 2009/11/15 Martin S. : > This restores functionality that existed before a recent change and > allows me to assign color profiles on the broken nvidia xrandr > implementation again. Applied, thanks. Richard. From hughsient at gmail.com Sun Nov 15 15:30:12 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:30:12 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <1258223031.9981.3.camel@goliath> References: <1258223031.9981.3.camel@goliath> Message-ID: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> 2009/11/14 Pascal de Bruijn : > Similarly as discussed in "Re: Fighting with the screensaver." it also > seems putting your laptop to sleep (standby) seems to reset the > VideoLUT/xrandr crtc's... Seems plausible, although I would argue we should probably just get X or the kernel to save the gamma tables on suspend and restore them on resume. It certainly seems a better idea then getting the session to do it. Richard. From amluto at gmail.com Sun Nov 15 15:33:14 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 10:33:14 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 10:30 AM, Richard Hughes wrote: > 2009/11/14 Pascal de Bruijn : >> Similarly as discussed in "Re: Fighting with the screensaver." it also >> seems putting your laptop to sleep (standby) seems to reset the >> VideoLUT/xrandr crtc's... > > Seems plausible, although I would argue we should probably just get X > or the kernel to save the gamma tables on suspend and restore them on > resume. It certainly seems a better idea then getting the session to > do it. Heh, I replied to Pascal directly instead of to all. I think that X already does that with server 1.7 and up and (on my machine, anyway) intel driver 2.9.0 and up. (e.g. F12 but not F11) --Andy > > Richard. > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pedro at pedrocr.net Sun Nov 15 19:15:24 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 11:15:24 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: > Heh, I replied to Pascal directly instead of to all. ?I think that X > already does that with server 1.7 and up and (on my machine, anyway) > intel driver 2.9.0 and up. ?(e.g. F12 but not F11) I run Ubuntu Karmic (9.10) and this is not the case. I do have the 2.9.0 intel driver but the server is only 1.6.4. So I guess the config for it is in the xserver. Strangely when I set the ICC profile with xcalib it seems to survive the suspend. Pedro From amluto at gmail.com Sun Nov 15 19:40:15 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 14:40:15 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 2:15 PM, Pedro C?rte-Real wrote: > On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: >> Heh, I replied to Pascal directly instead of to all. ?I think that X >> already does that with server 1.7 and up and (on my machine, anyway) >> intel driver 2.9.0 and up. ?(e.g. F12 but not F11) > > I run Ubuntu Karmic (9.10) and this is not the case. I do have the > 2.9.0 intel driver but the server is only 1.6.4. So I guess the config > for it is in the xserver. Strangely when I set the ICC profile with > xcalib it seems to survive the suspend. I believe it requires some cooperation between both. In the intel driver, in drmmode_set_mode_major, it says: #if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1,7,0,0,0) crtc->funcs->gamma_set(crtc, crtc->gamma_red, crtc->gamma_green, crtc->gamma_blue, crtc->gamma_size); #endif --Andy > > Pedro > From lars.tore at mulebakken.net Sun Nov 15 20:42:50 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Sun, 15 Nov 2009 21:42:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: <58497f010911151242u54a7926am8f1a9128da6dec42@mail.gmail.com> On Sat, Nov 14, 2009 at 8:19 PM, Martin S. wrote: > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > I use ubuntu 9.10 and I have a ATI Radeon 9200 PRO card. I use the radeon xorg driver and the xorg version is 1.7.4. Gnome-screensaver is 2.28.0 Lars Tore Gustavsen From pedro at pedrocr.net Sun Nov 15 23:53:38 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 15:53:38 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> First, thanks for this Richard. Gnome/Linux have been needing this kind of simple support for color in a long time. On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: > Strangely when I set the ICC profile with xcalib it seems to survive the suspend. xcalib is probably doing something very different as its calibration also applies to all displays. On the other hand this means that it both survives the suspend and is applied when the display is disconnected/connected, both things that g-c-m currently doesn't handle properly. The suspend/resume stuff should be handled by X but the connect/disconnect should probably be handled by g-c-m as that policy shouldn't be in X. Cheers, Pedro From hughsient at gmail.com Mon Nov 16 08:29:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 16 Nov 2009 08:29:32 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> Message-ID: <15e53e180911160029u572db018x7d459eaf624c5765@mail.gmail.com> 2009/11/15 Pedro C?rte-Real : > First, thanks for this Richard. Gnome/Linux have been needing this > kind of simple support for color in a long time. > > On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: >> Strangely when I set the ICC profile with xcalib it seems to survive the suspend. > > xcalib is probably doing something very different as its calibration > also applies to all displays. xcalib sets the per-screen gamma tables, and gcm sets the per-output gamma tables. Richard. From pmjdebruijn at pcode.nl Wed Nov 25 17:28:33 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:28:33 +0100 Subject: Regression: gnome-color-manager segfaults after dispcal Message-ID: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Hi, Using gnome-color-manager 2.29.1~git20091124 it seems to segfault after running dispcal. Can anybody confirm this? Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Wed Nov 25 17:30:03 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:30:03 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown Message-ID: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Hi, On my external display (HP LP2475w) connected via DVI to my Intel GMA, the precalibration "tips/guidelines" dialog isn't shown anymore. Has this been disabled on purpose, or is this an accidental regression? Regards, Pascal de Bruijn From hughsient at gmail.com Wed Nov 25 17:40:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:40:57 +0000 Subject: Regression: gnome-color-manager segfaults after dispcal In-Reply-To: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> References: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Message-ID: <15e53e180911250940l2187d4e7s9755ed15edc867eb@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Using gnome-color-manager 2.29.1~git20091124 it seems to segfault > after running dispcal. You got a backtrace please? Thanks. Richard. From hughsient at gmail.com Wed Nov 25 17:48:20 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:48:20 +0000 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Message-ID: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Has this been disabled on purpose, or is this an accidental regression? The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 18:09:48 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:09:48 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore Message-ID: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Hi, It seems that gcm-prefs from current git does not apply the VideoLUT/vcgt tag anymore... gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 18:14:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:14:51 +0100 Subject: gcm-prefs: New profiles not showing up in the list Message-ID: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Hi, When display calibration finishes, the newly created profile does not show up in the list in gcm-prefs. Restarting gcm-prefs helps, then I _do_ see the new profile. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:24:32 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:24:32 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore In-Reply-To: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> References: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Message-ID: <4c2c37f90911261224h24d5eb10u1cb767adde26787a@mail.gmail.com> On Thu, Nov 26, 2009 at 7:09 PM, Pascal de Bruijn wrote: > Hi, > > It seems that gcm-prefs from current git does not apply the > VideoLUT/vcgt tag anymore... > > gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Changing the profile in gcm-prefs, closing gcm-prefs, and opening gcm-prefs again also does _not_ change the profile that is selected by default. So the problem is most likely not the application of another profile's VideoLUT, but the VideoLUT of the original default selected profile is always being applied, no matter which profile was manually selected afterward. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:54:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:54:28 +0100 Subject: Patch: Debian binary detection fix Message-ID: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Hi, I noticed the following recent commit to detect the Debinized Argyll binaries: http://git.gnome.org/cgit/gnome-color-manager/commit/?id=3b06571386be55a7b21424c256b88b2fb2ec6347 Conceptually the commit is fine, it's particularly great, this detect method is used for all of Argyll's utilities. Practically this is only applicable for targen at the moment. But since it's used for all binaries, gcm is automatically future proofed against other binaries getting renamed as well. Excellent behaviour. However, the detection is backwards. Please allow me to explain. Debian maintainers don't rename binaries just because they get a kick out of arbitrarily renaming random binaries. Debian has problems with conflicting binaries because their package repository is so big (almost 30,000 packages). This means they are forced to rename binaries in all but one package with conflicting binaries. This implies, on systems with a 'argyll-targen' binary, a 'targen' binary could be installed as well. But if a 'targen' binary is installed as well, it's most likely completely unrelated to Argyll, and will almost certainly fail when called by gcm. Therefore the detect should _first_ detect if the Debian renamed binaries exist, and if not, fallback to the original binary names. I've attached a small patch, which should "fix" the issue described above. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-debian-fix.patch Type: text/x-patch Size: 1022 bytes Desc: not available URL: From hughsient at gmail.com Thu Nov 26 21:07:11 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:07:11 +0000 Subject: Patch: Debian binary detection fix In-Reply-To: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> References: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Message-ID: <15e53e180911261307l6b8b4427g13bc6de54b014f00@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Therefore the detect should _first_ detect if the Debian renamed > binaries exist, and if not, fallback to the original binary names. Agreed. I've attached the patch I've committed. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: look-for-debian-first.patch Type: text/x-patch Size: 1063 bytes Desc: not available URL: From alexandre.prokoudine at gmail.com Thu Nov 26 21:18:51 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 00:18:51 +0300 Subject: shifted dialog Message-ID: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Hi, The dialog that suggests to plug-in a measurement device somewhat unexpectedly pops up close to the left border of the screen, which is quite unfortunate for a 24" display :) Alexandre From hughsient at gmail.com Thu Nov 26 21:18:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:18:57 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Message-ID: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > When display calibration finishes, the newly created profile does not > show up in the list in gcm-prefs. Can you try now please. Thanks, Richard. From hughsient at gmail.com Thu Nov 26 21:22:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:22:33 +0000 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> 2009/11/26 Alexandre Prokoudine : > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Sure, I've shifted manually as by default it goes into the middle of the screen (as the calibration square is in the center) -- better ideas welcome. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 21:24:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:24:02 +0100 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <4c2c37f90911261324i570a102dsac872665b9e426fb@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Alexandre Prokoudine wrote: > Hi, > > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Why is this a problem? If this dialog would be displayed centered, it would end up under the actual calibration window. So this is a good thing... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 21:51:24 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:51:24 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> Message-ID: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> When display calibration finishes, the newly created profile does not >> show up in the list in gcm-prefs. > > Can you try now please. You "fixed" it, and "broke" it at the same time... Now, after generating a new profile, "None" gets selected, but "None" does actually display copyright/vendor information, and seems to load the VideoLUT associates with the new profile. So this is most likely a UI issue. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 22:04:31 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 23:04:31 +0100 Subject: Possible Regression: vendor/device metadata unknown Message-ID: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Hi, The profile I generated for my laptop a while back with an older checkout of gcm, seemed to semi-correctly detect vendor/device descriptions (154AT07-H01/154AT07-H01). When looking this up in my xorg.0.log, this should be: (WW) intel(0): Unknown vendor-specific block f (II) intel(0): SAMSUNG (II) intel(0): 154AT07-H01 However, a current git checkout produces this: ASCII data, length 21 chars: 0x0000: unknown manufacturer ASCII data, length 14 chars: 0x0000: unknown model If you require more information, please let me know. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Thu Nov 26 22:44:15 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 01:44:15 +0300 Subject: shifted dialog In-Reply-To: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> Message-ID: <733f2c730911261444v5ccee119j1b8fd0d3f899ec76@mail.gmail.com> On 11/27/09, Richard Hughes wrote: > Sure, I've shifted manually as by default it goes into the middle of > the screen (as the calibration square is in the center) -- better > ideas welcome. Ah, makes sense then. Sorry for the trouble. Alexandre From hughsient at gmail.com Fri Nov 27 11:13:01 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:13:01 +0000 Subject: Possible Regression: vendor/device metadata unknown In-Reply-To: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> References: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Message-ID: <15e53e180911270313q7a4e4ee9vce5dded99384a341@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > ?ASCII data, length 21 chars: > ? ?0x0000: unknown manufacturer > ?ASCII data, length 14 chars: > ? ?0x0000: unknown model > > If you require more information, please let me know. Can you pull git please, compile, and then run "./gcm-dump-edid" and then reply with the generated *.bin files attached. The complete log files for gcm-prefs would also be helpful. Thanks. Richard. From hughsient at gmail.com Fri Nov 27 11:35:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:35:46 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> Message-ID: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Now, after generating a new profile, "None" gets selected, but "None" > does actually display copyright/vendor information, and seems to load > the VideoLUT associates with the new profile. So this is most likely a > UI issue. Right, can you try one more time please. Thanks, Richard. From pmjdebruijn at pcode.nl Fri Nov 27 17:32:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 27 Nov 2009 18:32:59 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> Message-ID: <4c2c37f90911270932x1155c1c8k2525e5245c2856cf@mail.gmail.com> On Fri, Nov 27, 2009 at 12:35 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> Now, after generating a new profile, "None" gets selected, but "None" >> does actually display copyright/vendor information, and seems to load >> the VideoLUT associates with the new profile. So this is most likely a >> UI issue. > > Right, can you try one more time please. Thanks, Jep, that seems fixed as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:11:17 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:11:17 +0100 Subject: Bug: Recalibrating a display twice makes a single profile show up twice Message-ID: <4c2c37f90911280511v62082445i88480e326510c14b@mail.gmail.com> Hi, I think I found a small bug, when recalibrating a display twice (without restarting gcm-prefs), only a single ~/.color/icc/mydisplay.icc is generated however (actually two files are generated obviously, but the first is just overwritten by the second), it is added twice to the profile combobox in gcm-prefs. To reproduce: 1. Start gcm-prefs 2. Calibrate 3. Calibrate (again) 4. Now you'll notice the single ICC profile is listed twice in the combobox. The bigger question is what behavior do we want? 1. The slightly older profile is overwritten, and only the newer profile is displayed (once) in the gcm-prefs combo box. This makes a calibration history impossible. 2. Each calibration run, suffixes the profile filename (currently based on the serial???) with date and time (important, since we other can only calibrate once a day, without overwrites) to prevent older ones from getting overwritten. This automatically makes the current behavior of gcm-prefs correct by adding a new profile to the combobox. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:16:08 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:16:08 +0100 Subject: Profile Filenames Message-ID: <4c2c37f90911280516o40d616f6pb2a4dcae0594afb4@mail.gmail.com> Hi, I noticed gcm(-prefs) currently places newly generated profiles as: ~/.color/icc/serial.icc As I already indicated I think it would be wise to at least include date and time in the filename. I'd prefer something more human readable over the serial as well: ~/.color/icc/gcm_acer-al2016w_200911281415.icc As you'll noticed above, I think it's a good idea to also prefix gcm-prefs generated profiles with gcm, to clearly distinguish between profiles generated by gcm-prefs, and profiles gotten elsewhere (possibly from the vendor CD). I'd love to hear your thoughts on this. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:30:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:30:28 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> Message-ID: <4c2c37f90911280530i63ed52a9w989833570c5146df@mail.gmail.com> On Wed, Nov 25, 2009 at 6:48 PM, Richard Hughes wrote: > 2009/11/25 Pascal de Bruijn : >> Has this been disabled on purpose, or is this an accidental regression? > > The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Sorry, it took me a while to verify, but on my external display I can indeed confirm this has been fixed. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 17:43:55 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 18:43:55 +0100 Subject: auto hardware detection not working Message-ID: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Hi, I enabled hardware detection in my builds of GNOME Color Manager. However it's not working, the "Calibrate" button is enabled, no matter if a colorimeter is attached or not. Assuming gcm-prefs isn't the problem, I'm guessing this would be a udev issue? Or better a udev rules issue? Is anybody willing to give me some pointers on how to debug this issue? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Nov 28 20:49:26 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 28 Nov 2009 20:49:26 +0000 Subject: auto hardware detection not working In-Reply-To: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Message-ID: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> 2009/11/28 Pascal de Bruijn : > Is anybody willing to give me some pointers on how to debug this issue? Can you attach the output of gnome-color-manager --verbose as you plug in and plug out the adaptor please? Thanks. Richard. From pmjdebruijn at pcode.nl Sun Nov 29 12:53:39 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sun, 29 Nov 2009 13:53:39 +0100 Subject: Profile description for laptop displays Message-ID: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Hi, Currently GCM is using EDID to determine make and models for displays. This information is then usually incorporated into the profile make/model and description. For external displays this is great behavior, however for laptops this may get a bit confusing. An example: My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's display. However, whenever a user wants to assign a profile to his laptop screen, it's not obvious this HP laptop needs a profile with Samsung in it's description. This may confuse people. So for laptop display _descriptions_ it might be a good idea to use the DMI Product Name instead of the panels EDID. pmjdebruijn at unicron:~$ sudo dmidecode | grep -i compaq Product Name: HP Compaq 6730s Please do note, I think we should keep using the panel's EDID for the ICC profile make/model tags, since this is technically correct, no matter if it's a laptop display or not. Only the description needs to be made user friendly. Regards, Pascal de Bruijn From hughsient at gmail.com Sun Nov 29 21:42:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 29 Nov 2009 21:42:33 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Message-ID: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's > display. ?However, whenever a user wants to assign a profile to his > laptop screen, it's not obvious this HP laptop needs a profile with > Samsung in it's description. This may confuse people. Agreed: commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de Author: Richard Hughes Date: Sun Nov 29 21:04:48 2009 +0000 Use DMI data to improve the device title and fill in missing model information :100644 100644 4504005... 0289dbd... M src/gcm-client.c commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 Author: Richard Hughes Date: Sun Nov 29 21:04:15 2009 +0000 Add a GcmDmi object to parse DMI data about the host machine :100644 100644 76796f2... c6b219b... M src/Makefile.am :000000 100644 0000000... ed48ea9... A src/gcm-dmi.c :000000 100644 0000000... 0a4897c... A src/gcm-dmi.h :100644 100644 0a4bbb4... 5624175... M src/gcm-self-test.c Can you verify the new functionality please. Thanks. Richard. From alexandre.prokoudine at gmail.com Sun Nov 29 23:38:27 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 02:38:27 +0300 Subject: hardware autodetection Message-ID: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Hi, What do I need to have installed in my system to get hardware auto-detection: yes after running ./configure ? I do see "checking for GUDEV... yes" in the output. Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:41:58 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:41:58 +0100 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> On Mon, Nov 30, 2009 at 12:38 AM, Alexandre Prokoudine wrote: > Hi, > > What do I need to have installed in my system to get > > hardware auto-detection: ? yes > > after running ./configure ? > > I do see "checking for GUDEV... yes" in the output. You need a new ArgyllCMS release with the new udev rules. ArgyllCMS 1.1.0-rc should do. My Debian package has the following Build-Depends: Build-Depends: debhelper (>= 7), autotools-dev, cdbs, dpatch, docbook-utils, gtk-doc-tools, gnome-doc-utils, libx11-dev, libxxf86vm-dev, libxrandr-dev, libglib2.0-dev, libgtk2.0-dev, libgnome-desktop-dev, libgconf2-dev, libunique-dev (>= 1.0), libvte-dev (>= 0.22), libgudev-1.0-dev, libdbus-glib-1-dev Then it should work. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sun Nov 29 23:46:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:46:02 +0100 Subject: auto hardware detection not working In-Reply-To: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> Message-ID: <4c2c37f90911291546n19ee7040j48af2ef424e74209@mail.gmail.com> On Sat, Nov 28, 2009 at 9:49 PM, Richard Hughes wrote: > 2009/11/28 Pascal de Bruijn : >> Is anybody willing to give me some pointers on how to debug this issue? > > Can you attach the output of gnome-color-manager --verbose as you plug > in and plug out the adaptor please? Thanks. I think I was mistaken, it seems to work now. My bad. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Mon Nov 30 01:14:10 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 04:14:10 +0300 Subject: hardware autodetection In-Reply-To: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> Message-ID: <733f2c730911291714l7536bba9n74c11bb3b000591a@mail.gmail.com> On 11/30/09, Pascal de Bruijn wrote: > You need a new ArgyllCMS release with the new udev rules. ArgyllCMS > 1.1.0-rc should do. Well, it's argyll-1.1.0-rc1-3pmjdebruijn0~karmic all the way here :) Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:27:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:27:59 +0100 Subject: Profile description for laptop displays In-Reply-To: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> Message-ID: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> On Sun, Nov 29, 2009 at 10:42 PM, Richard Hughes wrote: > 2009/11/29 Pascal de Bruijn : >> My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's >> display. ?However, whenever a user wants to assign a profile to his >> laptop screen, it's not obvious this HP laptop needs a profile with >> Samsung in it's description. This may confuse people. > > Agreed: > > commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de > commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 > > Can you verify the new functionality please. Thanks. That was fast as usual :) It works mostly... I've attached a screenshot. I noticed you included the product_version as well, at least on my laptop it's actually the BIOS revision, I'm not sure what this is on other laptops. It's probably not that relevant... I noticed you're currently filling the ICC Make with the username, it seems rather redundant with the copyright. Besides the point that the field wasn't ment to be used like that. I'd stick the EDID info there (even with laptops). For the Model field as well, EDID is most likely best and most accurate here. For example: Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, only lookup in the gcm-prefs GUI). Model: 154AT07-H01 Storing the EDID info as verbatim as possible in the ICC make/models fields, will make it easier to auto match displays and profiles in the future. Storing the EDID verbatim without looking up in pnp.ids prevents false data from conflicting lookups (like my Samsung/Seiko issue) from ending up in the profile itself. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-dmi.png Type: image/png Size: 44070 bytes Desc: not available URL: From hughsient at gmail.com Mon Nov 30 08:19:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 08:19:46 +0000 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <15e53e180911300019x1c1a7cfbu43741868d045dce4@mail.gmail.com> 2009/11/29 Alexandre Prokoudine : > What do I need to have installed in my system to get You need to configure with --enable-hardware-detection and to make sure you have the fixed Argyllcms udev rules file. Richard. From hughsient at gmail.com Mon Nov 30 10:10:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 10:10:34 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> Message-ID: <15e53e180911300210tae5b9a0kaa94ead83633e413@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > I noticed you included the product_version as well, at least on my > laptop it's actually the BIOS revision, I'm not sure what this is on > other laptops. It's probably not that relevant... Hmm, it seems the manufacturers were in a rush when they designed your laptop! The bios version, logically, belongs in bios_version :-) Could you attach the output of "cat /sys/class/dmi/id/*" and we'll try and work around bios issues like this. Thanks. > I noticed you're currently filling the ICC Make with the username, it > seems rather redundant with the copyright. Besides the point that the > field wasn't ment to be used like that. I'd stick the EDID info there > (even with laptops). For the Model field as well, EDID is most likely > best and most accurate here. I deliberately changed it, as the vendor is supposed to be the person or company that designed or created the profile. In this sense, it seemed wrong to say that the profile was created "by Lenovo" when it was created by me, for my Lenovo display. > For example: > > Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, > only lookup in the gcm-prefs GUI). > Model: 154AT07-H01 > > Storing the EDID info as verbatim as possible in the ICC make/models > fields, will make it easier to auto match displays and profiles in the > future. Hmm, I think the fields have to be displayable. We need to look at adding private fields if we want to add any machine parsable data into the ICC file. > Storing the EDID verbatim without looking up in pnp.ids prevents false > data from conflicting lookups (like my Samsung/Seiko issue) from > ending up in the profile itself. I think the lookup is valuable as it works most of the time. Your panel should have encoded SAM into the PNP field, not SEC, unless of course the panel really is a Seiko panel that's been rebadged as a Samsung. For what it's worth, my nice expensive LG panel is actually a generic Goldstar chipset with LG additions and plastic wrapping. Hence, it shows up as "Goldstar" as the vendor. :-( Richard. From pmjdebruijn at pcode.nl Tue Nov 10 18:35:36 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 10 Nov 2009 19:35:36 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: <1257878136.9870.4.camel@goliath> Hi, I have a HP Photosmart C6280 (all-in-one), which is connected via HP JetDirect (Ethernet). Currently it is not being detected by GNOME Color Manager, while I can print, and XSane does recognize the scanner... I'm assuming this is because currently only USB connected devices are checked? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From hughsient at gmail.com Tue Nov 10 18:42:39 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 18:42:39 +0000 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) In-Reply-To: <1257878136.9870.4.camel@goliath> References: <1257878136.9870.4.camel@goliath> Message-ID: <15e53e180911101042k5746e765i185677d1957e3198@mail.gmail.com> 2009/11/10 Pascal de Bruijn : > I have a HP Photosmart C6280 (all-in-one), which is connected via HP > JetDirect (Ethernet). > Currently it is not being detected by GNOME Color Manager, while I can > print, and XSane does recognize the scanner... > I'm assuming this is because currently only USB connected devices are > checked? Correct. How does xsane recognise the scanner? At the moment we're just checking USB printers that use hplip and scanners that are matched with libsane. If you can work out how to identify the device using a property in udev, then it's an easy add. I'm not sure how the ethernet printing and scanning stuff actually works right now. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 19:35:48 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 20:35:48 +0100 Subject: A small bug Message-ID: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> I'm stumbled over this when I interrupted a profile creation. My target profile name was the same as set before with gcm-prefs. I ended up with the entire gcm-prefs gui blocked. Se attached screenshoot. I have reproduced it and attached a log file. If I do a "head -c 100 /dev/random > i1.icc" where i1.icc is my gcm-prefs chosen profile I got this messages in log: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected **************************************************** With a large file like this: "head -c 500 /dev/random > i1.icc" I got: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-log.txt.zip Type: application/zip Size: 2093 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: corrupt.png Type: image/png Size: 20741 bytes Desc: not available URL: From hughsient at gmail.com Tue Nov 10 20:08:28 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 20:08:28 +0000 Subject: A small bug In-Reply-To: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> Message-ID: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> 2009/11/10 Lars Tore Gustavsen : > I have reproduced it and attached a log file. > If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my > gcm-prefs chosen profile I got this messages in log: Can you try with git now please. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 21:35:09 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 22:35:09 +0100 Subject: A small bug In-Reply-To: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> Message-ID: <58497f010911101335g317529bev8f1e48d780e3ab5d@mail.gmail.com> On Tue, Nov 10, 2009 at 9:08 PM, Richard Hughes wrote: > 2009/11/10 Lars Tore Gustavsen : >> I have reproduced it and attached a log file. >> If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my >> gcm-prefs chosen profile I got this messages in log: > > Can you try with git now please. Thanks. > > Richard. > It works very well, thank you. Lars Tore From lars.tore at mulebakken.net Wed Nov 11 11:51:06 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 12:51:06 +0100 Subject: Bluish.icc Message-ID: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> The icc profile include with gnome-color-manager is very nice to test if everything works. However it advertise itself as "sRGB IEC61966-2-1" I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: bluish.icc Type: application/octet-stream Size: 3962 bytes Desc: not available URL: From hughsient at gmail.com Wed Nov 11 11:59:55 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 11:59:55 +0000 Subject: Bluish.icc In-Reply-To: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> Message-ID: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> 2009/11/11 Lars Tore Gustavsen : > I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Committed, thanks. Richard. From fred at crozat.net Wed Nov 11 12:53:41 2009 From: fred at crozat.net (Frederic Crozat) Date: Wed, 11 Nov 2009 13:53:41 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> Message-ID: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> 2009/11/11 Richard Hughes : > 2009/11/11 Lars Tore Gustavsen : >> I have edited the attached profile and it now reads "bluish test" in gcm-prefs. > > Committed, thanks. In the same idea, it could be interesting to bundle a "test" jpg or png image in gnome-color-manager which would be only visible (or display correctly) when ICC profiles are correctly handled by applications. I use either http://1reflet.skynetblogs.be/post/6632777/profil-colorimetrique-utilisateur-firefox (sorry it is in french, flower is supposed to be displayed in yellow, not pink) or http://www.color.org/version4html.xalter I don't the license of those images are compatible with free software but creating similar images would be useful. WDYT ? -- Frederic Crozat From hughsient at gmail.com Wed Nov 11 13:12:09 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 13:12:09 +0000 Subject: Bluish.icc In-Reply-To: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> Message-ID: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> 2009/11/11 Frederic Crozat : > I don't the license of those images are compatible with free software > but creating similar images would be useful. > WDYT ? I think it's a good idea, although the licence would have to be CC_BY_SA or something like that to be allowed in gcm. Can anybody find suitably licensed example photographs? We also want the gamma checker images, but alas, these have to be free too. Richard. From anders at brander.dk Wed Nov 11 13:43:43 2009 From: anders at brander.dk (Anders Brander) Date: Wed, 11 Nov 2009 14:43:43 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> Message-ID: <1257947023.29790.3.camel@smutogtab> Hi, On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > 2009/11/11 Frederic Crozat : > > I don't the license of those images are compatible with free software > > but creating similar images would be useful. > > WDYT ? > > I think it's a good idea, although the licence would have to be > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > suitably licensed example photographs? We also want the gamma checker > images, but alas, these have to be free too. I'm not sure what is meant here. If we need an image to test whether an ICC profile is respected, one could create an image with swapped red/green channels - and then embed a ICC-profile undoing that. It would be obvious if the profile is respected or not when viewing the image. Well... /Anders Brander From hughsient at gmail.com Wed Nov 11 14:38:15 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 14:38:15 +0000 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> 2009/11/11 Anders Brander : > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. Yes, I think that would be a good idea for testing purposes. Richard. From lars.tore at mulebakken.net Wed Nov 11 16:58:23 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 17:58:23 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> Message-ID: <58497f010911110858x42131154p3217ff2015f60f45@mail.gmail.com> On Wed, Nov 11, 2009 at 3:38 PM, Richard Hughes wrote: > 2009/11/11 Anders Brander : >> I'm not sure what is meant here. If we need an image to test whether an >> ICC profile is respected, one could create an image with swapped >> red/green channels - and then embed a ICC-profile undoing that. It would >> be obvious if the profile is respected or not when viewing the image. > > Yes, I think that would be a good idea for testing purposes. > > Richard. I often play with "dispwin -V profilename" to check correct loading of the clut. So that's another idea. Lars Tore Gustavsen From pmjdebruijn at pcode.nl Wed Nov 11 17:26:04 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 11 Nov 2009 18:26:04 +0100 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <1257960364.6073.7.camel@goliath> On Wed, 2009-11-11 at 14:43 +0100, Anders Brander wrote: > Hi, > > On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > > 2009/11/11 Frederic Crozat : > > > I don't the license of those images are compatible with free software > > > but creating similar images would be useful. > > > WDYT ? > > > > I think it's a good idea, although the licence would have to be > > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > > suitably licensed example photographs? We also want the gamma checker > > images, but alas, these have to be free too. > > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. We can have two purposes for the image: 1. See if the profile is loaded properly at all 2. See if the profile is in the right ballpark (regarding accuracy) While the following image surely isn't CC licensed, something similar to this would be just perfect: http://www.smugmug.com/help/calibration-1400.mg -- http://blog.pcode.nl/ http://photos.pcode.nl/ From memolus at googlemail.com Thu Nov 12 19:56:09 2009 From: memolus at googlemail.com (memolus at googlemail.com) Date: Thu, 12 Nov 2009 20:56:09 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: 2009/11/10 Richard Hughes : > Correct. How does xsane recognise the scanner? At the moment we're > just checking USB printers that use hplip and scanners that are > matched with libsane. If you can work out how to identify the device > using a property in udev, then it's an easy add. I'm not sure how the > ethernet printing and scanning stuff actually works right now. Thanks. I don't know how deep you know the details about the network support of hplip, but here's what I know, as an introduction: The printer and the scanner is identified by an URI "hp:/net/Photosmart_C6200_series?ip=192.168.0.2" (fax has hpfax:/ instead of hp:/) in cups and sane ("Photosmart_C6200_series:Photosmart_C6200_series?ip=192.168.0.2") using the hplip driver, and treated as an local device. Normal network printers have URIs like "socket://printer:9100". It's detectable using Zeroconf (dnssd://photosmart c6200 series [d44b9e]._pdl-datastream._tcp.local/) and UPnP, cause HP supports Mac and Windows. Actually automatic detection of hp photosmart all-in-one devices in system-config-printer-gnome is broken, but automatic detection works using gnome-cups-manager und sane. From lars.tore at mulebakken.net Fri Nov 13 16:38:42 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Fri, 13 Nov 2009 17:38:42 +0100 Subject: Fighting with the screensaver. Message-ID: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> First I wonder if I'm the only person now who fights with the lut deletion with gnome-screensaver. It almost look like it is fixed, but I have still have this problem with ubuntu 9.10. https://bugzilla.gnome.org/show_bug.cgi?id=342850 Should I expect the color manager to take care of this on it own? Like running some kind of services? When I use dispwin from the argyll package I normally take care of this with a desktop file in the autostart folder with an exec line like this. Exec=/bin/bash -c ? gnome-screensaver-command ?exit; dispwin -L;gnome-screensaver? I recently tried gcm on an xubuntu (xface)box and it worked very well, but I guess the reason was it used xscreensaver instead of gnome-screensaver. From fred at crozat.net Fri Nov 13 16:46:36 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 17:46:36 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> 2009/11/13 Lars Tore Gustavsen : > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally ?take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > ?dispwin -L;gnome-screensaver? gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in it) needs to be fixed to correctly save LUT before fading gamma at screensaver startup and restore it when it quits. I haven't found time to investigate before 2.28 was released :( -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 16:50:16 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 16:50:16 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> Message-ID: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> 2009/11/13 Frederic Crozat : > gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in > it) needs to be fixed to correctly save LUT before fading gamma at > screensaver startup and restore it when it quits. Or, gnome-screensaver could just call gcm-apply which resets everything as well. Richard. From pmjdebruijn at pcode.nl Fri Nov 13 16:56:50 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 13 Nov 2009 17:56:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <4c2c37f90911130856m5fdcd776vbc8e9b84a934d011@mail.gmail.com> On Fri, Nov 13, 2009 at 5:50 PM, Richard Hughes wrote: > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. While these are all solutions, the short term workaround is simply to not use a screensaver, and only have display power saving enabled :) I know it's lame... but screensavers don't have any real function any more, or do they? Regards, Pascal de Bruijn From fred at crozat.net Fri Nov 13 21:05:10 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:05:10 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. That would imply a dependency on gcm, which is not a really good idea. I really think gnome-screensaver should restore LUT after the fading (after all, I also want the pictures used for slideshow in screensaver to be correctly color managed ;) -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 21:12:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 21:12:34 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> Message-ID: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> 2009/11/13 Frederic Crozat : > That would imply a dependency on gcm, which is not a really good idea. Sure, but the sort of dependency where it doesn't matter if gcm-apply doesn't exist... > I really think gnome-screensaver should restore LUT after the fading > (after all, I also want the pictures used for slideshow in screensaver > to be correctly color managed ;) That is true. Richard. From fred at crozat.net Fri Nov 13 21:25:59 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:25:59 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> Message-ID: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> That would imply a dependency on gcm, which is not a really good idea. > > Sure, but the sort of dependency where it doesn't matter if gcm-apply > doesn't exist... It does if people uses dispwin manually (or anything else to change LUT) ;) -- Frederic Crozat From amluto at gmail.com Fri Nov 13 21:56:42 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Fri, 13 Nov 2009 16:56:42 -0500 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> Message-ID: On Fri, Nov 13, 2009 at 4:25 PM, Frederic Crozat wrote: > 2009/11/13 Richard Hughes : >> 2009/11/13 Frederic Crozat : >>> That would imply a dependency on gcm, which is not a really good idea. >> >> Sure, but the sort of dependency where it doesn't matter if gcm-apply >> doesn't exist... > > It does if people uses dispwin manually (or anything else to change LUT) ;) ISTM that gnome-screensaver would ideally just not touch the LUT. These days we have compositing, or even just taking a screen shot and fading to black with RENDER, for that. --Andy > > -- > Frederic Crozat > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pmjdebruijn at pcode.nl Sat Nov 14 18:23:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 14 Nov 2009 19:23:51 +0100 Subject: Standby also seems to reset the VideoLUT/crtc Message-ID: <1258223031.9981.3.camel@goliath> Hi, Similarly as discussed in "Re: Fighting with the screensaver." it also seems putting your laptop to sleep (standby) seems to reset the VideoLUT/xrandr crtc's... Can anybody test and confirm this... I have a Intel X4500MHD graphics chip, however, if I'm not mistaken the driver card/driver actually doesn't have anything to do with this, with the vcgt tag is applied via Xorg/xrandr. Or am I wrong about this? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From compiz at sukimashita.com Sat Nov 14 19:19:20 2009 From: compiz at sukimashita.com (Martin S.) Date: Sat, 14 Nov 2009 20:19:20 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <1258226360.12545.10.camel@mirell> On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 This is somewhat old. I remember working on that bug myself as it was annoying for both gnome-screensaver and xscreensaver if I had profiles set. However, the issue was clearly fixed and I did't see this anymore on a range of systems since then (nvidia, intel mostly). > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > dispwin -L;gnome-screensaver? This is not the right solution afaik. Applications should not fiddle with the color profile settings unless they are created to do just that. If you are sure gnome-screensaver causes it please file a bug. gnome-screensaver must respect the LUT settings here (the code apparently does already...). As noted above, this works fine on a couple of systems I tested for 2.28. What gfx driver do you use and which component versions (xorg, driver, gnome-screensaver? --- Martin S. From amluto at gmail.com Sat Nov 14 19:54:41 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sat, 14 Nov 2009 14:54:41 -0500 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: On my system, whatever xorg-xserver version F11 used interacted badly with intel to cause all kinds of things to reset the LUTs. For example, resuming, switching VTs, and even starting glxgears or okular (!). This has been fixed upstream and in F12. --Andy On Sat, Nov 14, 2009 at 2:19 PM, Martin S. wrote: > On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: >> First I wonder if I'm the only person now who fights with the lut >> deletion with gnome-screensaver. >> It almost look like it is fixed, but I have still have this problem >> with ubuntu 9.10. >> https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > This is somewhat old. I remember working on that bug myself as it was > annoying for both gnome-screensaver and xscreensaver if I had profiles > set. > > However, the issue was clearly fixed and I did't see this anymore on a > range of systems since then (nvidia, intel mostly). > >> Should I expect the color manager to take care of this on it own? Like >> running some kind of services? >> When I use dispwin from the argyll package I normally ?take care of >> this with a desktop file in the autostart folder with an exec line >> like this. >> Exec=/bin/bash -c ? gnome-screensaver-command ?exit; >> ?dispwin -L;gnome-screensaver? > > This is not the right solution afaik. Applications should not fiddle > with the color profile settings unless they are created to do just that. > > If you are sure gnome-screensaver causes it please file a bug. > gnome-screensaver must respect the LUT settings here (the code > apparently does already...). > > As noted above, this works fine on a couple of systems I tested for > 2.28. > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > > --- Martin S. > > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list From compiz at sukimashita.com Sun Nov 15 02:04:29 2009 From: compiz at sukimashita.com (Martin S.) Date: Sun, 15 Nov 2009 03:04:29 +0100 Subject: [PATCH] Enable adding xrandr devices with no EDID Message-ID: <1258250669.25043.1.camel@mirell> Devices without EDID information or bad XRANDR implementations work again and get standard properties set. This restores functionality that existed before a recent change and allows me to assign color profiles on the broken nvidia xrandr implementation again. --- Martin S. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Enable-adding-xrandr-devices-with-no-EDID.patch Type: text/x-patch Size: 1874 bytes Desc: not available URL: From hughsient at gmail.com Sun Nov 15 15:03:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:03:32 +0000 Subject: [PATCH] Enable adding xrandr devices with no EDID In-Reply-To: <1258250669.25043.1.camel@mirell> References: <1258250669.25043.1.camel@mirell> Message-ID: <15e53e180911150703r28ba9e0dm9a1fbf760b2ab6ea@mail.gmail.com> 2009/11/15 Martin S. : > This restores functionality that existed before a recent change and > allows me to assign color profiles on the broken nvidia xrandr > implementation again. Applied, thanks. Richard. From hughsient at gmail.com Sun Nov 15 15:30:12 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:30:12 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <1258223031.9981.3.camel@goliath> References: <1258223031.9981.3.camel@goliath> Message-ID: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> 2009/11/14 Pascal de Bruijn : > Similarly as discussed in "Re: Fighting with the screensaver." it also > seems putting your laptop to sleep (standby) seems to reset the > VideoLUT/xrandr crtc's... Seems plausible, although I would argue we should probably just get X or the kernel to save the gamma tables on suspend and restore them on resume. It certainly seems a better idea then getting the session to do it. Richard. From amluto at gmail.com Sun Nov 15 15:33:14 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 10:33:14 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 10:30 AM, Richard Hughes wrote: > 2009/11/14 Pascal de Bruijn : >> Similarly as discussed in "Re: Fighting with the screensaver." it also >> seems putting your laptop to sleep (standby) seems to reset the >> VideoLUT/xrandr crtc's... > > Seems plausible, although I would argue we should probably just get X > or the kernel to save the gamma tables on suspend and restore them on > resume. It certainly seems a better idea then getting the session to > do it. Heh, I replied to Pascal directly instead of to all. I think that X already does that with server 1.7 and up and (on my machine, anyway) intel driver 2.9.0 and up. (e.g. F12 but not F11) --Andy > > Richard. > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pedro at pedrocr.net Sun Nov 15 19:15:24 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 11:15:24 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: > Heh, I replied to Pascal directly instead of to all. ?I think that X > already does that with server 1.7 and up and (on my machine, anyway) > intel driver 2.9.0 and up. ?(e.g. F12 but not F11) I run Ubuntu Karmic (9.10) and this is not the case. I do have the 2.9.0 intel driver but the server is only 1.6.4. So I guess the config for it is in the xserver. Strangely when I set the ICC profile with xcalib it seems to survive the suspend. Pedro From amluto at gmail.com Sun Nov 15 19:40:15 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 14:40:15 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 2:15 PM, Pedro C?rte-Real wrote: > On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: >> Heh, I replied to Pascal directly instead of to all. ?I think that X >> already does that with server 1.7 and up and (on my machine, anyway) >> intel driver 2.9.0 and up. ?(e.g. F12 but not F11) > > I run Ubuntu Karmic (9.10) and this is not the case. I do have the > 2.9.0 intel driver but the server is only 1.6.4. So I guess the config > for it is in the xserver. Strangely when I set the ICC profile with > xcalib it seems to survive the suspend. I believe it requires some cooperation between both. In the intel driver, in drmmode_set_mode_major, it says: #if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1,7,0,0,0) crtc->funcs->gamma_set(crtc, crtc->gamma_red, crtc->gamma_green, crtc->gamma_blue, crtc->gamma_size); #endif --Andy > > Pedro > From lars.tore at mulebakken.net Sun Nov 15 20:42:50 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Sun, 15 Nov 2009 21:42:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: <58497f010911151242u54a7926am8f1a9128da6dec42@mail.gmail.com> On Sat, Nov 14, 2009 at 8:19 PM, Martin S. wrote: > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > I use ubuntu 9.10 and I have a ATI Radeon 9200 PRO card. I use the radeon xorg driver and the xorg version is 1.7.4. Gnome-screensaver is 2.28.0 Lars Tore Gustavsen From pedro at pedrocr.net Sun Nov 15 23:53:38 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 15:53:38 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> First, thanks for this Richard. Gnome/Linux have been needing this kind of simple support for color in a long time. On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: > Strangely when I set the ICC profile with xcalib it seems to survive the suspend. xcalib is probably doing something very different as its calibration also applies to all displays. On the other hand this means that it both survives the suspend and is applied when the display is disconnected/connected, both things that g-c-m currently doesn't handle properly. The suspend/resume stuff should be handled by X but the connect/disconnect should probably be handled by g-c-m as that policy shouldn't be in X. Cheers, Pedro From hughsient at gmail.com Mon Nov 16 08:29:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 16 Nov 2009 08:29:32 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> Message-ID: <15e53e180911160029u572db018x7d459eaf624c5765@mail.gmail.com> 2009/11/15 Pedro C?rte-Real : > First, thanks for this Richard. Gnome/Linux have been needing this > kind of simple support for color in a long time. > > On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: >> Strangely when I set the ICC profile with xcalib it seems to survive the suspend. > > xcalib is probably doing something very different as its calibration > also applies to all displays. xcalib sets the per-screen gamma tables, and gcm sets the per-output gamma tables. Richard. From pmjdebruijn at pcode.nl Wed Nov 25 17:28:33 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:28:33 +0100 Subject: Regression: gnome-color-manager segfaults after dispcal Message-ID: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Hi, Using gnome-color-manager 2.29.1~git20091124 it seems to segfault after running dispcal. Can anybody confirm this? Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Wed Nov 25 17:30:03 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:30:03 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown Message-ID: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Hi, On my external display (HP LP2475w) connected via DVI to my Intel GMA, the precalibration "tips/guidelines" dialog isn't shown anymore. Has this been disabled on purpose, or is this an accidental regression? Regards, Pascal de Bruijn From hughsient at gmail.com Wed Nov 25 17:40:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:40:57 +0000 Subject: Regression: gnome-color-manager segfaults after dispcal In-Reply-To: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> References: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Message-ID: <15e53e180911250940l2187d4e7s9755ed15edc867eb@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Using gnome-color-manager 2.29.1~git20091124 it seems to segfault > after running dispcal. You got a backtrace please? Thanks. Richard. From hughsient at gmail.com Wed Nov 25 17:48:20 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:48:20 +0000 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Message-ID: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Has this been disabled on purpose, or is this an accidental regression? The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 18:09:48 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:09:48 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore Message-ID: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Hi, It seems that gcm-prefs from current git does not apply the VideoLUT/vcgt tag anymore... gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 18:14:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:14:51 +0100 Subject: gcm-prefs: New profiles not showing up in the list Message-ID: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Hi, When display calibration finishes, the newly created profile does not show up in the list in gcm-prefs. Restarting gcm-prefs helps, then I _do_ see the new profile. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:24:32 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:24:32 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore In-Reply-To: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> References: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Message-ID: <4c2c37f90911261224h24d5eb10u1cb767adde26787a@mail.gmail.com> On Thu, Nov 26, 2009 at 7:09 PM, Pascal de Bruijn wrote: > Hi, > > It seems that gcm-prefs from current git does not apply the > VideoLUT/vcgt tag anymore... > > gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Changing the profile in gcm-prefs, closing gcm-prefs, and opening gcm-prefs again also does _not_ change the profile that is selected by default. So the problem is most likely not the application of another profile's VideoLUT, but the VideoLUT of the original default selected profile is always being applied, no matter which profile was manually selected afterward. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:54:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:54:28 +0100 Subject: Patch: Debian binary detection fix Message-ID: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Hi, I noticed the following recent commit to detect the Debinized Argyll binaries: http://git.gnome.org/cgit/gnome-color-manager/commit/?id=3b06571386be55a7b21424c256b88b2fb2ec6347 Conceptually the commit is fine, it's particularly great, this detect method is used for all of Argyll's utilities. Practically this is only applicable for targen at the moment. But since it's used for all binaries, gcm is automatically future proofed against other binaries getting renamed as well. Excellent behaviour. However, the detection is backwards. Please allow me to explain. Debian maintainers don't rename binaries just because they get a kick out of arbitrarily renaming random binaries. Debian has problems with conflicting binaries because their package repository is so big (almost 30,000 packages). This means they are forced to rename binaries in all but one package with conflicting binaries. This implies, on systems with a 'argyll-targen' binary, a 'targen' binary could be installed as well. But if a 'targen' binary is installed as well, it's most likely completely unrelated to Argyll, and will almost certainly fail when called by gcm. Therefore the detect should _first_ detect if the Debian renamed binaries exist, and if not, fallback to the original binary names. I've attached a small patch, which should "fix" the issue described above. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-debian-fix.patch Type: text/x-patch Size: 1022 bytes Desc: not available URL: From hughsient at gmail.com Thu Nov 26 21:07:11 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:07:11 +0000 Subject: Patch: Debian binary detection fix In-Reply-To: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> References: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Message-ID: <15e53e180911261307l6b8b4427g13bc6de54b014f00@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Therefore the detect should _first_ detect if the Debian renamed > binaries exist, and if not, fallback to the original binary names. Agreed. I've attached the patch I've committed. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: look-for-debian-first.patch Type: text/x-patch Size: 1063 bytes Desc: not available URL: From alexandre.prokoudine at gmail.com Thu Nov 26 21:18:51 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 00:18:51 +0300 Subject: shifted dialog Message-ID: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Hi, The dialog that suggests to plug-in a measurement device somewhat unexpectedly pops up close to the left border of the screen, which is quite unfortunate for a 24" display :) Alexandre From hughsient at gmail.com Thu Nov 26 21:18:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:18:57 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Message-ID: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > When display calibration finishes, the newly created profile does not > show up in the list in gcm-prefs. Can you try now please. Thanks, Richard. From hughsient at gmail.com Thu Nov 26 21:22:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:22:33 +0000 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> 2009/11/26 Alexandre Prokoudine : > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Sure, I've shifted manually as by default it goes into the middle of the screen (as the calibration square is in the center) -- better ideas welcome. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 21:24:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:24:02 +0100 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <4c2c37f90911261324i570a102dsac872665b9e426fb@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Alexandre Prokoudine wrote: > Hi, > > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Why is this a problem? If this dialog would be displayed centered, it would end up under the actual calibration window. So this is a good thing... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 21:51:24 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:51:24 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> Message-ID: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> When display calibration finishes, the newly created profile does not >> show up in the list in gcm-prefs. > > Can you try now please. You "fixed" it, and "broke" it at the same time... Now, after generating a new profile, "None" gets selected, but "None" does actually display copyright/vendor information, and seems to load the VideoLUT associates with the new profile. So this is most likely a UI issue. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 22:04:31 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 23:04:31 +0100 Subject: Possible Regression: vendor/device metadata unknown Message-ID: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Hi, The profile I generated for my laptop a while back with an older checkout of gcm, seemed to semi-correctly detect vendor/device descriptions (154AT07-H01/154AT07-H01). When looking this up in my xorg.0.log, this should be: (WW) intel(0): Unknown vendor-specific block f (II) intel(0): SAMSUNG (II) intel(0): 154AT07-H01 However, a current git checkout produces this: ASCII data, length 21 chars: 0x0000: unknown manufacturer ASCII data, length 14 chars: 0x0000: unknown model If you require more information, please let me know. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Thu Nov 26 22:44:15 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 01:44:15 +0300 Subject: shifted dialog In-Reply-To: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> Message-ID: <733f2c730911261444v5ccee119j1b8fd0d3f899ec76@mail.gmail.com> On 11/27/09, Richard Hughes wrote: > Sure, I've shifted manually as by default it goes into the middle of > the screen (as the calibration square is in the center) -- better > ideas welcome. Ah, makes sense then. Sorry for the trouble. Alexandre From hughsient at gmail.com Fri Nov 27 11:13:01 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:13:01 +0000 Subject: Possible Regression: vendor/device metadata unknown In-Reply-To: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> References: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Message-ID: <15e53e180911270313q7a4e4ee9vce5dded99384a341@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > ?ASCII data, length 21 chars: > ? ?0x0000: unknown manufacturer > ?ASCII data, length 14 chars: > ? ?0x0000: unknown model > > If you require more information, please let me know. Can you pull git please, compile, and then run "./gcm-dump-edid" and then reply with the generated *.bin files attached. The complete log files for gcm-prefs would also be helpful. Thanks. Richard. From hughsient at gmail.com Fri Nov 27 11:35:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:35:46 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> Message-ID: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Now, after generating a new profile, "None" gets selected, but "None" > does actually display copyright/vendor information, and seems to load > the VideoLUT associates with the new profile. So this is most likely a > UI issue. Right, can you try one more time please. Thanks, Richard. From pmjdebruijn at pcode.nl Fri Nov 27 17:32:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 27 Nov 2009 18:32:59 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> Message-ID: <4c2c37f90911270932x1155c1c8k2525e5245c2856cf@mail.gmail.com> On Fri, Nov 27, 2009 at 12:35 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> Now, after generating a new profile, "None" gets selected, but "None" >> does actually display copyright/vendor information, and seems to load >> the VideoLUT associates with the new profile. So this is most likely a >> UI issue. > > Right, can you try one more time please. Thanks, Jep, that seems fixed as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:11:17 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:11:17 +0100 Subject: Bug: Recalibrating a display twice makes a single profile show up twice Message-ID: <4c2c37f90911280511v62082445i88480e326510c14b@mail.gmail.com> Hi, I think I found a small bug, when recalibrating a display twice (without restarting gcm-prefs), only a single ~/.color/icc/mydisplay.icc is generated however (actually two files are generated obviously, but the first is just overwritten by the second), it is added twice to the profile combobox in gcm-prefs. To reproduce: 1. Start gcm-prefs 2. Calibrate 3. Calibrate (again) 4. Now you'll notice the single ICC profile is listed twice in the combobox. The bigger question is what behavior do we want? 1. The slightly older profile is overwritten, and only the newer profile is displayed (once) in the gcm-prefs combo box. This makes a calibration history impossible. 2. Each calibration run, suffixes the profile filename (currently based on the serial???) with date and time (important, since we other can only calibrate once a day, without overwrites) to prevent older ones from getting overwritten. This automatically makes the current behavior of gcm-prefs correct by adding a new profile to the combobox. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:16:08 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:16:08 +0100 Subject: Profile Filenames Message-ID: <4c2c37f90911280516o40d616f6pb2a4dcae0594afb4@mail.gmail.com> Hi, I noticed gcm(-prefs) currently places newly generated profiles as: ~/.color/icc/serial.icc As I already indicated I think it would be wise to at least include date and time in the filename. I'd prefer something more human readable over the serial as well: ~/.color/icc/gcm_acer-al2016w_200911281415.icc As you'll noticed above, I think it's a good idea to also prefix gcm-prefs generated profiles with gcm, to clearly distinguish between profiles generated by gcm-prefs, and profiles gotten elsewhere (possibly from the vendor CD). I'd love to hear your thoughts on this. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:30:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:30:28 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> Message-ID: <4c2c37f90911280530i63ed52a9w989833570c5146df@mail.gmail.com> On Wed, Nov 25, 2009 at 6:48 PM, Richard Hughes wrote: > 2009/11/25 Pascal de Bruijn : >> Has this been disabled on purpose, or is this an accidental regression? > > The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Sorry, it took me a while to verify, but on my external display I can indeed confirm this has been fixed. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 17:43:55 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 18:43:55 +0100 Subject: auto hardware detection not working Message-ID: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Hi, I enabled hardware detection in my builds of GNOME Color Manager. However it's not working, the "Calibrate" button is enabled, no matter if a colorimeter is attached or not. Assuming gcm-prefs isn't the problem, I'm guessing this would be a udev issue? Or better a udev rules issue? Is anybody willing to give me some pointers on how to debug this issue? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Nov 28 20:49:26 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 28 Nov 2009 20:49:26 +0000 Subject: auto hardware detection not working In-Reply-To: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Message-ID: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> 2009/11/28 Pascal de Bruijn : > Is anybody willing to give me some pointers on how to debug this issue? Can you attach the output of gnome-color-manager --verbose as you plug in and plug out the adaptor please? Thanks. Richard. From pmjdebruijn at pcode.nl Sun Nov 29 12:53:39 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sun, 29 Nov 2009 13:53:39 +0100 Subject: Profile description for laptop displays Message-ID: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Hi, Currently GCM is using EDID to determine make and models for displays. This information is then usually incorporated into the profile make/model and description. For external displays this is great behavior, however for laptops this may get a bit confusing. An example: My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's display. However, whenever a user wants to assign a profile to his laptop screen, it's not obvious this HP laptop needs a profile with Samsung in it's description. This may confuse people. So for laptop display _descriptions_ it might be a good idea to use the DMI Product Name instead of the panels EDID. pmjdebruijn at unicron:~$ sudo dmidecode | grep -i compaq Product Name: HP Compaq 6730s Please do note, I think we should keep using the panel's EDID for the ICC profile make/model tags, since this is technically correct, no matter if it's a laptop display or not. Only the description needs to be made user friendly. Regards, Pascal de Bruijn From hughsient at gmail.com Sun Nov 29 21:42:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 29 Nov 2009 21:42:33 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Message-ID: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's > display. ?However, whenever a user wants to assign a profile to his > laptop screen, it's not obvious this HP laptop needs a profile with > Samsung in it's description. This may confuse people. Agreed: commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de Author: Richard Hughes Date: Sun Nov 29 21:04:48 2009 +0000 Use DMI data to improve the device title and fill in missing model information :100644 100644 4504005... 0289dbd... M src/gcm-client.c commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 Author: Richard Hughes Date: Sun Nov 29 21:04:15 2009 +0000 Add a GcmDmi object to parse DMI data about the host machine :100644 100644 76796f2... c6b219b... M src/Makefile.am :000000 100644 0000000... ed48ea9... A src/gcm-dmi.c :000000 100644 0000000... 0a4897c... A src/gcm-dmi.h :100644 100644 0a4bbb4... 5624175... M src/gcm-self-test.c Can you verify the new functionality please. Thanks. Richard. From alexandre.prokoudine at gmail.com Sun Nov 29 23:38:27 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 02:38:27 +0300 Subject: hardware autodetection Message-ID: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Hi, What do I need to have installed in my system to get hardware auto-detection: yes after running ./configure ? I do see "checking for GUDEV... yes" in the output. Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:41:58 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:41:58 +0100 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> On Mon, Nov 30, 2009 at 12:38 AM, Alexandre Prokoudine wrote: > Hi, > > What do I need to have installed in my system to get > > hardware auto-detection: ? yes > > after running ./configure ? > > I do see "checking for GUDEV... yes" in the output. You need a new ArgyllCMS release with the new udev rules. ArgyllCMS 1.1.0-rc should do. My Debian package has the following Build-Depends: Build-Depends: debhelper (>= 7), autotools-dev, cdbs, dpatch, docbook-utils, gtk-doc-tools, gnome-doc-utils, libx11-dev, libxxf86vm-dev, libxrandr-dev, libglib2.0-dev, libgtk2.0-dev, libgnome-desktop-dev, libgconf2-dev, libunique-dev (>= 1.0), libvte-dev (>= 0.22), libgudev-1.0-dev, libdbus-glib-1-dev Then it should work. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sun Nov 29 23:46:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:46:02 +0100 Subject: auto hardware detection not working In-Reply-To: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> Message-ID: <4c2c37f90911291546n19ee7040j48af2ef424e74209@mail.gmail.com> On Sat, Nov 28, 2009 at 9:49 PM, Richard Hughes wrote: > 2009/11/28 Pascal de Bruijn : >> Is anybody willing to give me some pointers on how to debug this issue? > > Can you attach the output of gnome-color-manager --verbose as you plug > in and plug out the adaptor please? Thanks. I think I was mistaken, it seems to work now. My bad. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Mon Nov 30 01:14:10 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 04:14:10 +0300 Subject: hardware autodetection In-Reply-To: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> Message-ID: <733f2c730911291714l7536bba9n74c11bb3b000591a@mail.gmail.com> On 11/30/09, Pascal de Bruijn wrote: > You need a new ArgyllCMS release with the new udev rules. ArgyllCMS > 1.1.0-rc should do. Well, it's argyll-1.1.0-rc1-3pmjdebruijn0~karmic all the way here :) Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:27:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:27:59 +0100 Subject: Profile description for laptop displays In-Reply-To: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> Message-ID: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> On Sun, Nov 29, 2009 at 10:42 PM, Richard Hughes wrote: > 2009/11/29 Pascal de Bruijn : >> My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's >> display. ?However, whenever a user wants to assign a profile to his >> laptop screen, it's not obvious this HP laptop needs a profile with >> Samsung in it's description. This may confuse people. > > Agreed: > > commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de > commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 > > Can you verify the new functionality please. Thanks. That was fast as usual :) It works mostly... I've attached a screenshot. I noticed you included the product_version as well, at least on my laptop it's actually the BIOS revision, I'm not sure what this is on other laptops. It's probably not that relevant... I noticed you're currently filling the ICC Make with the username, it seems rather redundant with the copyright. Besides the point that the field wasn't ment to be used like that. I'd stick the EDID info there (even with laptops). For the Model field as well, EDID is most likely best and most accurate here. For example: Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, only lookup in the gcm-prefs GUI). Model: 154AT07-H01 Storing the EDID info as verbatim as possible in the ICC make/models fields, will make it easier to auto match displays and profiles in the future. Storing the EDID verbatim without looking up in pnp.ids prevents false data from conflicting lookups (like my Samsung/Seiko issue) from ending up in the profile itself. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-dmi.png Type: image/png Size: 44070 bytes Desc: not available URL: From hughsient at gmail.com Mon Nov 30 08:19:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 08:19:46 +0000 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <15e53e180911300019x1c1a7cfbu43741868d045dce4@mail.gmail.com> 2009/11/29 Alexandre Prokoudine : > What do I need to have installed in my system to get You need to configure with --enable-hardware-detection and to make sure you have the fixed Argyllcms udev rules file. Richard. From hughsient at gmail.com Mon Nov 30 10:10:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 10:10:34 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> Message-ID: <15e53e180911300210tae5b9a0kaa94ead83633e413@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > I noticed you included the product_version as well, at least on my > laptop it's actually the BIOS revision, I'm not sure what this is on > other laptops. It's probably not that relevant... Hmm, it seems the manufacturers were in a rush when they designed your laptop! The bios version, logically, belongs in bios_version :-) Could you attach the output of "cat /sys/class/dmi/id/*" and we'll try and work around bios issues like this. Thanks. > I noticed you're currently filling the ICC Make with the username, it > seems rather redundant with the copyright. Besides the point that the > field wasn't ment to be used like that. I'd stick the EDID info there > (even with laptops). For the Model field as well, EDID is most likely > best and most accurate here. I deliberately changed it, as the vendor is supposed to be the person or company that designed or created the profile. In this sense, it seemed wrong to say that the profile was created "by Lenovo" when it was created by me, for my Lenovo display. > For example: > > Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, > only lookup in the gcm-prefs GUI). > Model: 154AT07-H01 > > Storing the EDID info as verbatim as possible in the ICC make/models > fields, will make it easier to auto match displays and profiles in the > future. Hmm, I think the fields have to be displayable. We need to look at adding private fields if we want to add any machine parsable data into the ICC file. > Storing the EDID verbatim without looking up in pnp.ids prevents false > data from conflicting lookups (like my Samsung/Seiko issue) from > ending up in the profile itself. I think the lookup is valuable as it works most of the time. Your panel should have encoded SAM into the PNP field, not SEC, unless of course the panel really is a Seiko panel that's been rebadged as a Samsung. For what it's worth, my nice expensive LG panel is actually a generic Goldstar chipset with LG additions and plastic wrapping. Hence, it shows up as "Goldstar" as the vendor. :-( Richard. From pmjdebruijn at pcode.nl Tue Nov 10 18:35:36 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 10 Nov 2009 19:35:36 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: <1257878136.9870.4.camel@goliath> Hi, I have a HP Photosmart C6280 (all-in-one), which is connected via HP JetDirect (Ethernet). Currently it is not being detected by GNOME Color Manager, while I can print, and XSane does recognize the scanner... I'm assuming this is because currently only USB connected devices are checked? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From hughsient at gmail.com Tue Nov 10 18:42:39 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 18:42:39 +0000 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) In-Reply-To: <1257878136.9870.4.camel@goliath> References: <1257878136.9870.4.camel@goliath> Message-ID: <15e53e180911101042k5746e765i185677d1957e3198@mail.gmail.com> 2009/11/10 Pascal de Bruijn : > I have a HP Photosmart C6280 (all-in-one), which is connected via HP > JetDirect (Ethernet). > Currently it is not being detected by GNOME Color Manager, while I can > print, and XSane does recognize the scanner... > I'm assuming this is because currently only USB connected devices are > checked? Correct. How does xsane recognise the scanner? At the moment we're just checking USB printers that use hplip and scanners that are matched with libsane. If you can work out how to identify the device using a property in udev, then it's an easy add. I'm not sure how the ethernet printing and scanning stuff actually works right now. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 19:35:48 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 20:35:48 +0100 Subject: A small bug Message-ID: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> I'm stumbled over this when I interrupted a profile creation. My target profile name was the same as set before with gcm-prefs. I ended up with the entire gcm-prefs gui blocked. Se attached screenshoot. I have reproduced it and attached a log file. If I do a "head -c 100 /dev/random > i1.icc" where i1.icc is my gcm-prefs chosen profile I got this messages in log: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected **************************************************** With a large file like this: "head -c 500 /dev/random > i1.icc" I got: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-log.txt.zip Type: application/zip Size: 2093 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: corrupt.png Type: image/png Size: 20741 bytes Desc: not available URL: From hughsient at gmail.com Tue Nov 10 20:08:28 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 20:08:28 +0000 Subject: A small bug In-Reply-To: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> Message-ID: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> 2009/11/10 Lars Tore Gustavsen : > I have reproduced it and attached a log file. > If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my > gcm-prefs chosen profile I got this messages in log: Can you try with git now please. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 21:35:09 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 22:35:09 +0100 Subject: A small bug In-Reply-To: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> Message-ID: <58497f010911101335g317529bev8f1e48d780e3ab5d@mail.gmail.com> On Tue, Nov 10, 2009 at 9:08 PM, Richard Hughes wrote: > 2009/11/10 Lars Tore Gustavsen : >> I have reproduced it and attached a log file. >> If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my >> gcm-prefs chosen profile I got this messages in log: > > Can you try with git now please. Thanks. > > Richard. > It works very well, thank you. Lars Tore From lars.tore at mulebakken.net Wed Nov 11 11:51:06 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 12:51:06 +0100 Subject: Bluish.icc Message-ID: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> The icc profile include with gnome-color-manager is very nice to test if everything works. However it advertise itself as "sRGB IEC61966-2-1" I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: bluish.icc Type: application/octet-stream Size: 3962 bytes Desc: not available URL: From hughsient at gmail.com Wed Nov 11 11:59:55 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 11:59:55 +0000 Subject: Bluish.icc In-Reply-To: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> Message-ID: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> 2009/11/11 Lars Tore Gustavsen : > I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Committed, thanks. Richard. From fred at crozat.net Wed Nov 11 12:53:41 2009 From: fred at crozat.net (Frederic Crozat) Date: Wed, 11 Nov 2009 13:53:41 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> Message-ID: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> 2009/11/11 Richard Hughes : > 2009/11/11 Lars Tore Gustavsen : >> I have edited the attached profile and it now reads "bluish test" in gcm-prefs. > > Committed, thanks. In the same idea, it could be interesting to bundle a "test" jpg or png image in gnome-color-manager which would be only visible (or display correctly) when ICC profiles are correctly handled by applications. I use either http://1reflet.skynetblogs.be/post/6632777/profil-colorimetrique-utilisateur-firefox (sorry it is in french, flower is supposed to be displayed in yellow, not pink) or http://www.color.org/version4html.xalter I don't the license of those images are compatible with free software but creating similar images would be useful. WDYT ? -- Frederic Crozat From hughsient at gmail.com Wed Nov 11 13:12:09 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 13:12:09 +0000 Subject: Bluish.icc In-Reply-To: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> Message-ID: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> 2009/11/11 Frederic Crozat : > I don't the license of those images are compatible with free software > but creating similar images would be useful. > WDYT ? I think it's a good idea, although the licence would have to be CC_BY_SA or something like that to be allowed in gcm. Can anybody find suitably licensed example photographs? We also want the gamma checker images, but alas, these have to be free too. Richard. From anders at brander.dk Wed Nov 11 13:43:43 2009 From: anders at brander.dk (Anders Brander) Date: Wed, 11 Nov 2009 14:43:43 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> Message-ID: <1257947023.29790.3.camel@smutogtab> Hi, On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > 2009/11/11 Frederic Crozat : > > I don't the license of those images are compatible with free software > > but creating similar images would be useful. > > WDYT ? > > I think it's a good idea, although the licence would have to be > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > suitably licensed example photographs? We also want the gamma checker > images, but alas, these have to be free too. I'm not sure what is meant here. If we need an image to test whether an ICC profile is respected, one could create an image with swapped red/green channels - and then embed a ICC-profile undoing that. It would be obvious if the profile is respected or not when viewing the image. Well... /Anders Brander From hughsient at gmail.com Wed Nov 11 14:38:15 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 14:38:15 +0000 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> 2009/11/11 Anders Brander : > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. Yes, I think that would be a good idea for testing purposes. Richard. From lars.tore at mulebakken.net Wed Nov 11 16:58:23 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 17:58:23 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> Message-ID: <58497f010911110858x42131154p3217ff2015f60f45@mail.gmail.com> On Wed, Nov 11, 2009 at 3:38 PM, Richard Hughes wrote: > 2009/11/11 Anders Brander : >> I'm not sure what is meant here. If we need an image to test whether an >> ICC profile is respected, one could create an image with swapped >> red/green channels - and then embed a ICC-profile undoing that. It would >> be obvious if the profile is respected or not when viewing the image. > > Yes, I think that would be a good idea for testing purposes. > > Richard. I often play with "dispwin -V profilename" to check correct loading of the clut. So that's another idea. Lars Tore Gustavsen From pmjdebruijn at pcode.nl Wed Nov 11 17:26:04 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 11 Nov 2009 18:26:04 +0100 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <1257960364.6073.7.camel@goliath> On Wed, 2009-11-11 at 14:43 +0100, Anders Brander wrote: > Hi, > > On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > > 2009/11/11 Frederic Crozat : > > > I don't the license of those images are compatible with free software > > > but creating similar images would be useful. > > > WDYT ? > > > > I think it's a good idea, although the licence would have to be > > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > > suitably licensed example photographs? We also want the gamma checker > > images, but alas, these have to be free too. > > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. We can have two purposes for the image: 1. See if the profile is loaded properly at all 2. See if the profile is in the right ballpark (regarding accuracy) While the following image surely isn't CC licensed, something similar to this would be just perfect: http://www.smugmug.com/help/calibration-1400.mg -- http://blog.pcode.nl/ http://photos.pcode.nl/ From memolus at googlemail.com Thu Nov 12 19:56:09 2009 From: memolus at googlemail.com (memolus at googlemail.com) Date: Thu, 12 Nov 2009 20:56:09 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: 2009/11/10 Richard Hughes : > Correct. How does xsane recognise the scanner? At the moment we're > just checking USB printers that use hplip and scanners that are > matched with libsane. If you can work out how to identify the device > using a property in udev, then it's an easy add. I'm not sure how the > ethernet printing and scanning stuff actually works right now. Thanks. I don't know how deep you know the details about the network support of hplip, but here's what I know, as an introduction: The printer and the scanner is identified by an URI "hp:/net/Photosmart_C6200_series?ip=192.168.0.2" (fax has hpfax:/ instead of hp:/) in cups and sane ("Photosmart_C6200_series:Photosmart_C6200_series?ip=192.168.0.2") using the hplip driver, and treated as an local device. Normal network printers have URIs like "socket://printer:9100". It's detectable using Zeroconf (dnssd://photosmart c6200 series [d44b9e]._pdl-datastream._tcp.local/) and UPnP, cause HP supports Mac and Windows. Actually automatic detection of hp photosmart all-in-one devices in system-config-printer-gnome is broken, but automatic detection works using gnome-cups-manager und sane. From lars.tore at mulebakken.net Fri Nov 13 16:38:42 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Fri, 13 Nov 2009 17:38:42 +0100 Subject: Fighting with the screensaver. Message-ID: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> First I wonder if I'm the only person now who fights with the lut deletion with gnome-screensaver. It almost look like it is fixed, but I have still have this problem with ubuntu 9.10. https://bugzilla.gnome.org/show_bug.cgi?id=342850 Should I expect the color manager to take care of this on it own? Like running some kind of services? When I use dispwin from the argyll package I normally take care of this with a desktop file in the autostart folder with an exec line like this. Exec=/bin/bash -c ? gnome-screensaver-command ?exit; dispwin -L;gnome-screensaver? I recently tried gcm on an xubuntu (xface)box and it worked very well, but I guess the reason was it used xscreensaver instead of gnome-screensaver. From fred at crozat.net Fri Nov 13 16:46:36 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 17:46:36 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> 2009/11/13 Lars Tore Gustavsen : > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally ?take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > ?dispwin -L;gnome-screensaver? gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in it) needs to be fixed to correctly save LUT before fading gamma at screensaver startup and restore it when it quits. I haven't found time to investigate before 2.28 was released :( -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 16:50:16 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 16:50:16 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> Message-ID: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> 2009/11/13 Frederic Crozat : > gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in > it) needs to be fixed to correctly save LUT before fading gamma at > screensaver startup and restore it when it quits. Or, gnome-screensaver could just call gcm-apply which resets everything as well. Richard. From pmjdebruijn at pcode.nl Fri Nov 13 16:56:50 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 13 Nov 2009 17:56:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <4c2c37f90911130856m5fdcd776vbc8e9b84a934d011@mail.gmail.com> On Fri, Nov 13, 2009 at 5:50 PM, Richard Hughes wrote: > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. While these are all solutions, the short term workaround is simply to not use a screensaver, and only have display power saving enabled :) I know it's lame... but screensavers don't have any real function any more, or do they? Regards, Pascal de Bruijn From fred at crozat.net Fri Nov 13 21:05:10 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:05:10 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. That would imply a dependency on gcm, which is not a really good idea. I really think gnome-screensaver should restore LUT after the fading (after all, I also want the pictures used for slideshow in screensaver to be correctly color managed ;) -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 21:12:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 21:12:34 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> Message-ID: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> 2009/11/13 Frederic Crozat : > That would imply a dependency on gcm, which is not a really good idea. Sure, but the sort of dependency where it doesn't matter if gcm-apply doesn't exist... > I really think gnome-screensaver should restore LUT after the fading > (after all, I also want the pictures used for slideshow in screensaver > to be correctly color managed ;) That is true. Richard. From fred at crozat.net Fri Nov 13 21:25:59 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:25:59 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> Message-ID: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> That would imply a dependency on gcm, which is not a really good idea. > > Sure, but the sort of dependency where it doesn't matter if gcm-apply > doesn't exist... It does if people uses dispwin manually (or anything else to change LUT) ;) -- Frederic Crozat From amluto at gmail.com Fri Nov 13 21:56:42 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Fri, 13 Nov 2009 16:56:42 -0500 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> Message-ID: On Fri, Nov 13, 2009 at 4:25 PM, Frederic Crozat wrote: > 2009/11/13 Richard Hughes : >> 2009/11/13 Frederic Crozat : >>> That would imply a dependency on gcm, which is not a really good idea. >> >> Sure, but the sort of dependency where it doesn't matter if gcm-apply >> doesn't exist... > > It does if people uses dispwin manually (or anything else to change LUT) ;) ISTM that gnome-screensaver would ideally just not touch the LUT. These days we have compositing, or even just taking a screen shot and fading to black with RENDER, for that. --Andy > > -- > Frederic Crozat > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pmjdebruijn at pcode.nl Sat Nov 14 18:23:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 14 Nov 2009 19:23:51 +0100 Subject: Standby also seems to reset the VideoLUT/crtc Message-ID: <1258223031.9981.3.camel@goliath> Hi, Similarly as discussed in "Re: Fighting with the screensaver." it also seems putting your laptop to sleep (standby) seems to reset the VideoLUT/xrandr crtc's... Can anybody test and confirm this... I have a Intel X4500MHD graphics chip, however, if I'm not mistaken the driver card/driver actually doesn't have anything to do with this, with the vcgt tag is applied via Xorg/xrandr. Or am I wrong about this? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From compiz at sukimashita.com Sat Nov 14 19:19:20 2009 From: compiz at sukimashita.com (Martin S.) Date: Sat, 14 Nov 2009 20:19:20 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <1258226360.12545.10.camel@mirell> On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 This is somewhat old. I remember working on that bug myself as it was annoying for both gnome-screensaver and xscreensaver if I had profiles set. However, the issue was clearly fixed and I did't see this anymore on a range of systems since then (nvidia, intel mostly). > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > dispwin -L;gnome-screensaver? This is not the right solution afaik. Applications should not fiddle with the color profile settings unless they are created to do just that. If you are sure gnome-screensaver causes it please file a bug. gnome-screensaver must respect the LUT settings here (the code apparently does already...). As noted above, this works fine on a couple of systems I tested for 2.28. What gfx driver do you use and which component versions (xorg, driver, gnome-screensaver? --- Martin S. From amluto at gmail.com Sat Nov 14 19:54:41 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sat, 14 Nov 2009 14:54:41 -0500 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: On my system, whatever xorg-xserver version F11 used interacted badly with intel to cause all kinds of things to reset the LUTs. For example, resuming, switching VTs, and even starting glxgears or okular (!). This has been fixed upstream and in F12. --Andy On Sat, Nov 14, 2009 at 2:19 PM, Martin S. wrote: > On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: >> First I wonder if I'm the only person now who fights with the lut >> deletion with gnome-screensaver. >> It almost look like it is fixed, but I have still have this problem >> with ubuntu 9.10. >> https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > This is somewhat old. I remember working on that bug myself as it was > annoying for both gnome-screensaver and xscreensaver if I had profiles > set. > > However, the issue was clearly fixed and I did't see this anymore on a > range of systems since then (nvidia, intel mostly). > >> Should I expect the color manager to take care of this on it own? Like >> running some kind of services? >> When I use dispwin from the argyll package I normally ?take care of >> this with a desktop file in the autostart folder with an exec line >> like this. >> Exec=/bin/bash -c ? gnome-screensaver-command ?exit; >> ?dispwin -L;gnome-screensaver? > > This is not the right solution afaik. Applications should not fiddle > with the color profile settings unless they are created to do just that. > > If you are sure gnome-screensaver causes it please file a bug. > gnome-screensaver must respect the LUT settings here (the code > apparently does already...). > > As noted above, this works fine on a couple of systems I tested for > 2.28. > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > > --- Martin S. > > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list From compiz at sukimashita.com Sun Nov 15 02:04:29 2009 From: compiz at sukimashita.com (Martin S.) Date: Sun, 15 Nov 2009 03:04:29 +0100 Subject: [PATCH] Enable adding xrandr devices with no EDID Message-ID: <1258250669.25043.1.camel@mirell> Devices without EDID information or bad XRANDR implementations work again and get standard properties set. This restores functionality that existed before a recent change and allows me to assign color profiles on the broken nvidia xrandr implementation again. --- Martin S. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Enable-adding-xrandr-devices-with-no-EDID.patch Type: text/x-patch Size: 1874 bytes Desc: not available URL: From hughsient at gmail.com Sun Nov 15 15:03:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:03:32 +0000 Subject: [PATCH] Enable adding xrandr devices with no EDID In-Reply-To: <1258250669.25043.1.camel@mirell> References: <1258250669.25043.1.camel@mirell> Message-ID: <15e53e180911150703r28ba9e0dm9a1fbf760b2ab6ea@mail.gmail.com> 2009/11/15 Martin S. : > This restores functionality that existed before a recent change and > allows me to assign color profiles on the broken nvidia xrandr > implementation again. Applied, thanks. Richard. From hughsient at gmail.com Sun Nov 15 15:30:12 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:30:12 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <1258223031.9981.3.camel@goliath> References: <1258223031.9981.3.camel@goliath> Message-ID: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> 2009/11/14 Pascal de Bruijn : > Similarly as discussed in "Re: Fighting with the screensaver." it also > seems putting your laptop to sleep (standby) seems to reset the > VideoLUT/xrandr crtc's... Seems plausible, although I would argue we should probably just get X or the kernel to save the gamma tables on suspend and restore them on resume. It certainly seems a better idea then getting the session to do it. Richard. From amluto at gmail.com Sun Nov 15 15:33:14 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 10:33:14 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 10:30 AM, Richard Hughes wrote: > 2009/11/14 Pascal de Bruijn : >> Similarly as discussed in "Re: Fighting with the screensaver." it also >> seems putting your laptop to sleep (standby) seems to reset the >> VideoLUT/xrandr crtc's... > > Seems plausible, although I would argue we should probably just get X > or the kernel to save the gamma tables on suspend and restore them on > resume. It certainly seems a better idea then getting the session to > do it. Heh, I replied to Pascal directly instead of to all. I think that X already does that with server 1.7 and up and (on my machine, anyway) intel driver 2.9.0 and up. (e.g. F12 but not F11) --Andy > > Richard. > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pedro at pedrocr.net Sun Nov 15 19:15:24 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 11:15:24 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: > Heh, I replied to Pascal directly instead of to all. ?I think that X > already does that with server 1.7 and up and (on my machine, anyway) > intel driver 2.9.0 and up. ?(e.g. F12 but not F11) I run Ubuntu Karmic (9.10) and this is not the case. I do have the 2.9.0 intel driver but the server is only 1.6.4. So I guess the config for it is in the xserver. Strangely when I set the ICC profile with xcalib it seems to survive the suspend. Pedro From amluto at gmail.com Sun Nov 15 19:40:15 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 14:40:15 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 2:15 PM, Pedro C?rte-Real wrote: > On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: >> Heh, I replied to Pascal directly instead of to all. ?I think that X >> already does that with server 1.7 and up and (on my machine, anyway) >> intel driver 2.9.0 and up. ?(e.g. F12 but not F11) > > I run Ubuntu Karmic (9.10) and this is not the case. I do have the > 2.9.0 intel driver but the server is only 1.6.4. So I guess the config > for it is in the xserver. Strangely when I set the ICC profile with > xcalib it seems to survive the suspend. I believe it requires some cooperation between both. In the intel driver, in drmmode_set_mode_major, it says: #if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1,7,0,0,0) crtc->funcs->gamma_set(crtc, crtc->gamma_red, crtc->gamma_green, crtc->gamma_blue, crtc->gamma_size); #endif --Andy > > Pedro > From lars.tore at mulebakken.net Sun Nov 15 20:42:50 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Sun, 15 Nov 2009 21:42:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: <58497f010911151242u54a7926am8f1a9128da6dec42@mail.gmail.com> On Sat, Nov 14, 2009 at 8:19 PM, Martin S. wrote: > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > I use ubuntu 9.10 and I have a ATI Radeon 9200 PRO card. I use the radeon xorg driver and the xorg version is 1.7.4. Gnome-screensaver is 2.28.0 Lars Tore Gustavsen From pedro at pedrocr.net Sun Nov 15 23:53:38 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 15:53:38 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> First, thanks for this Richard. Gnome/Linux have been needing this kind of simple support for color in a long time. On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: > Strangely when I set the ICC profile with xcalib it seems to survive the suspend. xcalib is probably doing something very different as its calibration also applies to all displays. On the other hand this means that it both survives the suspend and is applied when the display is disconnected/connected, both things that g-c-m currently doesn't handle properly. The suspend/resume stuff should be handled by X but the connect/disconnect should probably be handled by g-c-m as that policy shouldn't be in X. Cheers, Pedro From hughsient at gmail.com Mon Nov 16 08:29:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 16 Nov 2009 08:29:32 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> Message-ID: <15e53e180911160029u572db018x7d459eaf624c5765@mail.gmail.com> 2009/11/15 Pedro C?rte-Real : > First, thanks for this Richard. Gnome/Linux have been needing this > kind of simple support for color in a long time. > > On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: >> Strangely when I set the ICC profile with xcalib it seems to survive the suspend. > > xcalib is probably doing something very different as its calibration > also applies to all displays. xcalib sets the per-screen gamma tables, and gcm sets the per-output gamma tables. Richard. From pmjdebruijn at pcode.nl Wed Nov 25 17:28:33 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:28:33 +0100 Subject: Regression: gnome-color-manager segfaults after dispcal Message-ID: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Hi, Using gnome-color-manager 2.29.1~git20091124 it seems to segfault after running dispcal. Can anybody confirm this? Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Wed Nov 25 17:30:03 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:30:03 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown Message-ID: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Hi, On my external display (HP LP2475w) connected via DVI to my Intel GMA, the precalibration "tips/guidelines" dialog isn't shown anymore. Has this been disabled on purpose, or is this an accidental regression? Regards, Pascal de Bruijn From hughsient at gmail.com Wed Nov 25 17:40:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:40:57 +0000 Subject: Regression: gnome-color-manager segfaults after dispcal In-Reply-To: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> References: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Message-ID: <15e53e180911250940l2187d4e7s9755ed15edc867eb@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Using gnome-color-manager 2.29.1~git20091124 it seems to segfault > after running dispcal. You got a backtrace please? Thanks. Richard. From hughsient at gmail.com Wed Nov 25 17:48:20 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:48:20 +0000 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Message-ID: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Has this been disabled on purpose, or is this an accidental regression? The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 18:09:48 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:09:48 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore Message-ID: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Hi, It seems that gcm-prefs from current git does not apply the VideoLUT/vcgt tag anymore... gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 18:14:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:14:51 +0100 Subject: gcm-prefs: New profiles not showing up in the list Message-ID: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Hi, When display calibration finishes, the newly created profile does not show up in the list in gcm-prefs. Restarting gcm-prefs helps, then I _do_ see the new profile. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:24:32 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:24:32 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore In-Reply-To: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> References: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Message-ID: <4c2c37f90911261224h24d5eb10u1cb767adde26787a@mail.gmail.com> On Thu, Nov 26, 2009 at 7:09 PM, Pascal de Bruijn wrote: > Hi, > > It seems that gcm-prefs from current git does not apply the > VideoLUT/vcgt tag anymore... > > gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Changing the profile in gcm-prefs, closing gcm-prefs, and opening gcm-prefs again also does _not_ change the profile that is selected by default. So the problem is most likely not the application of another profile's VideoLUT, but the VideoLUT of the original default selected profile is always being applied, no matter which profile was manually selected afterward. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:54:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:54:28 +0100 Subject: Patch: Debian binary detection fix Message-ID: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Hi, I noticed the following recent commit to detect the Debinized Argyll binaries: http://git.gnome.org/cgit/gnome-color-manager/commit/?id=3b06571386be55a7b21424c256b88b2fb2ec6347 Conceptually the commit is fine, it's particularly great, this detect method is used for all of Argyll's utilities. Practically this is only applicable for targen at the moment. But since it's used for all binaries, gcm is automatically future proofed against other binaries getting renamed as well. Excellent behaviour. However, the detection is backwards. Please allow me to explain. Debian maintainers don't rename binaries just because they get a kick out of arbitrarily renaming random binaries. Debian has problems with conflicting binaries because their package repository is so big (almost 30,000 packages). This means they are forced to rename binaries in all but one package with conflicting binaries. This implies, on systems with a 'argyll-targen' binary, a 'targen' binary could be installed as well. But if a 'targen' binary is installed as well, it's most likely completely unrelated to Argyll, and will almost certainly fail when called by gcm. Therefore the detect should _first_ detect if the Debian renamed binaries exist, and if not, fallback to the original binary names. I've attached a small patch, which should "fix" the issue described above. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-debian-fix.patch Type: text/x-patch Size: 1022 bytes Desc: not available URL: From hughsient at gmail.com Thu Nov 26 21:07:11 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:07:11 +0000 Subject: Patch: Debian binary detection fix In-Reply-To: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> References: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Message-ID: <15e53e180911261307l6b8b4427g13bc6de54b014f00@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Therefore the detect should _first_ detect if the Debian renamed > binaries exist, and if not, fallback to the original binary names. Agreed. I've attached the patch I've committed. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: look-for-debian-first.patch Type: text/x-patch Size: 1063 bytes Desc: not available URL: From alexandre.prokoudine at gmail.com Thu Nov 26 21:18:51 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 00:18:51 +0300 Subject: shifted dialog Message-ID: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Hi, The dialog that suggests to plug-in a measurement device somewhat unexpectedly pops up close to the left border of the screen, which is quite unfortunate for a 24" display :) Alexandre From hughsient at gmail.com Thu Nov 26 21:18:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:18:57 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Message-ID: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > When display calibration finishes, the newly created profile does not > show up in the list in gcm-prefs. Can you try now please. Thanks, Richard. From hughsient at gmail.com Thu Nov 26 21:22:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:22:33 +0000 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> 2009/11/26 Alexandre Prokoudine : > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Sure, I've shifted manually as by default it goes into the middle of the screen (as the calibration square is in the center) -- better ideas welcome. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 21:24:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:24:02 +0100 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <4c2c37f90911261324i570a102dsac872665b9e426fb@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Alexandre Prokoudine wrote: > Hi, > > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Why is this a problem? If this dialog would be displayed centered, it would end up under the actual calibration window. So this is a good thing... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 21:51:24 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:51:24 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> Message-ID: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> When display calibration finishes, the newly created profile does not >> show up in the list in gcm-prefs. > > Can you try now please. You "fixed" it, and "broke" it at the same time... Now, after generating a new profile, "None" gets selected, but "None" does actually display copyright/vendor information, and seems to load the VideoLUT associates with the new profile. So this is most likely a UI issue. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 22:04:31 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 23:04:31 +0100 Subject: Possible Regression: vendor/device metadata unknown Message-ID: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Hi, The profile I generated for my laptop a while back with an older checkout of gcm, seemed to semi-correctly detect vendor/device descriptions (154AT07-H01/154AT07-H01). When looking this up in my xorg.0.log, this should be: (WW) intel(0): Unknown vendor-specific block f (II) intel(0): SAMSUNG (II) intel(0): 154AT07-H01 However, a current git checkout produces this: ASCII data, length 21 chars: 0x0000: unknown manufacturer ASCII data, length 14 chars: 0x0000: unknown model If you require more information, please let me know. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Thu Nov 26 22:44:15 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 01:44:15 +0300 Subject: shifted dialog In-Reply-To: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> Message-ID: <733f2c730911261444v5ccee119j1b8fd0d3f899ec76@mail.gmail.com> On 11/27/09, Richard Hughes wrote: > Sure, I've shifted manually as by default it goes into the middle of > the screen (as the calibration square is in the center) -- better > ideas welcome. Ah, makes sense then. Sorry for the trouble. Alexandre From hughsient at gmail.com Fri Nov 27 11:13:01 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:13:01 +0000 Subject: Possible Regression: vendor/device metadata unknown In-Reply-To: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> References: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Message-ID: <15e53e180911270313q7a4e4ee9vce5dded99384a341@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > ?ASCII data, length 21 chars: > ? ?0x0000: unknown manufacturer > ?ASCII data, length 14 chars: > ? ?0x0000: unknown model > > If you require more information, please let me know. Can you pull git please, compile, and then run "./gcm-dump-edid" and then reply with the generated *.bin files attached. The complete log files for gcm-prefs would also be helpful. Thanks. Richard. From hughsient at gmail.com Fri Nov 27 11:35:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:35:46 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> Message-ID: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Now, after generating a new profile, "None" gets selected, but "None" > does actually display copyright/vendor information, and seems to load > the VideoLUT associates with the new profile. So this is most likely a > UI issue. Right, can you try one more time please. Thanks, Richard. From pmjdebruijn at pcode.nl Fri Nov 27 17:32:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 27 Nov 2009 18:32:59 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> Message-ID: <4c2c37f90911270932x1155c1c8k2525e5245c2856cf@mail.gmail.com> On Fri, Nov 27, 2009 at 12:35 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> Now, after generating a new profile, "None" gets selected, but "None" >> does actually display copyright/vendor information, and seems to load >> the VideoLUT associates with the new profile. So this is most likely a >> UI issue. > > Right, can you try one more time please. Thanks, Jep, that seems fixed as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:11:17 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:11:17 +0100 Subject: Bug: Recalibrating a display twice makes a single profile show up twice Message-ID: <4c2c37f90911280511v62082445i88480e326510c14b@mail.gmail.com> Hi, I think I found a small bug, when recalibrating a display twice (without restarting gcm-prefs), only a single ~/.color/icc/mydisplay.icc is generated however (actually two files are generated obviously, but the first is just overwritten by the second), it is added twice to the profile combobox in gcm-prefs. To reproduce: 1. Start gcm-prefs 2. Calibrate 3. Calibrate (again) 4. Now you'll notice the single ICC profile is listed twice in the combobox. The bigger question is what behavior do we want? 1. The slightly older profile is overwritten, and only the newer profile is displayed (once) in the gcm-prefs combo box. This makes a calibration history impossible. 2. Each calibration run, suffixes the profile filename (currently based on the serial???) with date and time (important, since we other can only calibrate once a day, without overwrites) to prevent older ones from getting overwritten. This automatically makes the current behavior of gcm-prefs correct by adding a new profile to the combobox. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:16:08 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:16:08 +0100 Subject: Profile Filenames Message-ID: <4c2c37f90911280516o40d616f6pb2a4dcae0594afb4@mail.gmail.com> Hi, I noticed gcm(-prefs) currently places newly generated profiles as: ~/.color/icc/serial.icc As I already indicated I think it would be wise to at least include date and time in the filename. I'd prefer something more human readable over the serial as well: ~/.color/icc/gcm_acer-al2016w_200911281415.icc As you'll noticed above, I think it's a good idea to also prefix gcm-prefs generated profiles with gcm, to clearly distinguish between profiles generated by gcm-prefs, and profiles gotten elsewhere (possibly from the vendor CD). I'd love to hear your thoughts on this. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:30:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:30:28 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> Message-ID: <4c2c37f90911280530i63ed52a9w989833570c5146df@mail.gmail.com> On Wed, Nov 25, 2009 at 6:48 PM, Richard Hughes wrote: > 2009/11/25 Pascal de Bruijn : >> Has this been disabled on purpose, or is this an accidental regression? > > The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Sorry, it took me a while to verify, but on my external display I can indeed confirm this has been fixed. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 17:43:55 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 18:43:55 +0100 Subject: auto hardware detection not working Message-ID: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Hi, I enabled hardware detection in my builds of GNOME Color Manager. However it's not working, the "Calibrate" button is enabled, no matter if a colorimeter is attached or not. Assuming gcm-prefs isn't the problem, I'm guessing this would be a udev issue? Or better a udev rules issue? Is anybody willing to give me some pointers on how to debug this issue? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Nov 28 20:49:26 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 28 Nov 2009 20:49:26 +0000 Subject: auto hardware detection not working In-Reply-To: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Message-ID: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> 2009/11/28 Pascal de Bruijn : > Is anybody willing to give me some pointers on how to debug this issue? Can you attach the output of gnome-color-manager --verbose as you plug in and plug out the adaptor please? Thanks. Richard. From pmjdebruijn at pcode.nl Sun Nov 29 12:53:39 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sun, 29 Nov 2009 13:53:39 +0100 Subject: Profile description for laptop displays Message-ID: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Hi, Currently GCM is using EDID to determine make and models for displays. This information is then usually incorporated into the profile make/model and description. For external displays this is great behavior, however for laptops this may get a bit confusing. An example: My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's display. However, whenever a user wants to assign a profile to his laptop screen, it's not obvious this HP laptop needs a profile with Samsung in it's description. This may confuse people. So for laptop display _descriptions_ it might be a good idea to use the DMI Product Name instead of the panels EDID. pmjdebruijn at unicron:~$ sudo dmidecode | grep -i compaq Product Name: HP Compaq 6730s Please do note, I think we should keep using the panel's EDID for the ICC profile make/model tags, since this is technically correct, no matter if it's a laptop display or not. Only the description needs to be made user friendly. Regards, Pascal de Bruijn From hughsient at gmail.com Sun Nov 29 21:42:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 29 Nov 2009 21:42:33 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Message-ID: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's > display. ?However, whenever a user wants to assign a profile to his > laptop screen, it's not obvious this HP laptop needs a profile with > Samsung in it's description. This may confuse people. Agreed: commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de Author: Richard Hughes Date: Sun Nov 29 21:04:48 2009 +0000 Use DMI data to improve the device title and fill in missing model information :100644 100644 4504005... 0289dbd... M src/gcm-client.c commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 Author: Richard Hughes Date: Sun Nov 29 21:04:15 2009 +0000 Add a GcmDmi object to parse DMI data about the host machine :100644 100644 76796f2... c6b219b... M src/Makefile.am :000000 100644 0000000... ed48ea9... A src/gcm-dmi.c :000000 100644 0000000... 0a4897c... A src/gcm-dmi.h :100644 100644 0a4bbb4... 5624175... M src/gcm-self-test.c Can you verify the new functionality please. Thanks. Richard. From alexandre.prokoudine at gmail.com Sun Nov 29 23:38:27 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 02:38:27 +0300 Subject: hardware autodetection Message-ID: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Hi, What do I need to have installed in my system to get hardware auto-detection: yes after running ./configure ? I do see "checking for GUDEV... yes" in the output. Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:41:58 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:41:58 +0100 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> On Mon, Nov 30, 2009 at 12:38 AM, Alexandre Prokoudine wrote: > Hi, > > What do I need to have installed in my system to get > > hardware auto-detection: ? yes > > after running ./configure ? > > I do see "checking for GUDEV... yes" in the output. You need a new ArgyllCMS release with the new udev rules. ArgyllCMS 1.1.0-rc should do. My Debian package has the following Build-Depends: Build-Depends: debhelper (>= 7), autotools-dev, cdbs, dpatch, docbook-utils, gtk-doc-tools, gnome-doc-utils, libx11-dev, libxxf86vm-dev, libxrandr-dev, libglib2.0-dev, libgtk2.0-dev, libgnome-desktop-dev, libgconf2-dev, libunique-dev (>= 1.0), libvte-dev (>= 0.22), libgudev-1.0-dev, libdbus-glib-1-dev Then it should work. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sun Nov 29 23:46:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:46:02 +0100 Subject: auto hardware detection not working In-Reply-To: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> Message-ID: <4c2c37f90911291546n19ee7040j48af2ef424e74209@mail.gmail.com> On Sat, Nov 28, 2009 at 9:49 PM, Richard Hughes wrote: > 2009/11/28 Pascal de Bruijn : >> Is anybody willing to give me some pointers on how to debug this issue? > > Can you attach the output of gnome-color-manager --verbose as you plug > in and plug out the adaptor please? Thanks. I think I was mistaken, it seems to work now. My bad. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Mon Nov 30 01:14:10 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 04:14:10 +0300 Subject: hardware autodetection In-Reply-To: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> Message-ID: <733f2c730911291714l7536bba9n74c11bb3b000591a@mail.gmail.com> On 11/30/09, Pascal de Bruijn wrote: > You need a new ArgyllCMS release with the new udev rules. ArgyllCMS > 1.1.0-rc should do. Well, it's argyll-1.1.0-rc1-3pmjdebruijn0~karmic all the way here :) Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:27:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:27:59 +0100 Subject: Profile description for laptop displays In-Reply-To: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> Message-ID: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> On Sun, Nov 29, 2009 at 10:42 PM, Richard Hughes wrote: > 2009/11/29 Pascal de Bruijn : >> My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's >> display. ?However, whenever a user wants to assign a profile to his >> laptop screen, it's not obvious this HP laptop needs a profile with >> Samsung in it's description. This may confuse people. > > Agreed: > > commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de > commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 > > Can you verify the new functionality please. Thanks. That was fast as usual :) It works mostly... I've attached a screenshot. I noticed you included the product_version as well, at least on my laptop it's actually the BIOS revision, I'm not sure what this is on other laptops. It's probably not that relevant... I noticed you're currently filling the ICC Make with the username, it seems rather redundant with the copyright. Besides the point that the field wasn't ment to be used like that. I'd stick the EDID info there (even with laptops). For the Model field as well, EDID is most likely best and most accurate here. For example: Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, only lookup in the gcm-prefs GUI). Model: 154AT07-H01 Storing the EDID info as verbatim as possible in the ICC make/models fields, will make it easier to auto match displays and profiles in the future. Storing the EDID verbatim without looking up in pnp.ids prevents false data from conflicting lookups (like my Samsung/Seiko issue) from ending up in the profile itself. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-dmi.png Type: image/png Size: 44070 bytes Desc: not available URL: From hughsient at gmail.com Mon Nov 30 08:19:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 08:19:46 +0000 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <15e53e180911300019x1c1a7cfbu43741868d045dce4@mail.gmail.com> 2009/11/29 Alexandre Prokoudine : > What do I need to have installed in my system to get You need to configure with --enable-hardware-detection and to make sure you have the fixed Argyllcms udev rules file. Richard. From hughsient at gmail.com Mon Nov 30 10:10:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 10:10:34 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> Message-ID: <15e53e180911300210tae5b9a0kaa94ead83633e413@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > I noticed you included the product_version as well, at least on my > laptop it's actually the BIOS revision, I'm not sure what this is on > other laptops. It's probably not that relevant... Hmm, it seems the manufacturers were in a rush when they designed your laptop! The bios version, logically, belongs in bios_version :-) Could you attach the output of "cat /sys/class/dmi/id/*" and we'll try and work around bios issues like this. Thanks. > I noticed you're currently filling the ICC Make with the username, it > seems rather redundant with the copyright. Besides the point that the > field wasn't ment to be used like that. I'd stick the EDID info there > (even with laptops). For the Model field as well, EDID is most likely > best and most accurate here. I deliberately changed it, as the vendor is supposed to be the person or company that designed or created the profile. In this sense, it seemed wrong to say that the profile was created "by Lenovo" when it was created by me, for my Lenovo display. > For example: > > Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, > only lookup in the gcm-prefs GUI). > Model: 154AT07-H01 > > Storing the EDID info as verbatim as possible in the ICC make/models > fields, will make it easier to auto match displays and profiles in the > future. Hmm, I think the fields have to be displayable. We need to look at adding private fields if we want to add any machine parsable data into the ICC file. > Storing the EDID verbatim without looking up in pnp.ids prevents false > data from conflicting lookups (like my Samsung/Seiko issue) from > ending up in the profile itself. I think the lookup is valuable as it works most of the time. Your panel should have encoded SAM into the PNP field, not SEC, unless of course the panel really is a Seiko panel that's been rebadged as a Samsung. For what it's worth, my nice expensive LG panel is actually a generic Goldstar chipset with LG additions and plastic wrapping. Hence, it shows up as "Goldstar" as the vendor. :-( Richard. From pmjdebruijn at pcode.nl Tue Nov 10 18:35:36 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 10 Nov 2009 19:35:36 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: <1257878136.9870.4.camel@goliath> Hi, I have a HP Photosmart C6280 (all-in-one), which is connected via HP JetDirect (Ethernet). Currently it is not being detected by GNOME Color Manager, while I can print, and XSane does recognize the scanner... I'm assuming this is because currently only USB connected devices are checked? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From hughsient at gmail.com Tue Nov 10 18:42:39 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 18:42:39 +0000 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) In-Reply-To: <1257878136.9870.4.camel@goliath> References: <1257878136.9870.4.camel@goliath> Message-ID: <15e53e180911101042k5746e765i185677d1957e3198@mail.gmail.com> 2009/11/10 Pascal de Bruijn : > I have a HP Photosmart C6280 (all-in-one), which is connected via HP > JetDirect (Ethernet). > Currently it is not being detected by GNOME Color Manager, while I can > print, and XSane does recognize the scanner... > I'm assuming this is because currently only USB connected devices are > checked? Correct. How does xsane recognise the scanner? At the moment we're just checking USB printers that use hplip and scanners that are matched with libsane. If you can work out how to identify the device using a property in udev, then it's an easy add. I'm not sure how the ethernet printing and scanning stuff actually works right now. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 19:35:48 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 20:35:48 +0100 Subject: A small bug Message-ID: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> I'm stumbled over this when I interrupted a profile creation. My target profile name was the same as set before with gcm-prefs. I ended up with the entire gcm-prefs gui blocked. Se attached screenshoot. I have reproduced it and attached a log file. If I do a "head -c 100 /dev/random > i1.icc" where i1.icc is my gcm-prefs chosen profile I got this messages in log: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:18:01 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:18:01 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: profile was not valid (file size too small) TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:18:01 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected **************************************************** With a large file like this: "head -c 500 /dev/random > i1.icc" I got: - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-prefs.c FN:gcm_prefs_add_profiles,885 - failed to add profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,131 - PNPID: SAM TI:20:25:40 FI:gcm-edid.c FN:gcm_edid_parse,149 - gamma is reported as 2,200000 TI:20:25:40 FI:gcm-profile.c FN:gcm_profile_parse,678 - loading '/home/ltg/.color/icc/i1.icc' *** WARNING *** TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,532 - failed to load: failed to load from config: failed to set from profile: not an ICC profile, signature is ' ?? ', expecting 'acsp' TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_dvi_0 is not connected TI:20:25:40 FI:gcm-client.c FN:gcm_client_xrandr_add,506 - xrandr_s_video is not connected Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-log.txt.zip Type: application/zip Size: 2093 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: corrupt.png Type: image/png Size: 20741 bytes Desc: not available URL: From hughsient at gmail.com Tue Nov 10 20:08:28 2009 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 10 Nov 2009 20:08:28 +0000 Subject: A small bug In-Reply-To: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> Message-ID: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> 2009/11/10 Lars Tore Gustavsen : > I have reproduced it and attached a log file. > If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my > gcm-prefs chosen profile I got this messages in log: Can you try with git now please. Thanks. Richard. From lars.tore at mulebakken.net Tue Nov 10 21:35:09 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Tue, 10 Nov 2009 22:35:09 +0100 Subject: A small bug In-Reply-To: <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> References: <58497f010911101135o47a1fc6dje73ce0277f9be91d@mail.gmail.com> <15e53e180911101208o23c83c8co7f43784d239b30ad@mail.gmail.com> Message-ID: <58497f010911101335g317529bev8f1e48d780e3ab5d@mail.gmail.com> On Tue, Nov 10, 2009 at 9:08 PM, Richard Hughes wrote: > 2009/11/10 Lars Tore Gustavsen : >> I have reproduced it and attached a log file. >> If I do a "head -c 100 /dev/random ? > i1.icc" ?where i1.icc is my >> gcm-prefs chosen profile I got this messages in log: > > Can you try with git now please. Thanks. > > Richard. > It works very well, thank you. Lars Tore From lars.tore at mulebakken.net Wed Nov 11 11:51:06 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 12:51:06 +0100 Subject: Bluish.icc Message-ID: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> The icc profile include with gnome-color-manager is very nice to test if everything works. However it advertise itself as "sRGB IEC61966-2-1" I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Regards Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: bluish.icc Type: application/octet-stream Size: 3962 bytes Desc: not available URL: From hughsient at gmail.com Wed Nov 11 11:59:55 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 11:59:55 +0000 Subject: Bluish.icc In-Reply-To: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> Message-ID: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> 2009/11/11 Lars Tore Gustavsen : > I have edited the attached profile and it now reads "bluish test" in gcm-prefs. Committed, thanks. Richard. From fred at crozat.net Wed Nov 11 12:53:41 2009 From: fred at crozat.net (Frederic Crozat) Date: Wed, 11 Nov 2009 13:53:41 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> Message-ID: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> 2009/11/11 Richard Hughes : > 2009/11/11 Lars Tore Gustavsen : >> I have edited the attached profile and it now reads "bluish test" in gcm-prefs. > > Committed, thanks. In the same idea, it could be interesting to bundle a "test" jpg or png image in gnome-color-manager which would be only visible (or display correctly) when ICC profiles are correctly handled by applications. I use either http://1reflet.skynetblogs.be/post/6632777/profil-colorimetrique-utilisateur-firefox (sorry it is in french, flower is supposed to be displayed in yellow, not pink) or http://www.color.org/version4html.xalter I don't the license of those images are compatible with free software but creating similar images would be useful. WDYT ? -- Frederic Crozat From hughsient at gmail.com Wed Nov 11 13:12:09 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 13:12:09 +0000 Subject: Bluish.icc In-Reply-To: <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> Message-ID: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> 2009/11/11 Frederic Crozat : > I don't the license of those images are compatible with free software > but creating similar images would be useful. > WDYT ? I think it's a good idea, although the licence would have to be CC_BY_SA or something like that to be allowed in gcm. Can anybody find suitably licensed example photographs? We also want the gamma checker images, but alas, these have to be free too. Richard. From anders at brander.dk Wed Nov 11 13:43:43 2009 From: anders at brander.dk (Anders Brander) Date: Wed, 11 Nov 2009 14:43:43 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> Message-ID: <1257947023.29790.3.camel@smutogtab> Hi, On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > 2009/11/11 Frederic Crozat : > > I don't the license of those images are compatible with free software > > but creating similar images would be useful. > > WDYT ? > > I think it's a good idea, although the licence would have to be > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > suitably licensed example photographs? We also want the gamma checker > images, but alas, these have to be free too. I'm not sure what is meant here. If we need an image to test whether an ICC profile is respected, one could create an image with swapped red/green channels - and then embed a ICC-profile undoing that. It would be obvious if the profile is respected or not when viewing the image. Well... /Anders Brander From hughsient at gmail.com Wed Nov 11 14:38:15 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 11 Nov 2009 14:38:15 +0000 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> 2009/11/11 Anders Brander : > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. Yes, I think that would be a good idea for testing purposes. Richard. From lars.tore at mulebakken.net Wed Nov 11 16:58:23 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 11 Nov 2009 17:58:23 +0100 Subject: Bluish.icc In-Reply-To: <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> <15e53e180911110638l47ed6he8c23214ac77af7f@mail.gmail.com> Message-ID: <58497f010911110858x42131154p3217ff2015f60f45@mail.gmail.com> On Wed, Nov 11, 2009 at 3:38 PM, Richard Hughes wrote: > 2009/11/11 Anders Brander : >> I'm not sure what is meant here. If we need an image to test whether an >> ICC profile is respected, one could create an image with swapped >> red/green channels - and then embed a ICC-profile undoing that. It would >> be obvious if the profile is respected or not when viewing the image. > > Yes, I think that would be a good idea for testing purposes. > > Richard. I often play with "dispwin -V profilename" to check correct loading of the clut. So that's another idea. Lars Tore Gustavsen From pmjdebruijn at pcode.nl Wed Nov 11 17:26:04 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 11 Nov 2009 18:26:04 +0100 Subject: Bluish.icc In-Reply-To: <1257947023.29790.3.camel@smutogtab> References: <58497f010911110351o3d7df74dt8ac35ef7c8cb5e4@mail.gmail.com> <15e53e180911110359j1de0eb47od68011e36b19bea9@mail.gmail.com> <21ad25710911110453p382c60d7sdce5cabe749ac5b5@mail.gmail.com> <15e53e180911110512o577b33c6m3dd01b76cb4fc0b0@mail.gmail.com> <1257947023.29790.3.camel@smutogtab> Message-ID: <1257960364.6073.7.camel@goliath> On Wed, 2009-11-11 at 14:43 +0100, Anders Brander wrote: > Hi, > > On Wed, 2009-11-11 at 13:12 +0000, Richard Hughes wrote: > > 2009/11/11 Frederic Crozat : > > > I don't the license of those images are compatible with free software > > > but creating similar images would be useful. > > > WDYT ? > > > > I think it's a good idea, although the licence would have to be > > CC_BY_SA or something like that to be allowed in gcm. Can anybody find > > suitably licensed example photographs? We also want the gamma checker > > images, but alas, these have to be free too. > > I'm not sure what is meant here. If we need an image to test whether an > ICC profile is respected, one could create an image with swapped > red/green channels - and then embed a ICC-profile undoing that. It would > be obvious if the profile is respected or not when viewing the image. We can have two purposes for the image: 1. See if the profile is loaded properly at all 2. See if the profile is in the right ballpark (regarding accuracy) While the following image surely isn't CC licensed, something similar to this would be just perfect: http://www.smugmug.com/help/calibration-1400.mg -- http://blog.pcode.nl/ http://photos.pcode.nl/ From memolus at googlemail.com Thu Nov 12 19:56:09 2009 From: memolus at googlemail.com (memolus at googlemail.com) Date: Thu, 12 Nov 2009 20:56:09 +0100 Subject: HP Printer/Scanner All-in-one not recognized via JetDirect (ethernet) Message-ID: 2009/11/10 Richard Hughes : > Correct. How does xsane recognise the scanner? At the moment we're > just checking USB printers that use hplip and scanners that are > matched with libsane. If you can work out how to identify the device > using a property in udev, then it's an easy add. I'm not sure how the > ethernet printing and scanning stuff actually works right now. Thanks. I don't know how deep you know the details about the network support of hplip, but here's what I know, as an introduction: The printer and the scanner is identified by an URI "hp:/net/Photosmart_C6200_series?ip=192.168.0.2" (fax has hpfax:/ instead of hp:/) in cups and sane ("Photosmart_C6200_series:Photosmart_C6200_series?ip=192.168.0.2") using the hplip driver, and treated as an local device. Normal network printers have URIs like "socket://printer:9100". It's detectable using Zeroconf (dnssd://photosmart c6200 series [d44b9e]._pdl-datastream._tcp.local/) and UPnP, cause HP supports Mac and Windows. Actually automatic detection of hp photosmart all-in-one devices in system-config-printer-gnome is broken, but automatic detection works using gnome-cups-manager und sane. From lars.tore at mulebakken.net Fri Nov 13 16:38:42 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Fri, 13 Nov 2009 17:38:42 +0100 Subject: Fighting with the screensaver. Message-ID: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> First I wonder if I'm the only person now who fights with the lut deletion with gnome-screensaver. It almost look like it is fixed, but I have still have this problem with ubuntu 9.10. https://bugzilla.gnome.org/show_bug.cgi?id=342850 Should I expect the color manager to take care of this on it own? Like running some kind of services? When I use dispwin from the argyll package I normally take care of this with a desktop file in the autostart folder with an exec line like this. Exec=/bin/bash -c ? gnome-screensaver-command ?exit; dispwin -L;gnome-screensaver? I recently tried gcm on an xubuntu (xface)box and it worked very well, but I guess the reason was it used xscreensaver instead of gnome-screensaver. From fred at crozat.net Fri Nov 13 16:46:36 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 17:46:36 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> 2009/11/13 Lars Tore Gustavsen : > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally ?take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > ?dispwin -L;gnome-screensaver? gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in it) needs to be fixed to correctly save LUT before fading gamma at screensaver startup and restore it when it quits. I haven't found time to investigate before 2.28 was released :( -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 16:50:16 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 16:50:16 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> Message-ID: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> 2009/11/13 Frederic Crozat : > gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in > it) needs to be fixed to correctly save LUT before fading gamma at > screensaver startup and restore it when it quits. Or, gnome-screensaver could just call gcm-apply which resets everything as well. Richard. From pmjdebruijn at pcode.nl Fri Nov 13 16:56:50 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 13 Nov 2009 17:56:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <4c2c37f90911130856m5fdcd776vbc8e9b84a934d011@mail.gmail.com> On Fri, Nov 13, 2009 at 5:50 PM, Richard Hughes wrote: > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. While these are all solutions, the short term workaround is simply to not use a screensaver, and only have display power saving enabled :) I know it's lame... but screensavers don't have any real function any more, or do they? Regards, Pascal de Bruijn From fred at crozat.net Fri Nov 13 21:05:10 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:05:10 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> Message-ID: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> gnome-screensaver (or now gnome-desktop if xrandr gamma part landed in >> it) needs to be fixed to correctly save LUT before fading gamma at >> screensaver startup and restore it when it quits. > > Or, gnome-screensaver could just call gcm-apply which resets everything as well. That would imply a dependency on gcm, which is not a really good idea. I really think gnome-screensaver should restore LUT after the fading (after all, I also want the pictures used for slideshow in screensaver to be correctly color managed ;) -- Frederic Crozat From hughsient at gmail.com Fri Nov 13 21:12:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 13 Nov 2009 21:12:34 +0000 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> Message-ID: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> 2009/11/13 Frederic Crozat : > That would imply a dependency on gcm, which is not a really good idea. Sure, but the sort of dependency where it doesn't matter if gcm-apply doesn't exist... > I really think gnome-screensaver should restore LUT after the fading > (after all, I also want the pictures used for slideshow in screensaver > to be correctly color managed ;) That is true. Richard. From fred at crozat.net Fri Nov 13 21:25:59 2009 From: fred at crozat.net (Frederic Crozat) Date: Fri, 13 Nov 2009 22:25:59 +0100 Subject: Fighting with the screensaver. In-Reply-To: <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> Message-ID: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> 2009/11/13 Richard Hughes : > 2009/11/13 Frederic Crozat : >> That would imply a dependency on gcm, which is not a really good idea. > > Sure, but the sort of dependency where it doesn't matter if gcm-apply > doesn't exist... It does if people uses dispwin manually (or anything else to change LUT) ;) -- Frederic Crozat From amluto at gmail.com Fri Nov 13 21:56:42 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Fri, 13 Nov 2009 16:56:42 -0500 Subject: Fighting with the screensaver. In-Reply-To: <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <21ad25710911130846o3391543fpeb501aed06261cf0@mail.gmail.com> <15e53e180911130850r7e5345c3we30fe6c3f1226998@mail.gmail.com> <21ad25710911131305n1f20741ds1b80c115625fa36f@mail.gmail.com> <15e53e180911131312t1876455em57f4af82391a1fd8@mail.gmail.com> <21ad25710911131325i116c0cf1o4fd986fc2087d3b9@mail.gmail.com> Message-ID: On Fri, Nov 13, 2009 at 4:25 PM, Frederic Crozat wrote: > 2009/11/13 Richard Hughes : >> 2009/11/13 Frederic Crozat : >>> That would imply a dependency on gcm, which is not a really good idea. >> >> Sure, but the sort of dependency where it doesn't matter if gcm-apply >> doesn't exist... > > It does if people uses dispwin manually (or anything else to change LUT) ;) ISTM that gnome-screensaver would ideally just not touch the LUT. These days we have compositing, or even just taking a screen shot and fading to black with RENDER, for that. --Andy > > -- > Frederic Crozat > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pmjdebruijn at pcode.nl Sat Nov 14 18:23:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 14 Nov 2009 19:23:51 +0100 Subject: Standby also seems to reset the VideoLUT/crtc Message-ID: <1258223031.9981.3.camel@goliath> Hi, Similarly as discussed in "Re: Fighting with the screensaver." it also seems putting your laptop to sleep (standby) seems to reset the VideoLUT/xrandr crtc's... Can anybody test and confirm this... I have a Intel X4500MHD graphics chip, however, if I'm not mistaken the driver card/driver actually doesn't have anything to do with this, with the vcgt tag is applied via Xorg/xrandr. Or am I wrong about this? Regards, Pascal de Bruijn -- http://blog.pcode.nl/ http://photos.pcode.nl/ From compiz at sukimashita.com Sat Nov 14 19:19:20 2009 From: compiz at sukimashita.com (Martin S.) Date: Sat, 14 Nov 2009 20:19:20 +0100 Subject: Fighting with the screensaver. In-Reply-To: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> Message-ID: <1258226360.12545.10.camel@mirell> On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: > First I wonder if I'm the only person now who fights with the lut > deletion with gnome-screensaver. > It almost look like it is fixed, but I have still have this problem > with ubuntu 9.10. > https://bugzilla.gnome.org/show_bug.cgi?id=342850 This is somewhat old. I remember working on that bug myself as it was annoying for both gnome-screensaver and xscreensaver if I had profiles set. However, the issue was clearly fixed and I did't see this anymore on a range of systems since then (nvidia, intel mostly). > Should I expect the color manager to take care of this on it own? Like > running some kind of services? > When I use dispwin from the argyll package I normally take care of > this with a desktop file in the autostart folder with an exec line > like this. > Exec=/bin/bash -c ? gnome-screensaver-command ?exit; > dispwin -L;gnome-screensaver? This is not the right solution afaik. Applications should not fiddle with the color profile settings unless they are created to do just that. If you are sure gnome-screensaver causes it please file a bug. gnome-screensaver must respect the LUT settings here (the code apparently does already...). As noted above, this works fine on a couple of systems I tested for 2.28. What gfx driver do you use and which component versions (xorg, driver, gnome-screensaver? --- Martin S. From amluto at gmail.com Sat Nov 14 19:54:41 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sat, 14 Nov 2009 14:54:41 -0500 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: On my system, whatever xorg-xserver version F11 used interacted badly with intel to cause all kinds of things to reset the LUTs. For example, resuming, switching VTs, and even starting glxgears or okular (!). This has been fixed upstream and in F12. --Andy On Sat, Nov 14, 2009 at 2:19 PM, Martin S. wrote: > On Fri, 2009-11-13 at 17:38 +0100, Lars Tore Gustavsen wrote: >> First I wonder if I'm the only person now who fights with the lut >> deletion with gnome-screensaver. >> It almost look like it is fixed, but I have still have this problem >> with ubuntu 9.10. >> https://bugzilla.gnome.org/show_bug.cgi?id=342850 > > This is somewhat old. I remember working on that bug myself as it was > annoying for both gnome-screensaver and xscreensaver if I had profiles > set. > > However, the issue was clearly fixed and I did't see this anymore on a > range of systems since then (nvidia, intel mostly). > >> Should I expect the color manager to take care of this on it own? Like >> running some kind of services? >> When I use dispwin from the argyll package I normally ?take care of >> this with a desktop file in the autostart folder with an exec line >> like this. >> Exec=/bin/bash -c ? gnome-screensaver-command ?exit; >> ?dispwin -L;gnome-screensaver? > > This is not the right solution afaik. Applications should not fiddle > with the color profile settings unless they are created to do just that. > > If you are sure gnome-screensaver causes it please file a bug. > gnome-screensaver must respect the LUT settings here (the code > apparently does already...). > > As noted above, this works fine on a couple of systems I tested for > 2.28. > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > > --- Martin S. > > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list From compiz at sukimashita.com Sun Nov 15 02:04:29 2009 From: compiz at sukimashita.com (Martin S.) Date: Sun, 15 Nov 2009 03:04:29 +0100 Subject: [PATCH] Enable adding xrandr devices with no EDID Message-ID: <1258250669.25043.1.camel@mirell> Devices without EDID information or bad XRANDR implementations work again and get standard properties set. This restores functionality that existed before a recent change and allows me to assign color profiles on the broken nvidia xrandr implementation again. --- Martin S. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Enable-adding-xrandr-devices-with-no-EDID.patch Type: text/x-patch Size: 1874 bytes Desc: not available URL: From hughsient at gmail.com Sun Nov 15 15:03:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:03:32 +0000 Subject: [PATCH] Enable adding xrandr devices with no EDID In-Reply-To: <1258250669.25043.1.camel@mirell> References: <1258250669.25043.1.camel@mirell> Message-ID: <15e53e180911150703r28ba9e0dm9a1fbf760b2ab6ea@mail.gmail.com> 2009/11/15 Martin S. : > This restores functionality that existed before a recent change and > allows me to assign color profiles on the broken nvidia xrandr > implementation again. Applied, thanks. Richard. From hughsient at gmail.com Sun Nov 15 15:30:12 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 15 Nov 2009 15:30:12 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <1258223031.9981.3.camel@goliath> References: <1258223031.9981.3.camel@goliath> Message-ID: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> 2009/11/14 Pascal de Bruijn : > Similarly as discussed in "Re: Fighting with the screensaver." it also > seems putting your laptop to sleep (standby) seems to reset the > VideoLUT/xrandr crtc's... Seems plausible, although I would argue we should probably just get X or the kernel to save the gamma tables on suspend and restore them on resume. It certainly seems a better idea then getting the session to do it. Richard. From amluto at gmail.com Sun Nov 15 15:33:14 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 10:33:14 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 10:30 AM, Richard Hughes wrote: > 2009/11/14 Pascal de Bruijn : >> Similarly as discussed in "Re: Fighting with the screensaver." it also >> seems putting your laptop to sleep (standby) seems to reset the >> VideoLUT/xrandr crtc's... > > Seems plausible, although I would argue we should probably just get X > or the kernel to save the gamma tables on suspend and restore them on > resume. It certainly seems a better idea then getting the session to > do it. Heh, I replied to Pascal directly instead of to all. I think that X already does that with server 1.7 and up and (on my machine, anyway) intel driver 2.9.0 and up. (e.g. F12 but not F11) --Andy > > Richard. > _______________________________________________ > gnome-color-manager-list mailing list > gnome-color-manager-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-color-manager-list > From pedro at pedrocr.net Sun Nov 15 19:15:24 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 11:15:24 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> Message-ID: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: > Heh, I replied to Pascal directly instead of to all. ?I think that X > already does that with server 1.7 and up and (on my machine, anyway) > intel driver 2.9.0 and up. ?(e.g. F12 but not F11) I run Ubuntu Karmic (9.10) and this is not the case. I do have the 2.9.0 intel driver but the server is only 1.6.4. So I guess the config for it is in the xserver. Strangely when I set the ICC profile with xcalib it seems to survive the suspend. Pedro From amluto at gmail.com Sun Nov 15 19:40:15 2009 From: amluto at gmail.com (Andrew Lutomirski) Date: Sun, 15 Nov 2009 14:40:15 -0500 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: On Sun, Nov 15, 2009 at 2:15 PM, Pedro C?rte-Real wrote: > On Sun, Nov 15, 2009 at 7:33 AM, Andrew Lutomirski wrote: >> Heh, I replied to Pascal directly instead of to all. ?I think that X >> already does that with server 1.7 and up and (on my machine, anyway) >> intel driver 2.9.0 and up. ?(e.g. F12 but not F11) > > I run Ubuntu Karmic (9.10) and this is not the case. I do have the > 2.9.0 intel driver but the server is only 1.6.4. So I guess the config > for it is in the xserver. Strangely when I set the ICC profile with > xcalib it seems to survive the suspend. I believe it requires some cooperation between both. In the intel driver, in drmmode_set_mode_major, it says: #if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1,7,0,0,0) crtc->funcs->gamma_set(crtc, crtc->gamma_red, crtc->gamma_green, crtc->gamma_blue, crtc->gamma_size); #endif --Andy > > Pedro > From lars.tore at mulebakken.net Sun Nov 15 20:42:50 2009 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Sun, 15 Nov 2009 21:42:50 +0100 Subject: Fighting with the screensaver. In-Reply-To: <1258226360.12545.10.camel@mirell> References: <58497f010911130838v1624a1abm743d4763d6b2b0a3@mail.gmail.com> <1258226360.12545.10.camel@mirell> Message-ID: <58497f010911151242u54a7926am8f1a9128da6dec42@mail.gmail.com> On Sat, Nov 14, 2009 at 8:19 PM, Martin S. wrote: > > What gfx driver do you use and which component versions (xorg, driver, > gnome-screensaver? > I use ubuntu 9.10 and I have a ATI Radeon 9200 PRO card. I use the radeon xorg driver and the xorg version is 1.7.4. Gnome-screensaver is 2.28.0 Lars Tore Gustavsen From pedro at pedrocr.net Sun Nov 15 23:53:38 2009 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte=2DReal?=) Date: Sun, 15 Nov 2009 15:53:38 -0800 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> Message-ID: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> First, thanks for this Richard. Gnome/Linux have been needing this kind of simple support for color in a long time. On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: > Strangely when I set the ICC profile with xcalib it seems to survive the suspend. xcalib is probably doing something very different as its calibration also applies to all displays. On the other hand this means that it both survives the suspend and is applied when the display is disconnected/connected, both things that g-c-m currently doesn't handle properly. The suspend/resume stuff should be handled by X but the connect/disconnect should probably be handled by g-c-m as that policy shouldn't be in X. Cheers, Pedro From hughsient at gmail.com Mon Nov 16 08:29:32 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 16 Nov 2009 08:29:32 +0000 Subject: Standby also seems to reset the VideoLUT/crtc In-Reply-To: <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> References: <1258223031.9981.3.camel@goliath> <15e53e180911150730n1c85b3adn5f5af7acadcafaef@mail.gmail.com> <62e8012c0911151115tb4e695p2844767e8c8c7d1@mail.gmail.com> <62e8012c0911151553v14283dccjd83b0922f37313b4@mail.gmail.com> Message-ID: <15e53e180911160029u572db018x7d459eaf624c5765@mail.gmail.com> 2009/11/15 Pedro C?rte-Real : > First, thanks for this Richard. Gnome/Linux have been needing this > kind of simple support for color in a long time. > > On Sun, Nov 15, 2009 at 11:15 AM, Pedro C?rte-Real wrote: >> Strangely when I set the ICC profile with xcalib it seems to survive the suspend. > > xcalib is probably doing something very different as its calibration > also applies to all displays. xcalib sets the per-screen gamma tables, and gcm sets the per-output gamma tables. Richard. From pmjdebruijn at pcode.nl Wed Nov 25 17:28:33 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:28:33 +0100 Subject: Regression: gnome-color-manager segfaults after dispcal Message-ID: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Hi, Using gnome-color-manager 2.29.1~git20091124 it seems to segfault after running dispcal. Can anybody confirm this? Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Wed Nov 25 17:30:03 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 25 Nov 2009 18:30:03 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown Message-ID: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Hi, On my external display (HP LP2475w) connected via DVI to my Intel GMA, the precalibration "tips/guidelines" dialog isn't shown anymore. Has this been disabled on purpose, or is this an accidental regression? Regards, Pascal de Bruijn From hughsient at gmail.com Wed Nov 25 17:40:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:40:57 +0000 Subject: Regression: gnome-color-manager segfaults after dispcal In-Reply-To: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> References: <4c2c37f90911250928n753a5086qd8db212f9f32c61c@mail.gmail.com> Message-ID: <15e53e180911250940l2187d4e7s9755ed15edc867eb@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Using gnome-color-manager 2.29.1~git20091124 it seems to segfault > after running dispcal. You got a backtrace please? Thanks. Richard. From hughsient at gmail.com Wed Nov 25 17:48:20 2009 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 25 Nov 2009 17:48:20 +0000 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> Message-ID: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> 2009/11/25 Pascal de Bruijn : > Has this been disabled on purpose, or is this an accidental regression? The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 18:09:48 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:09:48 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore Message-ID: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Hi, It seems that gcm-prefs from current git does not apply the VideoLUT/vcgt tag anymore... gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 18:14:51 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 19:14:51 +0100 Subject: gcm-prefs: New profiles not showing up in the list Message-ID: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Hi, When display calibration finishes, the newly created profile does not show up in the list in gcm-prefs. Restarting gcm-prefs helps, then I _do_ see the new profile. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:24:32 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:24:32 +0100 Subject: Regression: gcm-prefs from current git doesn't apply videolut anymore In-Reply-To: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> References: <4c2c37f90911261009g4d8064f8u7d52bfbb57c80372@mail.gmail.com> Message-ID: <4c2c37f90911261224h24d5eb10u1cb767adde26787a@mail.gmail.com> On Thu, Nov 26, 2009 at 7:09 PM, Pascal de Bruijn wrote: > Hi, > > It seems that gcm-prefs from current git does not apply the > VideoLUT/vcgt tag anymore... > > gcm-apply _does_ seem to apply the VideoLUT/vcgt tag on login though... Changing the profile in gcm-prefs, closing gcm-prefs, and opening gcm-prefs again also does _not_ change the profile that is selected by default. So the problem is most likely not the application of another profile's VideoLUT, but the VideoLUT of the original default selected profile is always being applied, no matter which profile was manually selected afterward. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 20:54:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 21:54:28 +0100 Subject: Patch: Debian binary detection fix Message-ID: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Hi, I noticed the following recent commit to detect the Debinized Argyll binaries: http://git.gnome.org/cgit/gnome-color-manager/commit/?id=3b06571386be55a7b21424c256b88b2fb2ec6347 Conceptually the commit is fine, it's particularly great, this detect method is used for all of Argyll's utilities. Practically this is only applicable for targen at the moment. But since it's used for all binaries, gcm is automatically future proofed against other binaries getting renamed as well. Excellent behaviour. However, the detection is backwards. Please allow me to explain. Debian maintainers don't rename binaries just because they get a kick out of arbitrarily renaming random binaries. Debian has problems with conflicting binaries because their package repository is so big (almost 30,000 packages). This means they are forced to rename binaries in all but one package with conflicting binaries. This implies, on systems with a 'argyll-targen' binary, a 'targen' binary could be installed as well. But if a 'targen' binary is installed as well, it's most likely completely unrelated to Argyll, and will almost certainly fail when called by gcm. Therefore the detect should _first_ detect if the Debian renamed binaries exist, and if not, fallback to the original binary names. I've attached a small patch, which should "fix" the issue described above. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-debian-fix.patch Type: text/x-patch Size: 1022 bytes Desc: not available URL: From hughsient at gmail.com Thu Nov 26 21:07:11 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:07:11 +0000 Subject: Patch: Debian binary detection fix In-Reply-To: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> References: <4c2c37f90911261254y49b35366t13b85e32f505c013@mail.gmail.com> Message-ID: <15e53e180911261307l6b8b4427g13bc6de54b014f00@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Therefore the detect should _first_ detect if the Debian renamed > binaries exist, and if not, fallback to the original binary names. Agreed. I've attached the patch I've committed. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: look-for-debian-first.patch Type: text/x-patch Size: 1063 bytes Desc: not available URL: From alexandre.prokoudine at gmail.com Thu Nov 26 21:18:51 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 00:18:51 +0300 Subject: shifted dialog Message-ID: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Hi, The dialog that suggests to plug-in a measurement device somewhat unexpectedly pops up close to the left border of the screen, which is quite unfortunate for a 24" display :) Alexandre From hughsient at gmail.com Thu Nov 26 21:18:57 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:18:57 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> Message-ID: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > When display calibration finishes, the newly created profile does not > show up in the list in gcm-prefs. Can you try now please. Thanks, Richard. From hughsient at gmail.com Thu Nov 26 21:22:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 26 Nov 2009 21:22:33 +0000 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> 2009/11/26 Alexandre Prokoudine : > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Sure, I've shifted manually as by default it goes into the middle of the screen (as the calibration square is in the center) -- better ideas welcome. Richard. From pmjdebruijn at pcode.nl Thu Nov 26 21:24:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:24:02 +0100 Subject: shifted dialog In-Reply-To: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> Message-ID: <4c2c37f90911261324i570a102dsac872665b9e426fb@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Alexandre Prokoudine wrote: > Hi, > > The dialog that suggests to plug-in a measurement device somewhat > unexpectedly pops up close to the left border of the screen, which is > quite unfortunate for a 24" display :) Why is this a problem? If this dialog would be displayed centered, it would end up under the actual calibration window. So this is a good thing... Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 21:51:24 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 22:51:24 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> Message-ID: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> On Thu, Nov 26, 2009 at 10:18 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> When display calibration finishes, the newly created profile does not >> show up in the list in gcm-prefs. > > Can you try now please. You "fixed" it, and "broke" it at the same time... Now, after generating a new profile, "None" gets selected, but "None" does actually display copyright/vendor information, and seems to load the VideoLUT associates with the new profile. So this is most likely a UI issue. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Thu Nov 26 22:04:31 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 26 Nov 2009 23:04:31 +0100 Subject: Possible Regression: vendor/device metadata unknown Message-ID: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Hi, The profile I generated for my laptop a while back with an older checkout of gcm, seemed to semi-correctly detect vendor/device descriptions (154AT07-H01/154AT07-H01). When looking this up in my xorg.0.log, this should be: (WW) intel(0): Unknown vendor-specific block f (II) intel(0): SAMSUNG (II) intel(0): 154AT07-H01 However, a current git checkout produces this: ASCII data, length 21 chars: 0x0000: unknown manufacturer ASCII data, length 14 chars: 0x0000: unknown model If you require more information, please let me know. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Thu Nov 26 22:44:15 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 27 Nov 2009 01:44:15 +0300 Subject: shifted dialog In-Reply-To: <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> References: <733f2c730911261318t1dd44c3chfa1e131e2e33dea@mail.gmail.com> <15e53e180911261322j4f01a8f5u1b8f6678b9a9edc7@mail.gmail.com> Message-ID: <733f2c730911261444v5ccee119j1b8fd0d3f899ec76@mail.gmail.com> On 11/27/09, Richard Hughes wrote: > Sure, I've shifted manually as by default it goes into the middle of > the screen (as the calibration square is in the center) -- better > ideas welcome. Ah, makes sense then. Sorry for the trouble. Alexandre From hughsient at gmail.com Fri Nov 27 11:13:01 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:13:01 +0000 Subject: Possible Regression: vendor/device metadata unknown In-Reply-To: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> References: <4c2c37f90911261404lc92bd8bvfae5137df04f4911@mail.gmail.com> Message-ID: <15e53e180911270313q7a4e4ee9vce5dded99384a341@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > ?ASCII data, length 21 chars: > ? ?0x0000: unknown manufacturer > ?ASCII data, length 14 chars: > ? ?0x0000: unknown model > > If you require more information, please let me know. Can you pull git please, compile, and then run "./gcm-dump-edid" and then reply with the generated *.bin files attached. The complete log files for gcm-prefs would also be helpful. Thanks. Richard. From hughsient at gmail.com Fri Nov 27 11:35:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 27 Nov 2009 11:35:46 +0000 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> Message-ID: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> 2009/11/26 Pascal de Bruijn : > Now, after generating a new profile, "None" gets selected, but "None" > does actually display copyright/vendor information, and seems to load > the VideoLUT associates with the new profile. So this is most likely a > UI issue. Right, can you try one more time please. Thanks, Richard. From pmjdebruijn at pcode.nl Fri Nov 27 17:32:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 27 Nov 2009 18:32:59 +0100 Subject: gcm-prefs: New profiles not showing up in the list In-Reply-To: <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> References: <4c2c37f90911261014yd837697nc2a21613b23c9ee@mail.gmail.com> <15e53e180911261318v7cd403fap10b26c66c1293b60@mail.gmail.com> <4c2c37f90911261351hdc928c8madd101ce8bae7e51@mail.gmail.com> <15e53e180911270335s493b51d2ye7e300cefaeb4f9d@mail.gmail.com> Message-ID: <4c2c37f90911270932x1155c1c8k2525e5245c2856cf@mail.gmail.com> On Fri, Nov 27, 2009 at 12:35 PM, Richard Hughes wrote: > 2009/11/26 Pascal de Bruijn : >> Now, after generating a new profile, "None" gets selected, but "None" >> does actually display copyright/vendor information, and seems to load >> the VideoLUT associates with the new profile. So this is most likely a >> UI issue. > > Right, can you try one more time please. Thanks, Jep, that seems fixed as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:11:17 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:11:17 +0100 Subject: Bug: Recalibrating a display twice makes a single profile show up twice Message-ID: <4c2c37f90911280511v62082445i88480e326510c14b@mail.gmail.com> Hi, I think I found a small bug, when recalibrating a display twice (without restarting gcm-prefs), only a single ~/.color/icc/mydisplay.icc is generated however (actually two files are generated obviously, but the first is just overwritten by the second), it is added twice to the profile combobox in gcm-prefs. To reproduce: 1. Start gcm-prefs 2. Calibrate 3. Calibrate (again) 4. Now you'll notice the single ICC profile is listed twice in the combobox. The bigger question is what behavior do we want? 1. The slightly older profile is overwritten, and only the newer profile is displayed (once) in the gcm-prefs combo box. This makes a calibration history impossible. 2. Each calibration run, suffixes the profile filename (currently based on the serial???) with date and time (important, since we other can only calibrate once a day, without overwrites) to prevent older ones from getting overwritten. This automatically makes the current behavior of gcm-prefs correct by adding a new profile to the combobox. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:16:08 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:16:08 +0100 Subject: Profile Filenames Message-ID: <4c2c37f90911280516o40d616f6pb2a4dcae0594afb4@mail.gmail.com> Hi, I noticed gcm(-prefs) currently places newly generated profiles as: ~/.color/icc/serial.icc As I already indicated I think it would be wise to at least include date and time in the filename. I'd prefer something more human readable over the serial as well: ~/.color/icc/gcm_acer-al2016w_200911281415.icc As you'll noticed above, I think it's a good idea to also prefix gcm-prefs generated profiles with gcm, to clearly distinguish between profiles generated by gcm-prefs, and profiles gotten elsewhere (possibly from the vendor CD). I'd love to hear your thoughts on this. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 13:30:28 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 14:30:28 +0100 Subject: Regression?: the precalibration "tips" dialog isn't shown In-Reply-To: <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> References: <4c2c37f90911250930g2ee7907fg3f294dc83cd3a197@mail.gmail.com> <15e53e180911250948w5b331236hbeab88a100ff823d@mail.gmail.com> Message-ID: <4c2c37f90911280530i63ed52a9w989833570c5146df@mail.gmail.com> On Wed, Nov 25, 2009 at 6:48 PM, Richard Hughes wrote: > 2009/11/25 Pascal de Bruijn : >> Has this been disabled on purpose, or is this an accidental regression? > > The latter, thanks for noticing this. I've re-enabled it in git master. Thanks. Sorry, it took me a while to verify, but on my external display I can indeed confirm this has been fixed. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sat Nov 28 17:43:55 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 28 Nov 2009 18:43:55 +0100 Subject: auto hardware detection not working Message-ID: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Hi, I enabled hardware detection in my builds of GNOME Color Manager. However it's not working, the "Calibrate" button is enabled, no matter if a colorimeter is attached or not. Assuming gcm-prefs isn't the problem, I'm guessing this would be a udev issue? Or better a udev rules issue? Is anybody willing to give me some pointers on how to debug this issue? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Nov 28 20:49:26 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 28 Nov 2009 20:49:26 +0000 Subject: auto hardware detection not working In-Reply-To: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> Message-ID: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> 2009/11/28 Pascal de Bruijn : > Is anybody willing to give me some pointers on how to debug this issue? Can you attach the output of gnome-color-manager --verbose as you plug in and plug out the adaptor please? Thanks. Richard. From pmjdebruijn at pcode.nl Sun Nov 29 12:53:39 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sun, 29 Nov 2009 13:53:39 +0100 Subject: Profile description for laptop displays Message-ID: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Hi, Currently GCM is using EDID to determine make and models for displays. This information is then usually incorporated into the profile make/model and description. For external displays this is great behavior, however for laptops this may get a bit confusing. An example: My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's display. However, whenever a user wants to assign a profile to his laptop screen, it's not obvious this HP laptop needs a profile with Samsung in it's description. This may confuse people. So for laptop display _descriptions_ it might be a good idea to use the DMI Product Name instead of the panels EDID. pmjdebruijn at unicron:~$ sudo dmidecode | grep -i compaq Product Name: HP Compaq 6730s Please do note, I think we should keep using the panel's EDID for the ICC profile make/model tags, since this is technically correct, no matter if it's a laptop display or not. Only the description needs to be made user friendly. Regards, Pascal de Bruijn From hughsient at gmail.com Sun Nov 29 21:42:33 2009 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 29 Nov 2009 21:42:33 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> Message-ID: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's > display. ?However, whenever a user wants to assign a profile to his > laptop screen, it's not obvious this HP laptop needs a profile with > Samsung in it's description. This may confuse people. Agreed: commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de Author: Richard Hughes Date: Sun Nov 29 21:04:48 2009 +0000 Use DMI data to improve the device title and fill in missing model information :100644 100644 4504005... 0289dbd... M src/gcm-client.c commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 Author: Richard Hughes Date: Sun Nov 29 21:04:15 2009 +0000 Add a GcmDmi object to parse DMI data about the host machine :100644 100644 76796f2... c6b219b... M src/Makefile.am :000000 100644 0000000... ed48ea9... A src/gcm-dmi.c :000000 100644 0000000... 0a4897c... A src/gcm-dmi.h :100644 100644 0a4bbb4... 5624175... M src/gcm-self-test.c Can you verify the new functionality please. Thanks. Richard. From alexandre.prokoudine at gmail.com Sun Nov 29 23:38:27 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 02:38:27 +0300 Subject: hardware autodetection Message-ID: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Hi, What do I need to have installed in my system to get hardware auto-detection: yes after running ./configure ? I do see "checking for GUDEV... yes" in the output. Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:41:58 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:41:58 +0100 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> On Mon, Nov 30, 2009 at 12:38 AM, Alexandre Prokoudine wrote: > Hi, > > What do I need to have installed in my system to get > > hardware auto-detection: ? yes > > after running ./configure ? > > I do see "checking for GUDEV... yes" in the output. You need a new ArgyllCMS release with the new udev rules. ArgyllCMS 1.1.0-rc should do. My Debian package has the following Build-Depends: Build-Depends: debhelper (>= 7), autotools-dev, cdbs, dpatch, docbook-utils, gtk-doc-tools, gnome-doc-utils, libx11-dev, libxxf86vm-dev, libxrandr-dev, libglib2.0-dev, libgtk2.0-dev, libgnome-desktop-dev, libgconf2-dev, libunique-dev (>= 1.0), libvte-dev (>= 0.22), libgudev-1.0-dev, libdbus-glib-1-dev Then it should work. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Sun Nov 29 23:46:02 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:46:02 +0100 Subject: auto hardware detection not working In-Reply-To: <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> References: <4c2c37f90911280943n5ef52b5fkbb02c090219ba33d@mail.gmail.com> <15e53e180911281249k73db21bap74e55a814752cd71@mail.gmail.com> Message-ID: <4c2c37f90911291546n19ee7040j48af2ef424e74209@mail.gmail.com> On Sat, Nov 28, 2009 at 9:49 PM, Richard Hughes wrote: > 2009/11/28 Pascal de Bruijn : >> Is anybody willing to give me some pointers on how to debug this issue? > > Can you attach the output of gnome-color-manager --verbose as you plug > in and plug out the adaptor please? Thanks. I think I was mistaken, it seems to work now. My bad. Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Mon Nov 30 01:14:10 2009 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 30 Nov 2009 04:14:10 +0300 Subject: hardware autodetection In-Reply-To: <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> <4c2c37f90911291541i5321126jdcb5f94b257e83e1@mail.gmail.com> Message-ID: <733f2c730911291714l7536bba9n74c11bb3b000591a@mail.gmail.com> On 11/30/09, Pascal de Bruijn wrote: > You need a new ArgyllCMS release with the new udev rules. ArgyllCMS > 1.1.0-rc should do. Well, it's argyll-1.1.0-rc1-3pmjdebruijn0~karmic all the way here :) Alexandre From pmjdebruijn at pcode.nl Sun Nov 29 23:27:59 2009 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 30 Nov 2009 00:27:59 +0100 Subject: Profile description for laptop displays In-Reply-To: <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> Message-ID: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> On Sun, Nov 29, 2009 at 10:42 PM, Richard Hughes wrote: > 2009/11/29 Pascal de Bruijn : >> My HP Compaq 6730s laptop has an el'cheapo Samsung panel for it's >> display. ?However, whenever a user wants to assign a profile to his >> laptop screen, it's not obvious this HP laptop needs a profile with >> Samsung in it's description. This may confuse people. > > Agreed: > > commit 70175a9e48ac5a8e0822b6e186bf9e412134a8de > commit e4683b90160a8fc70c5b5b24cecdf29c674c8c65 > > Can you verify the new functionality please. Thanks. That was fast as usual :) It works mostly... I've attached a screenshot. I noticed you included the product_version as well, at least on my laptop it's actually the BIOS revision, I'm not sure what this is on other laptops. It's probably not that relevant... I noticed you're currently filling the ICC Make with the username, it seems rather redundant with the copyright. Besides the point that the field wasn't ment to be used like that. I'd stick the EDID info there (even with laptops). For the Model field as well, EDID is most likely best and most accurate here. For example: Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, only lookup in the gcm-prefs GUI). Model: 154AT07-H01 Storing the EDID info as verbatim as possible in the ICC make/models fields, will make it easier to auto match displays and profiles in the future. Storing the EDID verbatim without looking up in pnp.ids prevents false data from conflicting lookups (like my Samsung/Seiko issue) from ending up in the profile itself. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-dmi.png Type: image/png Size: 44070 bytes Desc: not available URL: From hughsient at gmail.com Mon Nov 30 08:19:46 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 08:19:46 +0000 Subject: hardware autodetection In-Reply-To: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> References: <733f2c730911291538t63db094emf625a4451363e201@mail.gmail.com> Message-ID: <15e53e180911300019x1c1a7cfbu43741868d045dce4@mail.gmail.com> 2009/11/29 Alexandre Prokoudine : > What do I need to have installed in my system to get You need to configure with --enable-hardware-detection and to make sure you have the fixed Argyllcms udev rules file. Richard. From hughsient at gmail.com Mon Nov 30 10:10:34 2009 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 30 Nov 2009 10:10:34 +0000 Subject: Profile description for laptop displays In-Reply-To: <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> References: <4c2c37f90911290453x143c6820nb27f3a6b6188e3c7@mail.gmail.com> <15e53e180911291342o2b8755aavad083da3dcd849d2@mail.gmail.com> <4c2c37f90911291527v71d2cf9cy6bb41add8c7b3683@mail.gmail.com> Message-ID: <15e53e180911300210tae5b9a0kaa94ead83633e413@mail.gmail.com> 2009/11/29 Pascal de Bruijn : > I noticed you included the product_version as well, at least on my > laptop it's actually the BIOS revision, I'm not sure what this is on > other laptops. It's probably not that relevant... Hmm, it seems the manufacturers were in a rush when they designed your laptop! The bios version, logically, belongs in bios_version :-) Could you attach the output of "cat /sys/class/dmi/id/*" and we'll try and work around bios issues like this. Thanks. > I noticed you're currently filling the ICC Make with the username, it > seems rather redundant with the copyright. Besides the point that the > field wasn't ment to be used like that. I'd stick the EDID info there > (even with laptops). For the Model field as well, EDID is most likely > best and most accurate here. I deliberately changed it, as the vendor is supposed to be the person or company that designed or created the profile. In this sense, it seemed wrong to say that the profile was created "by Lenovo" when it was created by me, for my Lenovo display. > For example: > > Make: SEC (don't lookup in pnp.ids for storage in the ICC profile, > only lookup in the gcm-prefs GUI). > Model: 154AT07-H01 > > Storing the EDID info as verbatim as possible in the ICC make/models > fields, will make it easier to auto match displays and profiles in the > future. Hmm, I think the fields have to be displayable. We need to look at adding private fields if we want to add any machine parsable data into the ICC file. > Storing the EDID verbatim without looking up in pnp.ids prevents false > data from conflicting lookups (like my Samsung/Seiko issue) from > ending up in the profile itself. I think the lookup is valuable as it works most of the time. Your panel should have encoded SAM into the PNP field, not SEC, unless of course the panel really is a Seiko panel that's been rebadged as a Samsung. For what it's worth, my nice expensive LG panel is actually a generic Goldstar chipset with LG additions and plastic wrapping. Hence, it shows up as "Goldstar" as the vendor. :-( Richard.