I use Linux MX on my gaming desktop and LMDE on my laptop. I also have an encrypted LMDE VM that I use for some working stuff, since I have to use Windows on my company PC (but we’re allowed to have Virtualbox on it).
The desktop is pretty new, I built it a month ago after almost 10 years, it’s i9 and rtx 4070. The laptop is several years old (HP spectre), but since the previous one gave me so many headaches with nvidia optimus, I decided to go full Intel, I’m happy I did because I had no problems with it whatsoever, Intel only on laptops for me going on.
Turning AA off for fonts solved the missing characters, downside it doesn’t look very good. I still have glitchy artefacts in some menus and the package manager doesn’t display any text for buttons which is a bit problematic. Guessing disabling some more AA settings would remove more of the problems. But it doesn’t solve my main problem - why did AA break in the first place
That is helpful, I’m not sure what I’m looking for yet though. But another comment lead me into antialiasing and this line in the history seems plausible. install -y /tmp/zenity/nobara-amdgpu-config/fedora-amdgpu-pro/packages/amdamf-pro-runtime-5.4.3-4.fc37.x86_64.rpm /tmp/zenity/nobara-amdgpu-config/fedora-amdgpu-pro/packages/amd-gpu | 2023-04-25 20:11 | I, O | 11
Undo didn’t work though:
sudo dnf history undo 11
Error: The following problems occurred while running a transaction:
Cannot find rpm nevra “amd-gpu-firmware-20230404-149.fc37.noarch”.
So I made a rollback to my last know stable point: sudo dnf history rollback 2
It didn’t exactly workout either unfortunately:
Transaction history is incomplete, before 73.
ransaction history is incomplete, before 72.
Transaction history is incomplete, after 71.
Transaction history is incomplete, before 61.
Transaction history is incomplete, after 60.
Transaction history is incomplete, before 8.
Transaction history is incomplete, before 7.
Transaction history is incomplete, after 6.
Error: The following problems occurred while running a transaction:
Cannot find rpm nevra “ImageMagick-c+±1:6.9.12.82-1.fc37.x86_64”.
… many lines more about pkgs not found
I’ll do a reboot and see what actually took effect. Atleast I’m learning something, maybe I should do all my upgrades via dnf instead of the manager in the future, easier to know whats going on.
Most services just need the init system to start, stop and monitor them. There’s no special integration needed for each of them beyond running a command, monitoring the PID, and killing the PID when it’s time to stop.
If you mean the special integration of docker and podman with systemd, first of all that’s only required in rootless mode and not everybody runs rootless (most users probably run root docker). In rootless mode you have to manage each container individually as if it were a standalone service instead of just managing docker. Basically you have to integrate each container into the init system, whatever that is. There are some tools that make it easier to with podman+systemd because they write the systemd units for you but you can do it with any init system. The distro mostly doesn’t care because you have to do the work not them.
It looks nice in the screenshots, but it charges $40 for “premium” which is pretty much the same as the free one, besides it having a few extra themes, and some “professional creative software” and stuff (free software that they are bundling in, and acting as if it’s exclusive to Zorin or something)
They also have an IT management tool called Zorin Grid that has said “coming soon” for years now
I tried nix actually. Personally, I think it would make a great server os, but I do not enjoy it as a daily driver. I didn’t like the fact that I was forced to install everything through nix and couldn’t compile software from source.
It’s great to see that Pipewire has reached this milestone. Personally I’ve been using it since 0.3.35 for very basic audio needs and it’s been a very smooth transition. After installation I never had to tinker with it anymore. “It just works”^TM^
before you change anything it would be good to use dd and save the whole drive to a bigger drive or maybe compress it with gzip while using dd to save it to a slightly smaller one. That takes a very long time, but gives you the ability to start over with your recovery. Only do that if it’s worth to wait several hours.
photorec can also recover some files by looking at the raw data still there, if all else fails.
Your “of” can also just be a regular file if that’s easier to work with vs needing to create a new partition for the copy.
I’ll also say you might want to use the block size parameter “bs=” on “dd” to speed things up, especially if you are using fast storage. Using “dd” with “bs=1G” will speed things up tremendously if you have at least >1GB of RAM.
this clones one parition to another which is fine if you have free partition with enough space lying around. My code was for taking compressed backup of the partition to be restored later if needed. Its less convenient but doesnt require as much space nor does it require an entire partition
depends on what you mean by “broken”. If broken means has bad sector or other hardware issue, then yes OP should transfer data to healthy partition and work from there. though it certainly won’t hurt if he attempted to recover data from broken partition (worst the HD dies and OP restore the backup on healthy HD) However he said “i broke my partition” which make me think its software issue, not hardware. in which case, would be faster to recover data directly after taking backup
That’s what people always underestimate about data recovery jobs: you need lots of space. One copy for safekeeping. One to work on. One disk of the same size you store recovered files on.
Whenever friends or family ask me to look at a disk I always tell them to give me the disk and two new ones of the same or greater capacity and I’ll give it a shot. Usually they discover the data isn’t that important after all. If it is I have all I need.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.