deleted by creator

deleted by creator

deleted by creator

deleted by creator

Try playing games like Cyberpunk. I dare you :)

You are lucky if you can play without a crash for even one minute with that card. I am not exaggerating. Something is seriously messed up with the 20XX series.

Also Wayland is still a mess for Nvidia cards overall which is becoming more and more important.

You could try disabling VRR in your display settings. I believe it is set to auto by default if supported, but it does not work properly for some monitors causing flickering.

Same. A 7800 XT is on its way as we speak replacing my 2080 Super. I am just sick of Nvidia even though performance wise it wouldn’t be necessary.

I am aware, but check the referenced issues. Support has been merged like a year ago and at least gnome on Wayland should work out of the box. It’s incomplete, but it should be working

Also barrier is considered abandoned at this point the previous maintainers forked it which actually is leap input.

Check the input leap project. While I haven’t tested it myself, Wayland support got added like a year ago. You still needed to rebuild some packages, but reading the issue tracker now it seems to have gone a long way.

Unfortunately it is still not considered production ready. At this point I assume they will have it implemented and ready way before synergy though.

Sounds like you don’t clean your package cache. You can enable the paccache.timer to handle it for you on a weekly basis.

https://wiki.archlinux.org/title/pacman#Cleaning_the_package_cache

There was or is a bug with WebKit when using Nvidia. If that’s the case remove the Nvidia driver and use nouveau instead. After logging in you can reinstall the Nvidia driver again.

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2498

Wait, people really believe writing boilerplate filled bash scripts to implement just the idea of dependencies does scale into enterprise environments? Which don’t come even close to emulate most of the very useful and important features systemd provides?

Seriously that’s a take I have never heard one say while keeping a serious face. There is a reason systemd is as popular as it is for every desktop and server distro out there.

It is far from perfect, but who in their right mind would want sys-v init or similar systems back? I can’t even imagine what a mess it would be managing all the contexts and implementing it securely and portable with an init script.

I think the biggest difference is that it is based on Debian and is a bit more conservative. I prefer cinnamon over xfce and in its default even over KDE.

Really, I just assume better hardware compatibility and slightly newer packages from Mint and that’s just about it.

Don’t read too much into it. There is nothing wrong with MX, Debian or just plain Ubuntu either. In my opinion Ubuntu fixes a few problems Debian has and Mint does the same with Ubuntu. Because apt is widely supported the Debian family is a great choice anyway.

If people ask me what distro to choose I say Mint.

Unless you already know what you want and need it is simply the best distro out there to get your feet wet. It is very competent in what it is doing and can be used by anyone no matter the experience.

Even though I believe there are better distros out there this is the only one I would recommend to people new to Linux and it is still a solid choice for experienced users alike. You can use it forever or branch out from there, both are very valid choices.

Kinda. They still appear with a message telling you that they are blocked. You can press a button to show the comment anyway. It is like a soft block where you can decide whether you want to read a comment or not.

Of course not never, but not often enough to even recall once really.

It sounded like you are chewing on straws or so. Sorry for the misunderstanding!

Teeth? You are using straws wrong. They are supposed to only touch your lips

Arch is supposed to be used, it is a normal distribution. It is not hard, it is simple. That’s its whole philosophy.

It is only difficult if you are new to Linux, because it doesn’t hold your hands and has no opinion about a lot of things hence you must make many decisions yourself and configure everything like you need it. You have to know what you need and want.

The notion of a difficult distro for the sake of it is ridiculous. Who would ever want to use it? Arch is popular, because it is easy to use, but lets you configure the system to your desires for the most part.

I know it is not really what is asked, but cron is a pain in the ass to handle and manage. I am not sure if it is officially deprecated yet, but I would migrate everything to systemd timers instead it is so much better. It provides configuration tools and proper integrated logging and troubleshooting tools.

Just create a service file of type oneshot which runs your backup script and a timer unit with the same base name. Set the timer to hourly, place both files into /etc/systemd/system, do a daemon-reload and enable the timer. You can see the status or journal for output and list-timers to see the schedule and wether or not it ran.

Usually if programs can run in a user context but don’t work as some automated process it is either due to environment differences. Most importantly PATH which can be solved by using absolute paths for programs. Another very common problem is the systems MAC implantation although it happens more often with SEL. Still you might want to check your AppArmor configuration and (audit) logs.

If you want to stick with cron also make sure to read the mails (/var/mail/root by default), because most cron implementations dump their output/logs there.

If you can use containers always use containers as a rule of thumb. VMs are less efficient in almost every way and they add some unnecessary complexity.

For docker you basically only have to backup the persistent data. So in case of the docker setup you just have to backup the mounts and probably your compose file you are using. This probably also answers your third question already. Container files can be left alone and don’t need to be considered for backups as they should be stateless and can reside in their default location (/var/lib/docker/overlay2 or so by default).

Overall it is quite simple as you only really have to consider the mounts and the docker setup. The mounts you define and should be really obvious and the docker setup is just a few config files at most or just the compose file.