 thanks @teward001 for the bug hunting (& subsequent frustration, hair-pulling etc)
 thank security team for indicating this is already fixed upstream but they're lazy as heck for getting it into the repos :P
 aka "overworked"
 so apparmor updates are low on their priority list >.>
 @guiverc but I HAVE confirmed a fix... sorta... for the error.  It requires fixing an apparmor bug first though
 and then applying an update before Upstream torbrowser-launcher accepts the patch
 but also, the problem is X abstractions weren't pulled in so it won't work without those ANYWAYS so
 *shrugs*
 :)   That's great news & explains the security team involvement in your prior messages (if you added detail to the bug report I've not viewed it yet)