I second this. I need to try guix, nixos has been my daily driver for years now.

Nowhere, but I’ve bought prints locally that are really nice that come from people on patreon… Lol but I forgot the names :(

Maybe try kscreen-doctor? I don’t use kde regularly but that showed up in a search.

It’s a time proof blockchain system that allows submissions to be incorporated into a block and then after the block is published users can prove that they submitted whatever before a certain time I think. Worth a block IMHO.

Maybe this? https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3678

Try using alsamixer, check for channels that are muted.

Also check if your distro is saving and restoring alsa settings every boot and remove the settings file

Grub should be able to boot mint fine, just know where grub is installed and which disk boots the system before formatting anything. To test, unplug the windows disk and see what happens

Hopefully this isn’t a common problem, but I was running auto bed leveling manually, the getting failed prints because I didn’t save the levelling results to the printer and I didn’t have gcode to load the levelling data and enable it in my slicer settings.

Maybe something similar is happening to you.

You can also try disabling auto leveling and level manually, that was giving me better prints for a while but it’s a pain.

I have the same problem with nixos. It’s partially solved but some plugin derivations are behind the times or something (or maybe I’m the problem and I can blame documentation :P)

Maybe… In 2027 👀

Unfortunately it forced all existing users to submit as well, but we already gave it a bunch of photos of ourselves before the beast had revealed itself

Lol as we’ve discussed before, inaccurate but funny.

I think xvnc does this with vnc. If using gnome start gnome-remote-desktop with systemctl --user start gnome-remote-desktop then use grdctl to set it up (or the settings gui). I’ve had luck with rdp on a Wayland session this way.

Sounds like the right choice! I’m glad you got Debian up and running,

I get paid by the hour! 😅 But for real though it’s a struggle. Mostly I try to use msys2 for everything but. I still have native git. There are some long standing bugs that make the vim excruciatingly slow to open or close, really I should go try to fix it but it doesn’t feel like a fun problem.

And just like that gold is a proof of work currency. Too bad those economics will change as gold becomes less scarce. Buy mercury now!

For work, I just use windows. Not my machine not my problem.

For AC power, capacitors don’t effectively store energy for later, and would change the power factor to make the resistive load reactive which can bring down the efficiency of the power transfer. For AC power a big ol resistive heater is probably as efficient as you can get, which is part of why those kettles are so simple and boil water so fast.

A kettle that stores energy would need to use DC power, converting it from AC and probably have a very large capacitor, more likely a battery.

Don’t be afraid of the command line, breaking Linux is how you end up learning how to use it!

I haven’t done this tutorial but if that kind of thing helps you this one looks pretty good.

My best guess is you need to do something like:

(In the shell, one line at a time, enter runs the command)

mkdir /mnt/tmp
mount /dev/sda2 /mnt/tmp
nano /mnt/tmp/etc/fstab

Nano is a text editor that uses your whole terminal, so you will see the contents of /mnt/tmp/etc/fstab (the file that controls where disks are mounted) and replace ‘sdb’ with ‘sda’ on the line starting with /dev/sdb2. The bottom of nano’s screen shows you the keyboard shortcuts, I think Ctrl W will make it write the file, asking for confirmation of the filename, which should stay the same. Exit nano (Ctrl+x maybe?) then reboot with the command ‘reboot’

If you get any errors about access denied or permissions, run ‘sudo bash’ to get a shell with more power and try again.

Good luck!

What most likely happened is your disk order switched and, as others have mentioned, using /dev/sda1 or something similar to point to partitions is unstable and can’t be trusted. Once your system is back up, look up how to specify partitions in /etc/fstab using UUID (something like /dev/disks/by-uuid/xxxx-xxxxxxxxxx-xxxx instead of /dev/sda2)