I understand that, it’s definitely more of a headache than having a native package, but it is the next best thing you can do aside from waiting for the dev or someone else to package it for your distro of choice (you might be more lucky if you’re on an Arch based system, I’m sure an AUR package will be made if it hasn’t been done already).
The distrobox setup itself isn’t really that crazy either, once you have everything ready you’ll be able to run OBS as if it was installed on your host system since you can export the programs in your containers to have a desktop entry in your DE.
Now I was trying to get all that up and running, but I’m facing issues in the installation of the plugin and I don’t know what’s causing that exactly, it may be a mismatch in the distro I chose and which one the package was actually made for, I’ll report back if I find a solution, in the meantime here’s what I did:
<span style="font-style:italic;color:#969896;">## Creating the container
</span><span style="color:#323232;">distrobox create
</span><span style="color:#323232;"> --image quay.io/toolbx-images/ubuntu-toolbox:latest
</span><span style="color:#323232;"> --name toolbox-ubuntu
</span><span style="color:#323232;"> --home ~/.local/share/box-homes/Toolbox-Ubuntu
</span><span style="color:#323232;">distrobox enter toolbox-ubuntu
</span><span style="color:#323232;">
</span><span style="font-style:italic;color:#969896;">## Installing OBS Studio
</span><span style="color:#323232;">sudo apt update </span><span style="font-weight:bold;color:#a71d5d;">&</span><span style="color:#323232;">amp;</span><span style="font-weight:bold;color:#a71d5d;">&</span><span style="color:#323232;">amp</span><span style="font-weight:bold;color:#a71d5d;">; </span><span style="color:#323232;">sudo apt upgrade
</span><span style="color:#323232;">sudo apt install obs-studio
</span><span style="color:#323232;">qtwayland5 </span><span style="font-style:italic;color:#969896;"># to be able to launch OBS on my KDE Wayland
</span><span style="color:#323232;">
</span><span style="font-style:italic;color:#969896;">## Trying to install the plugin
</span><span style="color:#62a35c;">cd
</span><span style="color:#323232;">curl -O https://github.com/occ-ai/obs-localvocal/releases/download/0.0.5/obs-localvocal-0.0.5-x86_64-linux-gnu.deb
</span><span style="color:#323232;">sudo apt install ./obs-localvocal-0.0.5-x86_64-linux-gnu.deb </span><span style="font-style:italic;color:#969896;"># gives error, maybe not compatible with latest Ubuntu?
</span>
looking further into localvocal, its just captions and not translations, not like i got it working on a buntu variant either, currently trying to rip my hairs out with sayonari, it seems to support many languages, but the website for some reason is japanese only
i even followed tutorials but it just isnt working
i got the japanese one working, the REALLY stupid part about it was it needs chrome, im not talking chromium, it LITERALLY needs chrome to work, guess it uses some internal apis or something only chrome has
For near-guaranteed compatibility, there are dedicated manufacturers like System76 and Tuxedo. Framework also claims Linux compatibility but for set tested distros (Ubuntu and Fedora).
Generally, anything with Intel/AMD graphics and Intel Wifi is pretty much guaranteed to work in my experience. For laptops, high-DPI displays can be problematic but the fixes are on Wayland which is getting higher priority now.
To me, the big mistake both make is in the presumption the UI and utilities shipped with those platforms are why people use it. But no. Nobody uses MacOS because of its nifty calculator or the Finder. It’s the overall toolkit integration with apps. Not even look and feel. But consistency in use.
I don’t presume to know why others choose to use anything. But MacOS is highly consistent across apps. Dialog boxes, text input forms, file browsing, hot keys, all the same across applications.
take any distribution that someone at or close to the library is comfortable with, e.g popular Ubuntu or Debian,
setup a user profile that fits the need of the average library user, e.g Firefox with as a start page the library website
make sure the library card system do work
copy /home/thatuser directory somewhere, e.g /root/thatuserunmodified and insure permissions make it unmodifiable
add a cron task so that every evening 1h after the library close any thatuser session is terminated, /home/thatuser gets deleted, copy the /root/thatuserunmodified to /home/thatuser and fixer permission
assuming it’s fast enough (I bet it’s take 1min at most as /home/thatuser would be mostly empty) I’d do the process after each logout so that each new visitor gets a fresh session, no downloads from previous users, history, bookmarks, etc. Only what the library consider useful.
That’s it. This way one can still let the OS do it’s updates but the user experience is consistent.
I’ve not used either, just look on as a curious spectator, I’ve yet to leave the more idiot proof distros of mint and fedora. What makes it so hard to deal with vs nix?
If you want, here’s my config. Feel free to fork it.
github.com/harryprayiv/nix-config (you’ll have the most luck with the “plutus_vm” machine config output in my flake at first since the main output in my config is somewhat obscured by encryption).
I also have a Nix-Darwin config that I haven’t consolidated into my main one:
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.