Creating a different user account for it is out of the question btw, since you can still change the password for that user via the primary admin account.

First of all, if users have admin rights, nothing really prevents them to run that app. Even if you encrypt the app itself, they can just reinstall/replace it from standard repository.

Few ways this can be done:

1. If app needs internet connection, you may use firewall rules to block said connections, or even application firewall (Opensnitch). Create script which unloads said rules via su (create diffrent accounts with passwords the user must know) then runs app, and after closing app loads rules again. Users must not have admin rights or they can just unload fw rules.

2. Create encrypted container/directory, protected by password, and manually install said app under there (probably needs manual recompile of the app). Create script which asks password, unlocks the encrypted location, runs app, and locks container after use. Again, no admin rights for users or they just install same app from repositories.

3. Use apparmor or selinux to block said app. And again create script which by using su (create diffrent accounts with passwords the user must know) allows app via selinux/apparmor policies and runs app, and blocks it again afterwards. I repeat, users must not have admin rights or they can just unload those blocks.

What app it is?

EDIT: Clarification for su usage

To have user asked password before app can be done via su + sudo like this

• create user demouser
• give password of that user to end user
• give demouser sudo rights to run particular command as root without password (to unload fw rules, unload apparmor/selinux policy etc).

Did you upgrade its firmware?

Same workaround works here as with dirty frag. Just disable those kernel modules.

I would use Ubuntu LTS (free) or Redhat Enterprise Linux. If paying is not an option, some RHEL derivate would probably also work.

Care to elaborate how Ubuntu failed newest release?

Systemd has already won. So other init systems must adapt, and modify themselves to be compatible with systemd.

Here is how you can find it.

• First, in Steam, go to Settings -> Storage. There you can see the path for your library.
• Click … icon and select Browse Folder
• Open compactdata folder
• Open folder 3119540 (3119540 is Steam ID number for Scriptorium)
• Open folder pfx
• Open folder drive_c - this is emulated C drive of the game
• Most probably pictures are in users/steamuser folder somewhere

You are trying to install wrong versions of nvidia drivers and proton app.

For nvidia, use this https://linuxconfig.org/how-to-install-nvidia-drivers-on-ubuntu-26-04

For proton vpn, I assume you are trying to install app meant for 24.04. Do not do that, just search one for 26.04, if it is available.

I really hope Link is going to break some pots.

I am using Tiling Shell

https://extensions.gnome.org/extension/7065/tiling-shell/

Puppet / Foreman / Ansible for managing servers, and probably for workstations too.

Checkmk / Nagios / Zabbix for monitoring.

FreeIPA for user management.