That command won't work because the lrrmjddkkn problem stems from the redirection to a file. Running curl as root doesn't elevate the shell and therefore won't give you write access to /usr/share.

I don't understand why developers don't just use the output flag of curl instead of using file redirections like this. sudo curl -o [...] would've prevented all of that, instead of relying on someone being logged in as root (which is a terrible security practice I thought we as Linux users have been over already). I have to replace I/O redirections with sudo tee way too often, and it's impossible for any Linux beginner to understand what's going on here.