@Olli: We do have logging in ~/.cache/upstart/unity8.log which currently is the catch all logfile. I don't think we can enabling anything more than what the app is printing itself (which will end up in unity8.log)
@Jono: Please attach ~/.cache/ustart/unity8.log. Also, please note down which applications show this issue and if possible steps to trigger this issue.
@Kevin: No... I don't think those bugs have anything in common.
Also, Unity8 is most likely the wrong component for this bug. As qmlscene spinning the CPU indicates most likely a bug in an application. There is a chance that the QPA plugin is causing this but somewhat unlikely as we probably would see it waaay more often.
@Olli: We do have logging in ~/.cache/ upstart/ unity8. log which currently is the catch all logfile. I don't think we can enabling anything more than what the app is printing itself (which will end up in unity8.log)
@Jono: Please attach ~/.cache/ ustart/ unity8. log. Also, please note down which applications show this issue and if possible steps to trigger this issue.
@Kevin: No... I don't think those bugs have anything in common.
Also, Unity8 is most likely the wrong component for this bug. As qmlscene spinning the CPU indicates most likely a bug in an application. There is a chance that the QPA plugin is causing this but somewhat unlikely as we probably would see it waaay more often.