Downloaded, non-compiled copies of the randomizer cannot run on Ubuntu, due to how AppArmor is configured on that distro. This is a recent-ish change that will affect all versions of Ubuntu going forward, and, from what I understand, it has an effect on all Electron programs.
This will fail silently if the user runs Gui.py - https://discord.com/channels/274180765816848384/476723801032491008/1488733159968473231
If the user runs Cli.py, it's more verbose - https://discord.com/channels/274180765816848384/476723801032491008/1456469826473038017
There are two workarounds. One, the user can temporarily revert the security restrictions by entering
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
They can then run the randomizer, generate their seed, and then re-enable the restrictions by entering
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=1
This workaround comes from electron/electron#42510 (comment)
As this restriction was originally put in place to stop programs from using privilege escalation exploits (per https://ubuntu.com/blog/ubuntu-23-10-restricted-unprivileged-user-namespaces ), this workaround is probably not ideal.
The other workaround is for the user to add an AppArmor profile for rando themselves, which is definitely asking too much of the average user.
The ideal solution, per flagrama, would be for the randomizer to provide the AppArmor profile.
My recent conversation with flagrama where I personally had this issue is here https://discord.com/channels/274180765816848384/476723801032491008/1488767728243310683
Downloaded, non-compiled copies of the randomizer cannot run on Ubuntu, due to how AppArmor is configured on that distro. This is a recent-ish change that will affect all versions of Ubuntu going forward, and, from what I understand, it has an effect on all Electron programs.
This will fail silently if the user runs Gui.py - https://discord.com/channels/274180765816848384/476723801032491008/1488733159968473231
If the user runs Cli.py, it's more verbose - https://discord.com/channels/274180765816848384/476723801032491008/1456469826473038017
There are two workarounds. One, the user can temporarily revert the security restrictions by entering
They can then run the randomizer, generate their seed, and then re-enable the restrictions by entering
This workaround comes from electron/electron#42510 (comment)
As this restriction was originally put in place to stop programs from using privilege escalation exploits (per https://ubuntu.com/blog/ubuntu-23-10-restricted-unprivileged-user-namespaces ), this workaround is probably not ideal.
The other workaround is for the user to add an AppArmor profile for rando themselves, which is definitely asking too much of the average user.
The ideal solution, per flagrama, would be for the randomizer to provide the AppArmor profile.
My recent conversation with flagrama where I personally had this issue is here https://discord.com/channels/274180765816848384/476723801032491008/1488767728243310683