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?

What are you using for the Unified Push setup? I tried using ntfy and could never get notifications to come through on GrapheneOS

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.

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

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 👍

Is this secure drive erasure 🤔🤔🤔

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

I use Lyx with a local Texlive install, and it works great (openSUSE tumbleweed)

Having BTRFS snapshots set up for root: 😀 Elbow on the keyboard issues this command before the sudo timeout: sudo rm -rf ./testdir/cd $HOME RIP home directory 😭 and still figuring out the best way to do snapshots of home without using timeline snapshots and using a ton of space…

My current tower started out on Windows, and for some reason after a year or so it started crashing out randomly. Load didn’t matter, it would pass benchmark tests and then crash randomly 5mins after boot. However there was not a single useful error I could find. Installed Fedora, and looked at journalctl after a crash. Immediately I see “GPU has fallen on the bus”. Apparently it is relatively common, but I also found a thread that said it actually can be caused by loose connection. Did a complete reinstall on my GPU, haven’t had the problem again (~6mo now, had both 535 and 545 drivers). Sometimes it really might be a descriptive error message 😆

I use BTRFS and even have convenient Snapper snapshotting set up. It works great. Here is a whole step by step guide on how to set up your system with it: https://sysguides.com/install-fedora-with-snapshot-and-rollback-support

https://ibb.co/2vT1jSH

The situation is rapidly getting better, and I’m daily driving Fedora 38 with 3060Ti using the RPMFusion Nvidia driver and Gnome+Wayland. Everything (and I do mean everything) I’ve tried has all its basic functionality at baseline. Xwayland is a thing and it covers for not having true Wayland support in alot of cases. Not like there aren’t bugs and QOL issues, but from what I’ve seen Nvidia is engaged and working to fix them. We should probably try to critique Nvidia/Wayland based on specific issues now, instead of broad brush “Nvidia/Wayland bad” rhetoric…