Home › Forums › Help and Support › Screen stuck on initial flash
- This topic has 19 replies, 2 voices, and was last updated 8 years, 9 months ago by
finknottle.
-
AuthorPosts
-
2017-08-15 at 20:15 #8386
So I have this issue from time to time. When you open dispcal, there is an initial flash when the entire screen is kinda overcast. It gets stuck over there for me sometimes. Trying to reset the gamma table from the gui doesn’t work either, and loading a profile also errors out. I captured the syslog when this happened if it has anything relevant. System is a an optimus laptop with nouveau drivers currently on Ubuntu 16.04. Link to the log:
2017-08-15 at 20:15 #8390Possibly a graphics driver bug.
2017-08-15 at 20:30 #8391What happens during the initial flash ? If I can consistently reproduce the issue, that would help in raising relevant bug reports for graphics drivers.
2017-08-15 at 20:42 #8393This is from dispcal’s log:
2017-08-15 14:33:03,230 displaycal 3.3.3.0 2017-08-08T18:42:51.152932Z 2017-08-15 14:33:03,232 Ubuntu 16.04 xenial x86_64 2017-08-15 14:33:03,232 Python 2.7.12 (default, Nov 19 2016, 06:48:10) 2017-08-15 14:33:03,232 [GCC 5.4.0 20160609] 2017-08-15 14:33:03,233 ImportError: No module named faulthandler 2017-08-15 14:33:03,340 wxPython 3.0.2.0 gtk2 (classic) 2017-08-15 14:33:03,340 Encoding: UTF-8 2017-08-15 14:33:03,340 File system encoding: UTF-8 2017-08-15 14:33:03,528 Starting up... 2017-08-15 14:33:03,655 Audio module: pygame 1.9.1release 2017-08-15 14:33:05,016 Enumerating display devices and communication ports... 2017-08-15 14:33:05,016 /home/user/Downloads/Argyll_V1.9.2/bin 2017-08-15 14:33:11,328 ArgyllCMS 1.9.2 2017-08-15 14:33:11,330 ...ok. 2017-08-15 14:33:13,752 Checking video card gamma table access for display 1... 2017-08-15 14:33:15,014 DisplayCAL: Trying to terminate subprocess... 2017-08-15 14:33:15,015 ...failed! 2017-08-15 14:33:15,015 Initializing GUI... 2017-08-15 14:33:15,265 ...subprocess terminated. 2017-08-15 14:33:15,323 2017-08-15 14:33:16,284 ...ok. 2017-08-15 14:33:16,286 Ready. 2017-08-15 14:33:16,454 Setting up scripting host at 127.0.0.1:15411 2017-08-15 14:33:16,521 Check for application update... 2017-08-15 14:33:16,804 DisplayCAL is up-to-date. 2017-08-15 14:33:17,089 ArgyllCMS is up-to-date. 2017-08-15 14:34:27,037 Loading calibration curves from file... 2017-08-15 14:34:27,038 /home/user/.local/share/DisplayCAL/storage/B156HW01 #1 2017-08-07 23-19 2.2 F-S XYZLUT+MTX/B156HW01 #1 2017-08-07 23-19 2.2 F-S XYZLUT+MTX.icc 2017-08-15 14:34:27,041 ...failed! 2017-08-15 14:34:27,042 Calibration curves could not be loaded. 2017-08-15 14:34:27,042 /home/user/.local/share/DisplayCAL/storage/B156HW01 #1 2017-08-07 23-19 2.2 F-S XYZLUT+MTX/B156HW01 #1 2017-08-07 23-19 2.2 F-S XYZLUT+MTX.icc 2017-08-15 14:34:33,516 Executing BaseApp.OnExit()
2017-08-15 at 20:49 #8395It checks videoLUT access by loading a reduced contrast calibration and then checking whether the videoLUT matches said calibration. In your case, it looks like dispwin just crashes. You can probably get more output by running it on terminal with debugging enabled (e.g.
dispwin -v -D8 -c)2017-08-15 at 20:58 #8397That command works. It reset the gamma table. This is the output:
Checking XRandR 1.2 VideoLUT access Display 0 name = ':0.0' Got EDID for display About to open dispwin object on the display using ucmm for profile installation new_dispwin: Opened display OK dispwin_get_ramdac called Getting gamma using Randr 1.2 dispwin_get_ramdac returning OK Saved original VideoLUT new_dispwin: return successfully About to clear the calibration dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK About to destroy dispwin object dispwin_del called dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK Restored original ramdac About to close display finishedAlso, this command (normally) works too:
displaycal-apply-profiles ================================================================================ Loading calibration curves of current display device profile... Enumerating display devices and communication ports... /home/user/Downloads/Argyll_V1.9.2/bin ArgyllCMS 1.9.2 ...ok. -------------------------------------------------------------------------------- Working directory: / home/ user/ .local/ share/ icc/ Command line: dispwin -v -d1 'B156HW01 #1 2017-08-07 23-19 2.2 F-S XYZLUT+MTX.icc' About to open dispwin object on the display About to set display to given calibration Calibration set About to destroy dispwin object
It doesn’t work if the GUI is open in the garbled state. If I close the GUI, and run this command, it brings the display back to the calibrated state. So this is somehow related to what the GUI does ?
-
This reply was modified 8 years, 9 months ago by
finknottle.
2017-08-15 at 21:00 #8399It doesn’t work if the GUI is open in the garbled state. If I close the GUI, and run this command, it brings the display back to the calibrated state.
Make sure you’re actually using the same version of ArgyllCMS (check in DisplayCAL under “File” -> “Locate executables”).
So this is somehow related to what the GUI does ?
No, dispwin is run as a subprocess.
2017-08-15 at 21:10 #8400The reason that command doesn’t work when the GUI is open is probably because of a lock ? There is no output when I run “displaycal-apply-profiles” when the GUI is open. If I run it with strace, one of the last strings I see is “/home/user/.config/DisplayCAL/DisplayCAL.lock”. Regarding dispwin versions. I have a system one, and I have the one that dispcal downloads in my home directory. The command “dispwin -v -D8 -c” works for both of them. This however, just resets the gamma table, right ? Is there a command that would create the initial low contrast flash ?
2017-08-15 at 21:16 #8401The reason that command doesn’t work when the GUI is open is probably because of a lock ? There is no output when I run “displaycal-apply-profiles” when the GUI is open. If I run it with strace, one of the last strings I see is “/home/user/.config/DisplayCAL/DisplayCAL.lock”.
No, that’s just to keep track of open instances of the main application.
Is there a command that would create the initial low contrast flash ?
Yes. You have to figure out where test.cal is installed (probably /usr/share/DisplayCAL/test.cal) and provide it as last argument (after -c) to dispwin.
2017-08-15 at 21:30 #8403That works too.
./dispwin -v -D8 -c /usr/share/DisplayCAL/test.cal Checking XRandR 1.2 VideoLUT access Display 0 name = ':0.0' Got EDID for display About to open dispwin object on the display new_dispwin called using ucmm for profile installation new_dispwin: Opened display OK new_dispwin: DirectColor fdepth 8, rdepth 8, ndepth 8, edepth 16, r/g/b shifts 16 8 0 dispwin_get_ramdac called Getting gamma using Randr 1.2 dispwin_get_ramdac returning OK Saved original VideoLUT new_dispwin: return sucessfully About to clear the calibration dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK About to set display to given calibration dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK Calibration set About to destroy dispwin object dispwin_del called dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK Restored original ramdac About to close display finished user@plum:~/Downloads/Argyll_V1.9.2/bin$ ./dispwin -v -D8 -c Checking XRandR 1.2 VideoLUT access Display 0 name = ':0.0' Got EDID for display About to open dispwin object on the display new_dispwin called using ucmm for profile installation new_dispwin: Opened display OK new_dispwin: DirectColor fdepth 8, rdepth 8, ndepth 8, edepth 16, r/g/b shifts 16 8 0 dispwin_get_ramdac called Getting gamma using Randr 1.2 dispwin_get_ramdac returning OK Saved original VideoLUT new_dispwin: return sucessfully About to clear the calibration dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK About to destroy dispwin object dispwin_del called dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK Restored original ramdac About to close display finishedSwitching back and forth works too. Any way to capture detailed log for the gui launch and/or “displaycal-apply-profiles” ? I can attach the strace output, but it may be too verbose.
-
This reply was modified 8 years, 9 months ago by
finknottle.
2017-08-15 at 22:15 #8405After loading test.cal, you can then check it with
dispwin -v -D8 -V2017-08-15 at 22:22 #8406That shows that verification passed.
./dispwin -v -D8 -V /usr/share/DisplayCAL/test.cal Checking XRandR 1.2 VideoLUT access Display 0 name = ':0.0' Got EDID for display About to open dispwin object on the display new_dispwin called using ucmm for profile installation new_dispwin: Opened display OK new_dispwin: DirectColor fdepth 8, rdepth 8, ndepth 8, edepth 16, r/g/b shifts 16 8 0 dispwin_get_ramdac called Getting gamma using Randr 1.2 dispwin_get_ramdac returning OK Saved original VideoLUT new_dispwin: return sucessfully Verify: '/usr/share/DisplayCAL/test.cal' IS loaded (discrepancy 0.0%) About to destroy dispwin object dispwin_del called dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK dispwin_set_ramdac called Setting gamma using Randr 1.2 dispwin_set_ramdac returning OK Restored original ramdac About to close
display
finishedBtw, the gui failure is also a bit elusive. It is not deterministic. It happens if I try a few times, which makes me think if it’s some race condition or other non-deterministic behaviour. Right now, the GUI is open, the screen is washed out, dispwin verify works. None of the controls in the gui work. If there is anything I can do to capture more information, please let me know.
2017-08-15 at 22:42 #8407What’s the output of
dispwin -dcc:? -?anddispcal -dcc:? -?2017-08-15 at 23:03 #8408That just prints help usage message. Is that the right syntax ?
Edit: Also says ** No ChromCasts found **
-
This reply was modified 8 years, 9 months ago by
finknottle.
2017-08-15 at 23:16 #8411I tried dispcal -d 1, which generates a segmentation fault. dispwin -d 1 generates patches. Attaching crash log.
Crash log at https://www.dropbox.com/s/qbwgdqvlwl177s0/_usr_bin_dispcal.1000.crash?dl=0
-
This reply was modified 8 years, 9 months ago by
finknottle.
-
This reply was modified 8 years, 9 months ago by
-
AuthorPosts