Any ideas how to fix this please?
I’ve tried different Nvidia drivers (361, 340), and the Open Source Nouveau driver. I’ve also tried the newer DisplayCal app (3.1.4) before reverting to the repo version, 3.1.0.
I’ve also tried different settings with DisplayCal, with no change. A brief Duck Duck Go search yeilds no useful results.
Using LM18 Cinnamon 64-bit, i5, 16gb Ram.
It seemed to work under LM17.3 fine. If the answer is to revert to 17.3 or I need to wade through endless code, I think I’d rather wait for a relevant LM update.
EDIT: I’ve also removed the config file (~/home/.config/dispcalGUI) which reset the app fine, but the end result is the same.
Otherwise any help would be much appreciated!
Thanks in advance.
Can you get the log file or possibly grep ~/.xsession-errors for problems?
Nope, nothing there. There are a stack load of errors though! I might do a fresh clean install of LM18, not just the system drive, but /home as well. Hopefully that’ll make a difference… Stand by…
Nope, that was a waste of time.
I’m picking this is an issue with LM18 as it’s predecessor worked fine.
So, the way I see it, I either have to wait for LM to supply an update, which could take months; or find another distro. Yeah, great. (Sarcasm)
The Ubuntu 16.04 as a desktop has been a little… rocky. 
This is Linux not Windows, one does not format and reinstall a different operating system because of some undiagnosed error.
Install 3.1.4 again, and if it happens again then upload or paste the DisplayCAL log.
Tools > Show log window.
Downloaded and installed several times, and ended with v3.1 from the repo.
To me it seems like it might be an upstream Ubuntu issue affecting 16.04, and thus LM18. I’ll revert to LM17.3 (Ubu 14.04) later on today as it worked prior to the LM18 upgrade. I’m of no mind to fault-find errant issues today. 
I don’t follow.
Why several times? Once is enough.
What is “3.1 from the repo”, is that 3.1.4? “? > About” contains the full version number.
But that’s not so important. Showing the log is the important thing.
Again, that is a Very Bad Idea. It is a waste of your time, and it does not help at all in finding the cause of the problem so that it can be fixed. By doing that, you are effectively shooting yourself in the foot.
Maybe. I guess it comes down to how much time one has to spend fault finding. Whether the quicker approach is the better one to use at the time.
I do understand the need to look into such issues for the benefit of the community generally, but since 16.04 is at its first point release and a Web search brings up nothing of note, might suggest this could be a long process to resolve, involving time that right now I just don’t have spare.
