Is anyone else suddenly having problems with their Distroboxes? I have Signal set up in a Mint distrobox and it was working fine. I updated the distrobox and Signal stopped working. The distrobox seems fine. Signal just doesn’t run any more.
I created a simple kali distrobox with all defaults in Kontainer and I can’t even open a Terminal in it once it’s created. If I try updating it from Kontainer, the process seems to die. I can’t even enter the distrobox from Bazzite’s terminal with:
distrobox enter kalidistrobox
(that’s the name I gave it). That gives me:
Starting container... Error: An error occurred
Similar problems with a Mint distrobox. I tried creating a similar container from Terminal, but have no experience with that and it also won’t run.
EDIT: I’ve created an issue for this over on the Bazzite github page. But, I’m now leaning to the problem being a combination of a Distrobox issue and an actual Signal issue. Links to those problems are in that Bazzite issue:
Well, I’ll do you one even better and more stable solution, VM. Can install, update, whatever windows app. From my point of view, that is the problem, it being install. A perfect solution would be runnable. And outside maybe a few quirks, the bazaar version works perfectly. It’s not like the Desktop version is any more safe than the other one. Both use a server to keep your messages, and while not with openly shared key, any agency can just get it with a simple warrant.
Also, from user side, it allows the encrytion of the whole VM drive. And with a single button press, everything will be gone, like it never existed.
Now, as for the Kontainer. As far as I remember, it does not allow you to create new paths. So if it fails to install, cause it does not have access to some new files or paths, it is probably simpler to make a new Kontainer.