- This topic has 25 replies, 2 voices, and was last updated 5 years ago by
.
-
Posts
-
Hello,
I’m a beginner with DisplayCAL, and a brand new i1studio, on Linux only so dearly needing DisplayCAL for just anything đ
I repeatedly get the above error each time I try to start a calibration (it seems Argyll is correctly installed, at least, I have no request to e. g. locate it at startup).
On this forum to my delight I actually zoomed rapidly to Dominig’s post describing exactly the same symptoms, but there seems to be more to this in my case đI tried to comment on his post but I may have done it incorrectly as I don’t really see it (or else it’s marked closed?)
Anyway : DisplayCAL 3.7.2 / Argyll 2.0.1 on Debian 9 & latest xrite i1studio .deb installed. Same error, and like in Dominig’s case the log says the same, not being able to send commands to the device…
Any further advice?
Having no mac nor PC you are my only hope! đ
Thank you!
Calibrite ColorChecker Studio on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Florian that’s what I did initially but I may have done it wrong (at least, at the url I just gave I see my first intervention)
Are you using DisplayCAL 3.5.2 or newer and ArgyllCMS 2.0 or newer?
Yes, as I said DC3.7.2 and ACMS 2.01
Have you checked that the udev rules were installed successfully and your user added to the colord group?
I totally ignored there was such a group. How can I check its existence, and add my user to it?
Have you tried rebooting, or disconnecting/reconnecting the instrument?
Yes
Thank you for your fast reaction!
Hervé
I totally ignored there was such a group. How can I check its existence, and add my user to it?
Check the log after using “Tools” -> “Instrument” -> “Install ArgyllCMS instrument configuration files”. You’ll see udev rule installation, whether the ‘colord’ group existed or was created, and whether your user was successfully added to it.
Check the log after using âToolsâ -> âInstrumentâ -> âInstall ArgyllCMS instrument configuration filesâ. Youâll see udev rule installation, whether the âcolordâ group existed or was created, and whether your user was successfully added to it.
OK, I proceeded otherwise (just checking the ‘colord’ group existed and my user belongs to it), this appears OK.
I also de-installed then re-installed the config files : the log gives the following, which looks correct (french interface) :
09:35:28,742 ——————————————————————————–
09:35:28,742 Répertoire de travail :
09:35:28,743 /
09:35:28,743 tmp/
09:35:28,744 DisplayCAL-psLNwb/
09:35:28,744
09:35:28,744 Ligne de commandes :
09:35:28,745 /sbin/udevadm
09:35:28,745 control
09:35:28,745 –reload-rules
09:35:28,745
09:35:28,751 DisplayCAL: Waiting for EOF
09:35:28,813 Password:
09:35:28,823 DisplayCAL: Reached EOF (OK)
09:35:28,986 Installation des fichiers de configuration de sondes de mesure dâArgyllCMS âČ
âł terminĂ©e.I may be a bit pessimistic, but is there a possibility that the (brand-new!) i1Studio device may be wrong? I just tried to install the xrite app on my phone, plugged an USB-on-the-go adapter then the xrite, and the phone app tells me it doesn’t see the device… The only thing happening when I plug the i1Studio, up to now, is a brief white flash, both when plugging it on the Linux and on the phone. DisplayCAL correctly identified a ‘ColorMunki Design/Photo, i1Studio’ device in the device selector, although the log file when re-asking is very thin:
09:40:40,759 Inventaire des pĂ©riphĂ©riques dâaffichage et des ports de communicationâŠ
09:40:40,934
09:40:43,042 ArgyllCMS 2.0.1
09:40:43,043 ⊠opération terminée.
09:41:13,685 ———————-Thank you for taking care!
There should be more in the log after installing the udev rules, at the copying to /udev/rules.d generates several log entries.
Make sure /lib/udev/rules.d/55-Argyll.rules matches the respective file that comes with ArgyllCMS 2.x (it should have an i1 Studio entry).
Make sure /lib/udev/rules.d/55-Argyll.rules matches the respective file that comes with ArgyllCMS 2.x (it should have an i1 Studio entry).
Indeed there was no Argyll rule in /lib/udev/rules.d/
I copied both 55-Argyll.rules and 45-Argyll.rules from the Argyll package down there.
I then tried to update issueing ~$ sudo udevadm trigger in the same terminal, then restarted DisplayCAL. Still not working :
17:41:18,518 DisplayCAL: Starting interaction with subprocess
17:41:19,067 Number of patches = 3
17:41:19,080 Setting up the instrument
17:41:19,081 usb_open_port: open ‘/dev/bus/usb/001/007’ config 1 failed (-1) (Permissions ?)
17:41:19,081 usb_open_port: open ‘/dev/bus/usb/001/007’ config 1 failed (-1) (Permissions ?)
17:41:19,082 dispread: Error – new_disprd failed with ‘Instrument Access Failed’I’ll now try to deinstall/reinstall from DisplayCAL and get more in the log
Thank you again for your patience!
H.
(in the meanwhile I managed to run the i1Studio from Argyll’s Android app, so I now consider it is not dead on its side)
I come back having uninstalled then reinstalled Argyll’s rules from within DisplayCAL :
- I note that DisplayCAL does not install files in lib/udev/rules.d but in etc/udev/rules.d (in lib/udev/rules.d on the other hand there is a file named 55-Argyll.rules that contains a reference to my i1Studio device
- I dared launch DisplayCAL as su, then re-locate ArgyllCMS files etc. and in this case it works, which definitely means it is actually a problem of access rights
- Hereafter the long log for, successively, the deinstall then re-install (as a normal user), as you suggested :
15:47:55,427 -------------------------------------------------------------------------------- 15:47:55,427 RĂ©pertoire de travail : 15:47:55,428 / 15:47:55,428 home/ 15:47:55,428 saincth/ 15:47:55,429 .local/ 15:47:55,429 share/ 15:47:55,429 DisplayCAL/ 15:47:55,429 backup/ 15:47:55,430 20190413T154755/ 15:47:55,430 etc/ 15:47:55,431 udev/ 15:47:55,431 rules.d/ 15:47:55,431 15:47:55,431 Ligne de commandes : 15:47:55,432 mv 15:47:55,432 /etc/udev/rules.d/55-Argyll.rules 15:47:55,432 55-Argyll.rules 15:47:55,432 15:47:55,433 DisplayCAL: Waiting for EOF 15:47:55,505 Password: 15:47:55,506 DisplayCAL: Reached EOF (OK) 15:47:55,554 15:47:55,586 -------------------------------------------------------------------------------- 15:47:55,595 RĂ©pertoire de travail : 15:47:55,595 / 15:47:55,595 home/ 15:47:55,596 saincth/ 15:47:55,596 .local/ 15:47:55,596 share/ 15:47:55,596 DisplayCAL/ 15:47:55,597 backup/ 15:47:55,597 20190413T154755/ 15:47:55,597 lib/ 15:47:55,598 udev/ 15:47:55,599 rules.d/ 15:47:55,599 15:47:55,599 Ligne de commandes : 15:47:55,600 mv 15:47:55,600 /lib/udev/rules.d/55-Argyll.rules 15:47:55,600 55-Argyll.rules 15:47:55,600 15:47:55,612 DisplayCAL: Waiting for EOF 15:47:55,674 Password: 15:47:55,695 DisplayCAL: Reached EOF (OK) 15:47:55,801 -------------------------------------------------------------------------------- 15:47:55,802 RĂ©pertoire de travail : 15:47:55,802 / 15:47:55,802 tmp/ 15:47:55,803 DisplayCAL-X7aYtA/ 15:47:55,803 15:47:55,803 Ligne de commandes : 15:47:55,803 /sbin/udevadm 15:47:55,804 control 15:47:55,805 --reload-rules 15:47:55,806 15:47:55,819 DisplayCAL: Waiting for EOF 15:47:55,883 Password: 15:47:55,905 DisplayCAL: Reached EOF (OK) 15:47:56,121 DĂ©sinstallation des fichiers de configuration de sonde de mesure dâArgyllCMS âČ âł terminĂ©e. 15:48:10,602 -------------------------------------------------------------------------------- 15:48:10,602 RĂ©pertoire de travail : 15:48:10,603 / 15:48:10,603 etc/ 15:48:10,603 udev/ 15:48:10,604 rules.d/ 15:48:10,604 15:48:10,604 Ligne de commandes : 15:48:10,604 cp 15:48:10,605 --remove-destination 15:48:10,605 /home/saincth/Downloads/Argyll_V2.0.1/usb/55-Argyll.rules 15:48:10,605 55-Argyll.rules 15:48:10,605 15:48:10,606 DisplayCAL: Waiting for EOF 15:48:10,615 Password: 15:48:10,622 DisplayCAL: Reached EOF (OK) 15:48:10,643 15:48:10,719 15:48:10,723 -------------------------------------------------------------------------------- 15:48:10,724 RĂ©pertoire de travail : 15:48:10,724 / 15:48:10,724 etc/ 15:48:10,725 udev/ 15:48:10,725 rules.d/ 15:48:10,727 15:48:10,728 Ligne de commandes : 15:48:10,728 chmod 15:48:10,729 0644 15:48:10,729 55-Argyll.rules 15:48:10,729 15:48:10,736 DisplayCAL: Waiting for EOF 15:48:10,800 Password: 15:48:10,811 DisplayCAL: Reached EOF (OK) 15:48:10,914 -------------------------------------------------------------------------------- 15:48:10,920 RĂ©pertoire de travail : 15:48:10,921 / 15:48:10,921 tmp/ 15:48:10,921 DisplayCAL-X7aYtA/ 15:48:10,922 15:48:10,922 Ligne de commandes : 15:48:10,926 /sbin/udevadm 15:48:10,926 control 15:48:10,927 --reload-rules 15:48:10,927 15:48:10,927 DisplayCAL: Waiting for EOF 15:48:10,985 Password: 15:48:10,996 DisplayCAL: Reached EOF (OK) 15:48:11,182 Installation des fichiers de configuration de sondes de mesure dâArgyllCMS âČ âł terminĂ©e.
I copied both 55-Argyll.rules and 45-Argyll.rules from the Argyll package down there.
Delete 45-Argyll.rules, it’s for ancient udev versions. Modern systems will at best ignore the file, and at worst it might cause errors.
I note that DisplayCAL does not install files in lib/udev/rules.d but in etc/udev/rules.d
That’s correct. /lib/udev/rules.d is for default (system) rules, /etc/udev/rules.d is for custom rules.
(in lib/udev/rules.d on the other hand there is a file named 55-Argyll.rules that contains a reference to my i1Studio device
Why is this file still there after uninstallation though? I can see it being moved to the backup location during uninstallation in the log above.
I copied both 55-Argyll.rules and 45-Argyll.rules from the Argyll package down there.
Delete 45-Argyll.rules, itâs for ancient udev versions. Modern systems will at best ignore the file, and at worst it might cause errors.
done
I note that DisplayCAL does not install files in lib/udev/rules.d but in etc/udev/rules.d
Thatâs correct. /lib/udev/rules.d is for default (system) rules, /etc/udev/rules.d is for custom rules.
So I removed the 55.etc from /lib/udev/rules.d
(in lib/udev/rules.d on the other hand there is a file named 55-Argyll.rules that contains a reference to my i1Studio device
Why is this file still there after uninstallation though? I can see it being moved to the backup location during uninstallation in the log above.
it was there before I deinstall in fact.
And… after all this I’m still stuck with the perms issue
So, 55-Argyll.rules in /etc/udev/rules.d/ and contains i1 Studio entry?
Have you disconnected and reconnected the instrument?
So, 55-Argyll.rules in /etc/udev/rules.d/ and contains i1 Studio entry?
Yes, among other it contains the lines:
# ColorMunki i1 Studio
ATTRS{idVendor}==”0768″, ATTRS{idProduct}==”6008″, ENV{COLORD_SENSOR_KIND}=”color-munki-photo” ENV{COLORD_SENSOR_CAPS}=”lcd crt projector printer spot ambient”Have you disconnected and reconnected the instrument?
Yes
I also ran DisplayCAL as su (sudo displaycal in a terminal) : in this case the previous error is not shown; I advance a couple of steps (self calibration) then once the initially black window has been measured three times I get another error, ‘Write error : Unable to open file ‘0_16.ti3′ for writing’ (the log file then announces :
20:20:49,356 DisplayCAL: Waiting for send buffer
20:21:06,485 DisplayCAL: Sending buffer: ‘ ‘
20:21:06,536 Correct position then hit Esc or Q to give up, any other key to retry:
20:21:21,473 Patch 3 of 3
20:21:21,476 The instrument can be removed from the screen.
20:21:21,859 dispread: Error – Write error : Unable to open file ‘0_16.ti3’ for writing
20:21:21,867 DisplayCAL: Reached EOF (OK)
20:21:21,972 ⊠interrompu.One last thing : I see I have AppArmor installed in my Debian system, shich (if I understand correctly) may not be there by default. Is there a possibility that Apparmor ‘constrains’ DisplayCAL to e. g. not writing to ports or files?
(but anyway, the difference in behavior between a superuser-launched DisplayCAL and the normal launch really hints to a permissions issue…)
Thank you!
Hervé
