Comment 6 for bug 486944

Hmm, I didn't appear to be notified of your replies, so didn't notice them until now.

It's looking very much like schroot is not being run with full effective root permissions, despite being correctly setuid-root as intended. Are you using anything which could override this? For example, mandatory access controls as provided by SELinux or AppArmor. TTBOMK we aren't in the SELinux policy, so this could be a source of privilege restriction. If this is the case, then this needs sorting out with the SELinux people (I haven't got the knowledge to help here, sorry).

Regards,
Roger