Raise your kids to only use FOSS. Not for ideological reasons but so they never get addicted to videogames. Luanti (formerly Minetest's) and Super Tux Kart are fun yet so ass compared to what they're trying to copy
Back in primary school we got to play SuperTux on our Linux machines after finishing our touch-typing lessons and schoolwork. It had sadly no noticeable effect in preventing me from wasting time that I could have spent learning useful skills instead.
I think forcing your kids to use Linux so they can't play League of Legends or Fortnite is a good idea though, for those games specifically
So, I have a very weird problem. Chrooting into an unrelated install to get a few things fixed there seems to have borked my SuSE's Xorg. I don't know what exactly happened, but the GUI wouldn't start anymore ever since.
It cannot find the NVidia modules for some reason. I tried to fix it by installing XLibre, but that didn't work, either. Both SDDM or LightDM refuse to start, the log file always states that the 'nvidia' module cannot be found or doesn't exist, yet, I have all four module variants loaded and can play games that don't strictly require X just fine, and they even run faster.
I've made the modules load early using the Dracut method — didn't help.
So, I have a very weird problem. Chrooting into an unrelated install to get a few things fixed there seems to have borked my SuSE's Xorg. I don't know what exactly happened, but the GUI wouldn't start anymore ever since.
It cannot find the NVidia modules for some reason. I tried to fix it by installing XLibre, but that didn't work, either. Both SDDM or LightDM refuse to start, the log file always states that the 'nvidia' module cannot be found or doesn't exist, yet, I have all four module variants loaded and can play games that don't strictly require X just fine, and they even run faster.
I've made the modules load early using the Dracut method — didn't help.
Kernel module != xorg video driver, check that /usr/lib/xorg/modules/drivers/nvidia_drv.so (or whatever the suse equivalent path is) exists and is readable.
(And who asks forums for help these days, and not Claude, Gork or chat geepetee.)
eta: gangster computer gods are more familiar with suse than me and suggested this:
I've actually been following the PaintdotNETonWine project for a little while now. Mostly because it's the only viable fucking program for image editing that isn't owned by some gigantic company (yes, I hate GIMP).
The creator of PaintDotNet has been a massive fucking cuck ever since version 3.5 at the very least. PaintDotNet stopped being open source since version 3.5 or so because 'too many people were mimicking being the creator'. So instead of having the source available for people, so Linux development could be easier, he completely abolished the GitHub repo, only allowing the most recent version to be downloaded - only because there were like five bad actors. He's a gigantic cuck and actively fucks over his own program. He wants sole control over the program.
I'm so glad he changed his stance (literally yesterday lol) on having it work on Wine since then. He was basically saying "Fuck off, I don't have time for you faggots" to Linux users who were used to his program before.
To combat this and a few other similar instances that have happened over the years, I believe I will change the way that I release the source code for Paint.NET. As a stopgap before the v3.20 release, the version 3.10 source code is no longer available, starting immediately, while I finalize on this decision. It just feels like it’s a disaster waiting to happen with the way I’ve been releasing it so far.
Here are the changes I’m thinking of:
I will no longer be releasing the source code for the installer.
I will no longer be releasing the source code for PaintDotNet.Resources.dll, which has the code for loading resources as well as all the graphics (icons, logo, etc.)
I will no longer be releasing the text and graphic resources in the source code distribution (RESX files, icons, logos). This includes the translations to non-English languages.
I am still contemplating how much of PaintDotNet.exe I want to release. Especially parts such as the updater and core parts of the main UI that I’ve spent a lot of creative energy on.
He hasn't provided the source code since 2007, which means Linux users still had to do with the version that came out two fucking decades ago, fucking XOrg had more updates since then.
The creator of PaintDotNet has been a massive fucking cuck ever since version 3.5 at the very least. PaintDotNet stopped being open source since version 3.5 or so because 'too many people were mimicking being the creator'. So instead of having the source available for people, so Linux development could be easier, he completely abolished the GitHub repo, only allowing the most recent version to be downloaded - only because there were like five bad actors. He's a gigantic cuck and actively fucks over his own program. He wants sole control over the program.
Opening the main paintdotnet.dll in dnspy, it doesn't seem obfuscated or anything. I suppose you could use an LLM to assist in renaming the few variable names that do come out a bit garbled to be more readable.
Kernel module != xorg video driver, check that /usr/lib/xorg/modules/drivers/nvidia_drv.so (or whatever the suse equivalent path is) exists and is readable.
(And who asks forums for help these days, and not Claude, Gork or chat geepetee.)
eta: gangster computer gods are more familiar with suse than me and suggested this:
Thanks for your help, but what eventually fixed it was a complete reinstallation through YAST. I had noticed SuSE had thrown in an older version of the open driver, so I've completely replaced it with a newer one. After a restart, it booted straight away into LightDM.
It's a massive over-engineered slopfest that doesn't even implement effects itself (as evidenced by his need for direct2d effects to be implemented in wine) written in the classic retard-signaling language.
And it's not Kolourpaint, so any argument for it is de facto (if not de jure) invalid.
It's a massive over-engineered slopfest that doesn't even implement effects itself (as evidenced by his need for direct2d effects to be implemented in wine) written in the classic retard-signaling language.
There is nothing really that wrong with .NET, and it was a Windows-only program, so using Direct 2D, which is one of the APIs that existed on the platform for almost 20 years, doesn't make it slop.
There is nothing really that wrong with .NET, and it was a Windows-only program, so using Direct 2D, which is one of the APIs that existed on the platform for almost 20 years, doesn't make it slop.
"Existed on the platform for almost 20 years", let me just spend 20 minutes installing 5GB of runtimes while scrutinizing 20 checkboxes asking me to sacrifice newborns every five minutes.
"Existed on the platform for almost 20 years", let me just spend 20 minutes installing 5GB of runtimes while scrutinizing 20 checkboxes asking me to sacrifice newborns every five minutes.
The .NET 4.8 runtime (which was the last full-fat runtime) is about 70 MB. NET 9.0 (which Paint.NET uses) is smaller at 48 MB.
I could install Paint.NET in minutes on a computer back in 2010, and I just did it on my work machine, and nothing has changed.
The SDKs for .NET aren't event that big these days compared to the days of the full-fat runtime.
The biggest problem with .NET is that are VB 6 and VB.NET refugees, and the code they produce reflects this. Luckily most of these guys are nearing retirement age.
"Existed on the platform for almost 20 years", let me just spend 20 minutes installing 5GB of runtimes while scrutinizing 20 checkboxes asking me to sacrifice newborns every five minutes.
View attachment 9514492
The .NET 4.8 runtime (which was the last full-fat runtime) is about 70 MB. NET 9.0 (which Paint.NET uses) is smaller at 48 MB.
I could install Paint.NET in minutes on a computer back in 2010, and I just did it on my work machine, and nothing has changed.
The SDKs for .NET aren't event that big these days compared to the days of the full-fat runtime.
The biggest problem with .NET is that are VB 6 and VB.NET refugees, and the code they produce reflects this. Luckily most of these guys are nearing retirement age.
Are you talking installer sizes? WINEPREFIX bloats with more than tens of megabytes whenever I need to run some retarded dot not shit, and it takes forever to install even on my high-speed 56k dial-up here in Lesotho.
And that's also ignoring the massive directx runtimes, I wrote "runtimes" plural for a reason. paintdotnet is a bloated slopfest no matter how you look at it.
