Comment # 3 on bug 953651 from Jason Mader

(In reply to Dominique Leuenberger from comment #1)
> Probably an error in the apparmor profile: do you have apparmor
> enabled/loaded?
> 
> > systemctl status apparmor

apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/boot.apparmor)
   Active: active (exited) since Wed 2015-11-04 16:05:42 EST; 22min ago
  Process: 811 ExecStart=/etc/init.d/boot.apparmor start (code=exited,
status=0/SUCCESS)

Nov 04 16:05:42 linux-x56z boot.apparmor[811]: Starting AppArmor ..done

> if you have it enabled - could you disable it and verify if this makes the
> colord error go away (that would be a clear confirmation)
> 
> WARNING: disabling apparmor and re-enabling it leaves all running process
> unprotected! You'd need to restart your services or, easier, your system

confirmed. with apparmor disabled, the warning doesn���t appear.