sudo systemctl restart vaultwarden.service

Done. :)

Thanks for the heads up.

So if I don’t have a camera on my laptop, I’m good?

It did 4 passes by default. It took almost 3 hours to run on 16 GB of RAM.

It’s possible there is an issue with the WiFi. I had lots of WiFi issues on this laptop when I used Windows (micro freezing when using typing into an SSH shell, and pings would drop at the same time), but since switching to Linux, those went away. I’ll definitely keep that in mind. I’ll try using wired network if the issues come back after swapping SSDs.

Well, I reinstalled this morning and I’m keeping the nouveau driver this time instead of going with the proprietary. I don’t play play games on this laptop anymore since I set up sunshine/moonlight, so it shouldn’t be a problem.

Well, I just reinstalled on a new SSD this morning. Fingers crossed it all works out! It usually takes a few weeks for the issues to start happening each time, so I guess I’ll just wait in agony until then. 🥲

I will try this once I get my system back up and running tomorrow! I’m going to install the distro on a new SSD and see what happens.

Yeah, I just ordered a new SSD. I’ll give that a try when it arrives tomorrow. Smart says it passed, but suspect my SSD enough that I think it’s worth it to just try another SSD.

I have 16GB of RAM and 16GB of swap as a swap partition. Though I have also tried a 16GB swapfile and saw no difference. I don’t know about zram.

It’s a 2021 Asus Zephyrus G15 with an AMD CPU and an Nvidia GPU. I got an aftermarket SSD off of Amazon so I could dual boot with Windows, but I haven’t booted back into Windows a single time since installing Linux. Though that might be a good test.

I can try set -x once I reinstall my distro and get it back up and running tomorrow, as it is currently borked. Since zypper does all the downloads then all of the installs, I was able to see that it always happened during the install phase, not the download phase.

I am definitely interested in the possibility of it being related to the proprietary Nvidia driver. When it happened yesterday, the proprietary Nvidia driver was being updated (not sure at that exact time. But it was in the list of packages to be updated). I’ll keep an eye on that for sure.

1. Already done. :)
2. It started with GUI, but I switched to command line, and even did it in a separate TTY to make sure it wasn’t something weird going on with updating plasma from plasma. After switching to Arch-based distros, I have only use CLI.
3. Currently I’m on EndeavourOS, but after the most recent time this happened, it won’t boot, and I can’t even mount and chroot to it (I get an I/O error message)
4. No, I’m at about 1% capacity.
5. I ran this from a live USB, and it came back with no errors detected, but returned instantaneously, so I’m not sure if it ran the right thing. Doing more research on it now. Edit: I did it wrong. The test is running now. Edit 2: Smart says it passed. :/

Thank you for the suggestion. I am unfamiliar with this, but I am reading about it now.

I was at work and I spent a full day trying to figure out how to do something work-related on Windows, but every program for it was for Linux. This was before WSL, so that wasn’t an option. I don’t remember exactly what the task was, but I remember growing increasingly frustrated before I decided to just dual boot my work laptop with Ubuntu. I never booted back into Windows a single time after that. I eventually deleted that partition to reclaim the space.

I didn’t install Linux on my personal laptop until about a year ago because of how awful Windows 11 is. I was reading about how Windows 10 is going EOL fairly soon, and decided to just make the switch now.

Just this weekend I installed Manjaro after having tons and tons of issues with SUSE since the Plasma 6 upgrade. I have a laptop with AMD integrated graphics, which Plasma is running on, so your issues may not apply to me. But if I run any apps on the Nvidia GPU in full screen, I do get the flickering issue.

My biggest issue I have is that no matter what distro I use, as soon as I install the proprietary Nvidia driver, my system fails to boot like 20% of the time. It just freezes during boot with no error messages or warnings that I can find. But once it boots, it works.

I’m not sure how to run Plasma on my dedicated GPU so I can see if I have the same issues you have. But with my current setup, it works.

Could you elaborate more about why returns discourage deep sales? I’m not sure I’m getting it from your comment. It seems like it is just correlation rather than causation.

I have tried KDE connect, and it never works when I need it to. I just send it to myself on Signal. It’s the easiest, most non-bullshit way.

I guess I’m a dummy, because I never even thought about this. Maybe I got lucky, but when I did restore from a backup, I didn’t have any issues. My containerized services came right back up like nothing was wrong. Though that may have been right before I successfully hosted my own (now defunct) Lemmy instance. I can’t remember, but I think I only had sqlite databases in my services at the time.

I use it most days, even as a PC/web browser connected to my TV. I play any classic games or anything not graphically intensive on it. Anything with a medium-level of graphical intensity I’ll use moonlight to stream from my desktop in the next room over. If it’s a particularly beautiful game, I’ll play it on my gaming PC directly, since I have a really nice OLED monitor hooked up to it directly.

I imagine people who care about this sort of thing are more likely to report it. And people who care about this sort of thing are also more likely to be early adopters and go through the effort of switching to Wayland.

The way to get a more random sample is not something I want (built-in, automatic telemetry by default). So I’m fine with having skewed data for something like this.

I have only ever packaged for RPM (the company I work for has our own RPM-based distro). How does it compare? I find RPM to be pretty easy, but I have nothing to compare against.

Mine are named after fictional robots, computer programs, or AI. It started with my wifi being GLaDOS for 5 GHz and Wheatley for 2.4 GHz. I thought it was funny that everyone could immediately tell that Wheatley was the slower one. Over time, I continued the trend. My gaming PCs are named after characters from the Mega Man X series (desktop is Zero, laptop is X, steam deck is Sigma). My macs are named EVE and WALL-E. My server is named Sibyl System (from Psycho Pass).