NVIDIA definitely has stability issues, newest drivers still kernel panic on resume from suspend. Only thing more you can do is try to capture debug logs with nvidia-bug-report.sh (I go in during a crash via SSH, usually the system is still responsive for a little while after), and post it to the NVIDIA Linux forums. They do actually seem to use the feedback there, NVIDIA reps respond from time to time and say they’ve submitted bug reports from the feedback. Otherwise, after that yeah you just do what you have to do for a usable system and wait…

Relax and Recover for bare metal backup of the OS critical components and directories, and Deja Dup (or Gnome Backup) for user files

So… does THIS mean that this doesn’t support explicit sync, right as explicit sync is about to be stable and supported in the NVIDIA 560/565 drivers? As far as I know there are currently other ways to do screen capture outside of this protocol on Wayland so its not like there are no interim solutions, why release this when it is essentially still incomplete?

I wonder how this calculus changes with the dawn of AI built into the OS… will a Linux system that avoids all that nonsense end up being more energy efficient?

I am so old

If it works on chromium I’d consider that even if it is a quirk on the bank website, chromium is handling it cleanly and allowing you to use the site. That’s something we probably want incorporated in Firefox. I’d encourage submitting the bug report to Mozilla, and don’t assume too much about what they can/cannot do!

I think the key part here is that it’s a guess on your part whether using Firefox is the cause. Do you get any specific error when using the website? Or does something just “not work”, such as you click a button and it does nothing?

Also, I’ve run into stuff like this before, and my best bet has been to be flexible about using other browsers to work around issues. I would suggest testing the banking website with Chromium (or even Chrome). If it works, file a bug with Mozilla (https://support.mozilla.org/en-US/kb/file-bug-report-or-feature-request-mozilla) and just use Chromium/Chrome for only that website until the bug is fixed.

This will allow you to still do business, while still participating in open source via a helpful bug report that could end up benefitting others as well.

Because beginners have no idea about OS architecture concepts. If they are a true beginner coming from Windows or MacOS they may not understand things like the Linux boot process. Of course they can read the Arch install procedure which I’ve heard is excellent, but many people are easily intimidated by documentation and often view computers as a tool that should just work out of the box without them needing to understand it. Mint is an attempt at making that happen. Obviously, once you start to modify your Mint install alot you are going to run into issues, and a highly modified or customized system is where distros like Arch and Tumbleweed actually become easier to maintain. I’d argue Mint is a natural first step to the Linux pipeline. People who only need a web browser will probably stop there, while others will continue to explore distros that better fit their needs.

Thank you!

What did you have to change for VRR? I’m also having an issue where I need to force the EDID and haven’t been able to get VRR

Looks like a whole bunch of conversation about this topic can be found here:

https://retrocomputing.stackexchange.com/questions/1811/which-linux-or-bsd-distributions-do-still-support-i386-i486-or-i586-cpus#1815

Take note this is an informal blog post, I somehow thought this was “official”… but it’s just sort of a rambling update on various items. Still good insider info

Archive.org is essential. I donate regularly, they are a key part of the infrastructure of the internet now…

So, basically shitposting poisons AI training. Good to know 👍

I used to use this, you can turn the audible alarm all the way off and just use the shaker!

https://www.amazon.com/Sonic-Alert-SBB500SS-Extra-Loud-Flashing/dp/B000OOWZUK

If you haven’t I would join the Matrix space, really helps when there’s a gap in the docs!

Right… does it even make sense that installing all recommended packages is the default zypper behavior? Lyx for example will install a 2GB Tex distribution by default, which will conflict with any existing Tex install. Why on earth is that the default… If you are installing Lyx, you very likely at least understand that you need to choose a Tex distribution.

You can already write a for loop that handles whitespace in file names, just use quotes around the file name variable:

https://www.howtogeek.com/850124/spaces-in-filenames-on-linux/#how-to-use-filenames-with-spaces-in-bash-scripts

Just to be sure, you should check whether SSHD is enabled: sudo systemctl status sshd.service If you never enabled it and it’s disabled+inactive, then no need to reinstall Tumbleweed per the current guidance. Also you can double check your version of xz to make sure it’s downgraded, the downgraded version for Tumbleweed should look like this:

sudo zypper search -vi xz
Loading repository data...
Reading installed packages...

S  | Name | Type    | Version               | Arch   | Repository
---+------+---------+-----------------------+--------+------------------
i+ | xz   | package | 5.6.1.revertto5.4-3.2 | x86_64 | update-tumbleweed
    name: xz

Fairly simple explanation by arstechnica: “The malicious versions [of xz], researchers said, intentionally interfere with authentication performed by SSH, a commonly used protocol for connecting remotely to systems. SSH provides robust encryption to ensure that only authorized parties connect to a remote system. The backdoor is designed to allow a malicious actor to break the authentication and, from there, gain unauthorized access to the entire system. The backdoor works by injecting code during a key phase of the login process.”

Also from the article, you should check if your distro is offering a downgrade from the affected 5.6.x packages. Right now the exploit is not fully understood. For example, openSUSE recommends a full reinstall of Tumbleweed if an SSH server was enabled, just to mitigate risk.

https://arstechnica.com/security/2024/03/backdoor-found-in-widely-used-linux-utility-breaks-encrypted-ssh-connections/

https://news.opensuse.org/2024/03/29/xz-backdoor/