

TMDB — themoviedb (dot) com
TMDB — themoviedb (dot) com
I did seem to gain around 10s in a compilation workload that takes just under 2 minutes (after the switch), but I didn’t perform any actual benchmark
Is there any meaningful difference between installing CachyOS and installing Arch but setong up the CachyOS repositories and using CachyOS’ kernel? I did the latter, and things seem to work fine
Or both! Debian on my server, arch on my desktop, btw
If the time is off by that much after being powered off, this tells me two things:
An incorrect clock can absolutely cause network issues, so I would bet that’s what is causing you trouble
Why are you using networkd instead of networkmanager on a desktop?
What a weird question. Networkd works anywhere systemd works, why whould desktops be any different.
It’s the same as asking someone “why are you using systemd-boot instead of grub?” Because I like systemd boot better and it’s easier to configure. Same with networkd, configuration is stupid simple, I have installed it on my work machine even.
As for op: since you can manually ping ip addresses and the issue seems to be time-based, could it be that your machine is somehow not renegotiating a dhcp lease?
TempleOS
I know looking at it from the outside can look like throwing a fit, but as a software dev I can assure you our professional life is a constellation of papercuts and stumbling blocks on the best days. It is a fun job in many ways but it’s by its nature extremely frustrating at times. For professionals, the inherent frustrations are just the tip of the proverbial iceberg, the rest of the iceberg being induced frustrations due to work environment causes of various nature, and a lot of devs who also develop stuff in their own free time do it to regain a sense of purpose and control.
If these kinda hiccups keep happening even outside the day job of a developer, it is absolutely understandable that the reaction is simply to cut the bullshit rather than grabbing yet another shovel to shovel away the shit you’ve been covered with this time.
Ultimately, the cost benefit analysis for keeping uBOL hosted on mozilla’s platform became skewed on the cost side and the additional expense is not one that gorhill can or wants to afford.
So, yeah, it’s not a hissy fit.
+1. Arch is super easy to install, just open the install guide on the wiki and do what it says.
It’s also really stable nowadays, I can’t actually remember the last time something broke.
As a counterpoint, on ubuntu I constantly had weird issues where the system would change something apparently on its own. Like the key repeat resetting every so often (I mean multiple times an hour), weirdness with graphic drivers, and so on.
That said, I also appreciate debian for server usage. Getting security updates only can be desirable for something that should be little more than an appliance. Doing a dist upgrade scares the shit out of me though, while on arch that’s not even close to a concern.
I think it’s possible that the filesystem ran out of inodes, so even though there is space on disk, there is no space in the filesystem metadata to store new files.
Now, I don’t know off the top of my head how to check this, but I assume the answer is on the internet somewhere (am on phone and can’t help much more than this, sorry)
What is this mysterious device that requires specific libraries and kernel modules? So I can state the fuck away from the device and the brand
They are yeah, but in that scenario you would also not have a window decoration with a close button, so I assumed the OP meant maximized :P
Reread the OP. They say:
not on GNOME, because you have a panel at the top
And
when usign GTK apps on those [non-GNOME] desktops
So you would not “access the controls above the app”, because having controls above the app is not covered by this scenario.
The scenario is:
Which makes the close button be in the corner of the screen, but without actually extending to it.
On topic: never knew this was a problem, guess I got spoiled by the Qt environment
Not necessarily. Timestamps, file paths, and other environment metadata can easily sneak into an executable and make a program not build reproducibly