Comment 12 for bug 1863613

I have the same problem after upgrading from Fedora 31 to 32.

I strace'd the process and found that one of the last things before exit was:
```
getresuid([1000], [1000], [1000]) = 0
getresgid([1000], [1000], [1000]) = 0
write(2, "need to run as root or suid", 27need to run as root or suid) = 27
```

Sure enough, I ran it as root, it did something to spin my fans for a bit, and then successfully launched. It's the Spotify binary itself that is checking if it's running as root and then bailing.

Subsequent launches not as root still have the same problem, so it wasn't a one-time setup operation.

I happen to have another Fedora 32 machine where I had install Spotify via flatpak. On that one I can see that the getresuid()/getresgid() calls return root even though I launched non-privileged.

Is snap supposed to be lying such that these syscalls return that user and group are root?