Comment 20 for bug 1562417

Revision history for this message
penalvch (penalvch) wrote :

Brad, as per #12, the libv4l2 error seems collateral damage from the libjpeg errors.

However, I'm still fishing around for which liibjpeg is being used here (or both?!), as each has a different upstream group to contact:
https://launchpad.net/ubuntu/+source/libjpeg8-empty
https://launchpad.net/ubuntu/+source/libjpeg-turbo

Hence, I'll mark this Triaged for now against Cheese (even though the evidence doesn't suggest cheese is the root cause) so the cheese specialist(s) may review faster then my digging reveals.