It's true that based on the bug report linked in the post, the application bundle is modified by a 3rd party installer running as root. I still think Chrome sho

It's true that based on the bug report linked in the post, the application bundle is modified by a 3rd party installer running as root. I still think Chrome should correctly handle the permissions problem with a warning or asking for root privileges to fix it, but I've updated the post to point out Chrome itself is not the origin of the problem.