We're seeing this error in Samigo after 10.5 and I believe it's related to recent fixes for 10.5 an incorrect assumptions about the question pool.
There now only 2 places were false is returned from populateItemBean and the second results in a separate stack trace in the log so it has to be this one.
This is the code that is being used to determine if it's a question pool, but it already knows if it's a question pool.
// Check permissions: if sequence is null, the item is *not* in a pool
if (itemfacade.getSequence() != null)
I believe it's checking individual questions in the pool to see if they have a sequence as well as the pool, and when the individual questions do, and the user doesn't have access to edit they're getting an error.
I don't know if this should be critical or blocker, I guess it would depend on how many people hit it but the fix seems straightforward.
org.sakaiproject.portal.api.PortalHandlerException: org.sakaiproject.tool.api.ToolException: javax.servlet.ServletException: failed to populateItemBean.
caused by: org.sakaiproject.tool.api.ToolException: javax.servlet.ServletException: failed to populateItemBean.
caused by: javax.servlet.ServletException: failed to populateItemBean.
caused by: java.lang.RuntimeException: failed to populateItemBean.