WSL for me.
WSL for me.
Sail the sea.
In your word, pointless.
Mint Cinnamon. I would choose Zorin Lite (XFCE) as it has nice theme already.
Setup Btrfs + Btrfs Assistant, rollback if any update breaks things you need.
It’s stable enough for me everyday use but this will depend on your use case + hardware setup. Even some people will swear by Manjaro for years without breaking. I found that usually if stuffs break in Arch, i can fix it but not so much if stuffs break by update from Ubuntu/Fedora.
I find it hard to think you care about the beginner experience if you recommend Arch.
TL;DR: it came out that some devs of one of the biggest platforms in their respective space neglected to bring in some very basic functionality regarding the ability for users, mods, and admins to delete images that were uploaded. When a user asked about having this functionality, especially in the context of GDPR compliance, the devs acted like a bunch of entitled dicks, effectively bellowing at the person for daring to make such demands of their time.
I generally think these guys are being a bunch of assholes.
Software engineer full-time ~70k/year, lemmy dev 24k/year. You should look into the mirror.
And it’s not that the devs won’t fix the issue but there are other issues with more priorities than this. Europe is not the only continent. So just like any other FOSS projects, wait for it or smash money if it’s really important or do it yourself.
Btw based on Nutomic’s comment, it’s fixed next release if you bother to look before making 2 articles back to back.
Unfortunately there was some miscommunication in this issue and we failed to get to the root cause. In fact the Lemmy backend has an option to delete all content when an account is deleted. This used to be the default behaviour but was changed in 0.19 so you need to set a parameter delete_content. We failed to add a checkbox for this parameter to lemmy-ui.
However the checkbox is added now in #2385 and will be included in the next Lemmy release. Other frontends and clients may also need to adjust the delete_account api call.
From the blog
Something that I notice said consistently by those who have little experience in Lemmy admin spaces is “why not just contribute then?”
And the answer people try. And this happens. This unfortunately leads into the next point that is the developer teams behavior. As well, highlighted above in the blog post of that Lemmy user who unfortunately had to deal with devs behavior themselves.
From https://programming.dev/post/5180682
I will no longer be able to assist with development nor debugging actual issues with the software… Quite juvenile behavior from the devs. It stemmed from this issue where the devs continuously argued in public by opening and closing an issue. Anyway, thought I would keep y’all apprised of the situation, since these are the people maintaining the software you are currently using.
Root issue: https://github.com/LemmyNet/lemmy/issues/234
1st snowe’s comment
This is a really weird thing to have an argument about. Scheduling client side would be a nightmare, like how Microsoft Outlook handles emails where you schedule an email for the morning, close your laptop, and then the email doesn’t send because your laptop is asleep.
But even then arguing about it through reopening and closing an issue is really weird. Leave the issue open, have a discussion, talk about the pros and cons of putting it in the software, and then make a decision with the community.
2nd snowe’s comment
And then marking the most relevant comment in the thread as off-topic. You’re really alienating your users and server admins with this. Have the discussion like adults.
Full of . There’s hardly any arguing if you look at the timeline of the 2 devs’s comments. 7 days temp ban to chill looks ok to me.
Can always change whatever you don’t like, that’s the strong part of KDE, unlike Gnome where you have to rely on 3rd party extensions and hope they don’t break next update.
My OCD can’t stand the shutdown/reboot buttons just floating there. I would just use the terminal for reboot/shutdown.
This is done via storing the unlock key in USB drive and need the USB plugged to auto unlock, see if it helps.
Nvidia driver: https://rpmfusion.org/Howto/NVIDIA
Gnome and KDE (other Desktop Environments too) install Nvidia driver the same way.
For partitioning, I suggest to keep it simple, usually the stock config from the distro is good enough. This is useful for troubleshooting if issues arise later.
Big size data like media/games can be kept in other drives.
My comment is based on MIT-MAGIC-COOKIE-1
from the log in the picture. Look at it again and there’s also SocketCreateListener() failed
. So OP may check this as well
https://wiki.archlinux.org/title/xorg#SocketCreateListener_error
Check /etc/hostname
This is based on the image, the best you can do it check the logs like other comments said, it’s better if the error is identified through the log.
There’s a KDE plugin for Wallpaper Engine
https://store.kde.org/p/1475528
Github: https://github.com/catsout/wallpaper-engine-kde-plugin
An alternative to Kubuntu is TuxedoOS (similar to PopOS (Gnome) but for KDE). You can also try KDE Neon.
You can use VM to install and try new distro, worst case you make a new VM and start again.
For learning, if it was me I would just roll with Arch, using distro like Garuda that has BTRFS rollback or even EndeavourOS. A fuck up can be saved from BTRFS rollback, back up dual boost or 2nd pc.
Avoid Nvidia.
You can still do the auto snapshot daily/weekly plus the manual snapshot whenever big update coming or try something.