Distrobox, by default, doesn’t provide much isolation/sandboxing - it’s main aim is desktop integration and filesystem transparency. So if you’re trying to use it for isolation, it’s a bad idea.
However, you can create a new container which will isolate your filesystem and prevent such conflicts, using the –unshare-devsys flag. (if you want FULL isolation though, use the –unshare-all flag).
Then enter the container and install the flatpak app as usual.
I just tested this on Fedora uBlue and an Arch container and it works fine, didn’t have to unmount anything.
I know that I’m not getting a full sandbox - that’s ok. Ultimately I’m trying to get bottles running in the hopes of getting a semi-contained environment for me to test out yabridge and getting reaper to load the vsts without crashing. (Reaper is the easy part, the plugins not so much…)
A modicum of isolation here (even if not complete) will help me figure things out. Obviously, if I need different kernel/flags the host will get it too.
If I unshare-devsys, will that disable audio? (I’m still trying to get a clear picture of what’s shared and what isn’t with distrobox/podman (with docker, it feels a bit more straightforward, but I’m not sure docker would be the right choice here…)
Audio works. Not sure how though, –unshare-devsys is supposed to not share the hosts devices, but I guess audio devices are an exception.
The full isolation flags are:
<span style="color:#323232;">--unshare-devsys: do not share host devices and sysfs dirs from host
</span><span style="color:#323232;">--unshare-ipc: do not share ipc namespace with host
</span><span style="color:#323232;">--unshare-netns: do not share the net namespace with host
</span><span style="color:#323232;">--unshare-process: do not share process namespace with host
</span><span style="color:#323232;">--unshare-all: activate all the unshare flags below
</span>
I don’t pretend to be an expert in this, and I also have no idea what the state machine looks like for unauthenticated WiFi, but my thinking on the call stack is either you were authenticated and the association with the AP dropped while sending a frame and puked, or it kicked it while attempting to authenticate to an AP, and I have no idea why a mutex would be taken, or to what, but it timed out apparently.
So why would this happen after a rebuild?
freak accident/timing thing.
I see multiple mt## modules loaded, and I’m suspecting while not looking it up that they are operating a MediaTek chip in that dongle, and are potentially conflicting.
lots of wifi devices I’ve seen recently have loaded firmware separately from driver from /use/lib(or lib64)/firmware and the version changed from before, and maybe needs updating now or you did it before or whatever.
I agree with others - I’d give you a fiver if it happens again without the adapter connected.
I think You’re right, it is a mediatek chip and I used to add the USB device id manually to load the module, but with nixos 23.11 it started working automatically. I’m also running a preemptable kernel… Probably related now that I think about it :P
I should track down the firmware, that was one of the things I was looking into when setting up the device id hack.
I think this happened once before after uptime of about a week… But I didn’t get any information from that crash. Also, I’m remembering that some configurations were failing to see this wifi device and falling back to wired so maybe this has been a hidden problem since the new nixos release…
Thanks to everyone for your thoughts, it’s very helpful.
I also started with LTS assuming they would be more usable, but the extremely outdated package have later driven me away from linux for a while.
Now I realize I can just run normal Ubuntu to get reasonably up-to-date packages. But I like the latest (non-graphical) software that is offered by fedora.
Just friggin’ install it. People spend so much time debating “which distro should I install”. Toss a dart at a board and pick one. Install it. Get your hands dirty and go. You’re not naming your first born you’re trying a new OS.
Artistic modelling i use Blender but Parametric modelling I used FreeCAD.
Despite having worked with CAD software, both were a little hard to wrap my head around initially, but I watched like 2 hours of video tutorials each and I figured it out enough for my needs.
Depends on what your using it for? For 3d printers I like FreeCAD. Though it has a bit of an initial learning curve. It has a lot of functionally. SolveSpace was pretty good but I had some trouble with fillets and things. Might have been user errors… I havent used blender much but heard its good for more artistic modeling for games and videos. Not sure if it would work good for 3d parts? Anyone use it for that?
X is old and very hard to maintain. A lot of rules about how displays work have changed drastically since X became a thing. X went along with most of those changes, which meant the introduction of more and more hacks to keep it running.
Over time X became worse and worse to work on and people realized that it’s easier to write something new from scratch instead of trying to fix the decade-old technical debt in X.
That new thing was Wayland and over time most if not all people that where interested in working on desktop compositing pivoted away from X.
Wayland (as it is always the case with new software of that size) didn’t hit the ground running. It had various issues at the beginning and also follows a different desig philosophy than X.
Despite a lot of issues being fixed some people are still very vocal about not wanting to use wayland for one reason or another. While some of those reasons are valid, most come from ignorance or laziness to adapt.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.