I used to be in a similar position as you. I ditched Windows about 1.5 years ago, and I hopped around several distros for a while before settling on Linux Mint. About 2 months ago, i decided that I wanted to try out something new, not because Linux Mint wasn’t working for me, but just to see if there was something else that would be fun to learn about Linux. Today, I use Arch, and my DE is basically the Linux Mint Cinnamon DE.
EndeavourOS is a pretty decent setup, it has been working well for me so far, and I prefer Arch-based distros because of how quickly Linux has been moving.
Manjaro have let their SSL cert problem happen twice since I’ve been in the loop, and they were unintentionally DDOSing the AUR for a while.
Yes. I know Manjaro got bad press several times, about their SSL cert and about firing their treasurer but as a Linux distribution Manjaro is pretty decent for the average user, in my opinion.
SSL cert expiring stopped access to updates. That’s not just bad press, that’s poor form overall, especially for an Arch-based distro. Even worse, this happened while certbot exists, so there’s no excuse. It tells me they are less reliable as a distro, especially to have let it happen twice.
None of those people have a slightest clue. Your options really are: ubuntu vanilla and maybe pop os.
Everything else will very quickly require you to read through some obscure docs and bash your head against the terminal.
Vanilla Ubuntu, not kubuntu/xubuntu/whateverbuntu is the only polished and documented distro. After a year or two of that you’ll be ready to consider this “what distro” question.
In my experience, any HDMI’s or Display Ports plugged into my GPU have terrible performance on Wayland while working perfectly on X11, so it seems there are still problems. Though tbf X11 doesn’t work at all with HDMI’s plugged into my motherboard so it could be a hardware issue? I have a 11 year old motherboard so idk.
If you’re mixing a dedicated GPU and onboard graphics you need to set the dedicated GPU as primary somewhere, otherwise all screens get rendered on the onboard and “reverse PRIME’d” to the dedi GPU outputs.
I’ll see if I can find the snippet that fixed this for me.
Way back at the dawn of time, there was a regular issue with low quality applications that would run XGrabKeyboard() (or XGrabPointer()), and then get stuck without releasing it again. If you can, try to log in over the network from another machine and kill application processes one by one until it releases? It’s most likely the video game (or library used by it) that has gotten stuck.
Are you sure its a similar issue? Because usually closing the window actually doesn’t solve it, as then reopening another X11/XWayland window will still not register keyboard presses. I am adding some more info to the post right now.
I’m not sure, there can always be other issues. But note that closing the window is not the same as terminating the application. When you close the window, the application gets a signal that it usually handles as cleaning up and shutting down. But if it is hanging, that task is not performed and resources are still held.
I like Garuda. I use the dragonized theme and it makes it look similar to mac OS. IMO it’s as easy to use as any other justworks distro but is far prettier
A few years ago I was having obscure audio problems on Ubuntu so I tried replacing pulseaudio with pipewire. I was feeling pretty cocky with using the package manager so I tried
sudo apt install pipewire
Installed successfully, realized nothing changed, figured maybe I had to get rid of pulseaudio to make it stick.
sudo apt remove pulseaudio
Just two commands. Instant black screen, PC reboots into the terminal interface. No GUI. Rebooting again just brings me back to the terminal.
I fixed it eventually, but I’m really not very computer literate despite using Linux, so I was sweating bullets for a minute that I might have bricked it irreversibly or something.
I used to work at this place that had a gigantic QNX install. I don’t know if QNX that we used back then had any relation to q&x now They certainly don’t look very close.
It was in the '90s and they had it set up so that particular nodes handled particular jobs. One node to handle boot images and serve as a net boot provider, one node handled all of the arcnet to ethernet communication, one node handled all the serial to mainframe, a number of the nodes were main worker nodes that collected data and operated machinery and diverters. All of these primary systems were on upper-end 386s or 486s ,they all had local hard disks.
The last class of node they called slave nodes. They were mainly designed for user data ingest, data scanning stations, touch screen terminals, simple things that weren’t very high priority.
These nodes could have hard discs in them, and if they did, they would attempt to boot from them saving the net boot server a few cycles.
If for some reason they were unable to boot from their local hard drive, They would netboot format their local hard drive and rewrite their local file system.
If they were on able to rewrite their local file system they could still operate perfectly fine purely off the net boot. The Achilles heel of the system was that you had no idea that they had net booted unless you looked into the log files. If you boot it off your local hard drive of course your root file system would be on your local hard drive. If you had net booted, and it could not rebuild your local file system, your local root file / was actually the literal partition on the boot server. Because of the design of the network boot, nothing looked like it was remotely mounted.
SOP for problems on one of the slave nodes was to wipe the hard disk and reboot, in the process it would format the hard drive and either fix itself or show up as unreliable and you could then replace the disc or just leave the disc out of it. Of course If the local disk had failed and the box had already rebooted off netboot without a technician standing there to witness it, rm -Rf would wipe out the master boot node.
I wasn’t the one that wiped it, but I fully understand why the guy did.
Turns out we were on a really old version of QNX, we were kind of a remote warehouse mostly automated. They just shut us down for about a week. Flew a team out. Rebuilt the system from newer software, and setup backups.
I had a few programs for various things and one was simply an extension from the gnome extension manager. I updated it and my screen turned black and I couldn’t get it back. I had to revert to a previous version, then uninstall everything until I figurd out what caused it.
Have tried this myself and never had much luck trying to install nvim plugins via nix.
I’ve found the best way is to just use the plugin managers built for neovim, I’m not sure if this applies to all of them but lazy.nvim seems to be fairly declarative anyway, have home-manager map a directory to .config/nvim/ and away you go
As a side note though I think it is rather silly just how many different neovim package managers there are, which at the end of the day all do the same thing in very similar ways
Thanks for the feedback. I’m used to packer but it’s not maintained anymore so may be a good time to switch to lazy.
I’ll see if I can have it work in NixOS.
I have no idea, from what I gather there aren’t all the packages
I’m not sure what if anything installing them via nix does I’ve just come to the realisation it’s already declarative so why would people bother getting it working under nix
As other comments point out, they are usually not properly packaged through nix.
If you read the , for most plugins, the derivation just downloads the plugin, puts it to nix-store, and makes it available to the editor through environment variables. So it’s similar to the binary distributed software. Two most notable restrictions:
Nix is not aware of transient dependencies.
The plugin is not aware of the nix-store model.
So for plugins that don’t have external dependencies (or dependencies other than the “common” ones like python or sh that happen to be available), and that don’t interact with the filesystems, this approach would be fine, but the more complex ones would fail.
In your example, mason failed because of 1, home-manager wasn’t aware that the pip module is a transient dependency of this plugin; and treesitter failed because of 2, because it doesn’t know that nix-store is read-only and should be managed by nix.
There are no general solutions, but people may have nixified some plugins on a case-by-case basis. If you don’t want to spend a lot of time (and remember that it might be broken by the next plugin upgrade), as others have suggested, take the traditional plugin management approach. (Personally, I use LunarVim which uses Lazy.nvim and it’s been working fine.)
Back when I started using Linux, I really wanted something that was super different from windows (I used Gnome 3 for like 3 years). I decided one day to try out Fedora cause, hey, I can live on the bleeding edge.
Second day I had it installed, I was having issues with the audio. Decided to try reinstalling pulse. Apt autoremoved it and somehow completely nuked the entire GUI. Stuck in terminal mode, I found that I had no ethernet to connect to, nor could I figure out how to connect to a wifi network with a password or download packages to a USB. After a couple hours, I gave up, wiped the drive, and went back to Mint.
Same thing happened to me! I was on Ubuntu, trying to replace pulse and when it got removed instantly kicked me to the terminal. Eventually I fixed it but now I also just Mint, lol
I had issues with a new version of glibc that prevented me from working on music in Ardour on Manjaro. I then proceeded to force-downgrade glibc (in the hopes of letting me get back to work) and that broke sudo and some other things, which I found out after rebooting. That was an interesting learning experience. Now I snapshot before I do stupid stuff. :]
The first time I wanted to try Linux I did by installing elementary OS in dual boot mode (with windows) and everything went well, I played with it a bit and then I returned to Windows…
So, few days after that I realize that I have a lot of space in the Linux partition and I didn’t have plans to use it anymore so I go to drive’s & partition’s manager on windows to delete my elementary OS partition…
Oh Lord when I restarted my PC, grub was showing nonsenses and I couldn’t boot on windows again, I was in panic, I spent the rest of the day trying to fix grub to boot windows. At the end of the day I did it and save all my files and I uninstall grub properly, but what a day 😂
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.