The only difference is Distrobox is more agnostic and will create .desktop files for containers and applications installed in them automatically. Toolbx you need to make the .desktop manually.
Consider immutable, I use ublue-kinoite (fedora spin ‘with batteries’) and use a distrobox Arch for the AUR and development, best of both worlds, rock stable main OS, cutting edge rolling release as needed. I’ve been very happy, and if you’re using for uni and work, reliability should be a consideration.
That’s not how it works. The second bare double-quote closes the first one regardless of how it is nested in a string. The middle pair of double-quotes would need to be escaped. Also, single-quotes cannot be escaped in this way.
The only place I can think of where nested double quotes do work is in subshells
This is because the subshell is interpreted before the outer logic, so during interpretation of the outer logic there is never a nested double quote, just the stdout of the subshell.
These things are sometimes difficult to grok, and even more common, difficult to spot with human eyes. Best to use shellcheck, which will surely help you get better at shell scripting.
Not at my computer so I can’t double check, but I believe you can replace the outer double quotes with single quotes. I’d also remove the spaces before and after the equal sign for the alias. I don’t know about fish but I know bash doesn’t like when you add spaces there.
Manjaro. I’ve attempted to use Manjaro a few different times, and outside of a VM it just didn’t work properly; on my laptop it would boot loop for reasons I don’t understand, it had poor hardware support and optimization on a Raspberry Pi, and it didn’t last long on my desktop. It’s had its chances, I’m done trying.
I really did not hitch horses with Pop!_OS, and it’s almost entirely because Pop!_OS started at Gnome and kept fucking going. Just thinking about the two miserable weeks I spent trying to get Gnome to do anything is making me physically angry. Words like disobedient and belligerent come to mind when I think of what it’s like to use Pop!_OS. Linux Mint is designed to feel familiar to anyone coming from Windows. Pop!_OS feels like it’s designed to be the opposite of that, it deliberately doesn’t work the way you think it does. YOU have to conform to IT. And I FUCKING hate it. It is never welcome on my hardware ever again.
im pretty sure you can get by pretty well without the terminal, for the most part. although, it is arch based, and its kind of the point. no distro is for everyone.
its besides the point, but why dont u like the terminal?
For me personally: Something like Arch. I want to spend as little time as possible on installation and configuration, and I don’t want to have to read update notes or break my system. But I get that it’s great for some people, and their wiki is just next level!
In general: Ubuntu. It feels like I read something about Canonical causing trouble every other week, and don’t even get me started on snaps!
Just to share my experience, I used the archinstall script so I have btrfs snapshots and didnt have to put together everything myself. I almost update every day because it gives me a dopamine hit and nothing has broken in the last year and a half since I switched off Windows. I’ve had fewer issues than when I tried to Fedora with the Nvidia card I already owned. It could definitely be a case of ‘works on my machine’ but I think reports of Arch breakages are overblown.
I had to hold off on updating my Debian 12 server due to a severe bug just a month or two ago.
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.
Comm: wpa_supplicant being the wifi function makes me suspicious of your wifi hardware as well before I saw the rest of your post. I’ve had the best success with PCIe based wifi cards (if this is a desktop pc)
Agreed, this wifi stick was mega cheap on AliExpress so I went for it. I may take a look at the PCB in detail if removing it restores order to my PC. Yes, desktop PC (still hanging on to 2012 hardware woohoo!)
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.