

What laptop model is it?
Can you check if the hardware or specific audio device it uses is supported on https://linux-hardware.org/ ?
I used to have a laptop that had lacked support for it’s builtin speakers on Linux, but bluetooth would work fine.


What laptop model is it?
Can you check if the hardware or specific audio device it uses is supported on https://linux-hardware.org/ ?
I used to have a laptop that had lacked support for it’s builtin speakers on Linux, but bluetooth would work fine.


See my other comment: https://programming.dev/post/53544261/24909721


The point of mit is to get the licensed thing used as widely as possible. It breaks down any barriers to use
There are no barriers to use, except that you have to share the source code back, and give users the option to modify it. If you use it without modifyiing it, you can just point users to the existing public code.
The only barrier to use is that Apple disallows (A)GPL related libraries in any of their code, published through their main distribution channels to their platforms (mainly talking about apple app store here).
https://www.zdnet.com/article/how-to-avoid-public-gpl-floggings-on-apples-app-store/
But this is ultimately on Apple for not giving users the needed amount of control over their devices to comply with the license. This annoyingly common rhetoric that the GPL itself is a “barrier” or “restrictive” is just blaming the wrong party.
Now, even though I’m more in favor of copyleft, I can understand with the decision to license software or libraries permissively in order to be able to distribute them through the App Store.
gpl licensed is a game engine you want people to be able to freely use and modify but never make secret changes to sell
This is tricky because the GPL is fairly aggressive, and may require the entire game to be open sourced if it’s distributed as one bundle. LGPL doesn’t fight as hard for users freedoms, but also has some similar issues. Most game developers don’t want to open source their games, so I think a permissive license is probably the easiest choice for a game engine.


Yes. Under the hood, gnome controls the power profiles daemon.
You can configure it from the cli via powerprofilesctl.
powerprofilesctl get gets the currently active mode. powerprofilesctl set performance set’s it to performance mode.
There are three modes: ‘power-saver’, ‘balanced’, ‘performance’
I used to use innoextract to extract the launchers, and the the system wine to run it. Although sometimes I have to run extra installers that put dlls in the right spots.
You should probably just run the installer in lutris (which ships a proton distributution) or bottles.
Edit: I can’t read smh my head.
Check this out: https://github.com/lutris/docs/blob/2b116519c5b67254733234f36ab33a60f14f1358/WineDependencies.md
TeamPCP is very interesting, since they actually reused an open source secrets scanner to find secrets:
https://github.com/trufflesecurity/trufflehog
So if you wanted to know, I’d start by looking there.


I am trying to use nix and firejail only, but it is pretty rough and barely documented which is kinda insane as firejail is THE tool. Unlike crabjail, bubblejail and what else is out there
I was investigating sandboxing with Nix. Here is a dump of my saved notes:
https://todo.sr.ht/~alexdavid/jail.nix
Projects to sandbox AI agents:
https://github.com/archie-judd/agent-sandbox.nix
https://github.com/myme/jaillm/blob/main/flake.nix
https://github.com/gfauredev/nix-agents-jail
https://github.com/azuwis/fence-agent.nix
github.com/kohane27/jailed-ai-agents/blob/main/llm.sh
Someone told me that if you take these things and then replace the entrypoint with bash, you get a sandboxed shell environment


Not everybody does. It’s just sometimes.


If the tarball was dynamically linked against specific distro’s libraries though, then it wouldn’t work on all distros.
They also often provide RPM packages for Red Hat systems. Not always though, and I use Arch (btw) anyways.


snap is likely the most secure by avoiding user namespaces, using AppArmor only and thus being very flexible (also for use for kernels, drivers, browsers …) but it is proprietary, nobody likes it and Canonical doesnt wanna stop somehow.
Snap does seem to support user namespaces. Although I want to comment that user namespaces are not universally insecure. When an application is confined within a user namespace, seccomp rules restrict it from being able to interact with the user namespaces subsystem, walling it off from the increased attack surface.


distrobox/toolbox
Distrobox excels for when you need some proprietary tool that ships it’s packages as a repo for Ubuntu but not much else. You spin up a distrobox for Cisco Packet Tracer, or VSCode (the proprietary microsoft one, not Arch’s Code-OSS and Unity.
Then, once you’re done, you can just delete it all.


nix doesnt have any of these, but sandboxing is hard, there is either stable or unstable, changing and configuring things is very complex. Likely no official packages. Still the method I prefer.
Nix is what I use, and it was frustrating to have to hack a lot of it into place, but I feel like it has the most potential. Unfortunately the flakes nonflakes split, in combination with the split of “distros” like determinate nix, flox, and so on, and the governance concerns really hold it back. It has horrific documentation, for the most part caused by the above (flakes are “experimental” and so can’t be included in official docs), and it is frustrating the lengths I have to go to to make stuff work that should be easy.
For example, GPU acceleration of Nix packaged apps on non Nixos systems. I figured out how to do it:
(config.lib.nixGL.wrappers.mesa pkgs.gzdoom)
But I think it’s just straight up impossible to do this via imperative package installs, outside of home manager. And it’s kind off important if you want any GUI app whatsoever to work.
But now that I have it working, I use Nixpkgs exclusively and am able to avoid the AUR entirely. To me, the AUR is a last resort, only for something like say, system level printer drivers (thankfully I’ve never needed to install anything to get printers to work). By ensuring that I only use the AUR once in a blue moon, I can make sure that I actually review the PKGBUILD when using it.


They are probably referring to the way that snap, flatpak, and distrobox are available as official packages in most linux distro’s repositories, whereas nix isn’t. I have encountered this frustration for sure. Debian and Arch provide nix packages, but many other distros don’t.
In addition to this, nix requires manual setup if you install it from the repos, which is annoying. And then you have to do further manual setup to enable flakes, and then you have to figure out how to install packages and it’s not fun.
So the main way people install nix is via the curl | bash scripts various “distros” of Nix provide.
lmao. I hate takes like this.
It’s not about making the website impossible to get to, it’s about making the website more difficult and annoying to get to than an alternative productive activity/site.
Part of making it difficult to get to is technical.


Woops, a duplicate?


Did you reboot?
It could be that a system service was installed, and activated. This service could stay running even after the packages are removed, since the programs would remain in memory.


Absolutely, this is an admirable project.
But the first thing you should know is that QubeOS is not based on Linux, but is actually a different kernel, Xen. The Xen kernel virtualizes Linux, and all Linux runs under it.
Networking and hardware access is done by certain VM’s having devices (like the ethernet card or monitor/keyboard) passed through them, where Linux then handles the hardware access with it’s drivers.
This is important to understand that, because QubeOS is not a Linux distro. Really, it’s just that they selected Linux (it was either Debian or Fedora IIRC) as their management VMs.
But once you understand that it’s absolutely feasible to adjust the VM’s. It’s probably easier to modify a LInux distro (or create your own) and use that for all the VM’s, and then to reuse Qube’s management related software. That way you could do something like ship a version of debian that disables non-free software and firmware in the debian repos. Doing that is probably easier than creating your own distro entirely from scratch.
Another interesting thing about Qubes is that you are not limited to Linux. Of course, using Linux will be easiest. But the management VM’s can technically be any OS that supports it.


Yes this is the best way.
On Linux I’ve never had to install drivers for any printers, it comes with a “generic” driver that works for a ton of brands,
I used to use Arch + KDE on a device with only 32 gb of storage space. I used BTRFS and transparent compression, and I got the actual Arch Linux install compressed down into 6 gb (where it would have been 10 gb uncompressed).