I do agree that quality control should catch things, but we are all human and we don’t catch a 100%. So if quality control is flooded with too much things to catch, the chance of one slipping by increases.

Also, a lot of FOSS is based on volenteers, do we just ask those people to put in more hours? Who is responsible anyways if something makes it through and actually causes damage to something or someone?

I find the decision quite reasonable. You at least filter out the party most likely to pull something shady. We should still be very careful, but it takes away some the work.

Removed by mod

Removed by mod

Removed by mod

Removed by mod

This is cool. I struggled with exactly the problem as described. Installed the NVIDIA driver and it would not load, without telling me why. Somebody on Lemmy pointed out that you need to disable Secure boot.

It’s nice to know they are working on a solution, just a pity it’s so difficult. But they are trying very hard to make it workable.

Well, how is the system supposed to know that you want the crack to do something to that executable? The anti virus just sees something is happening and flags it. It does not see a difference.

Not at all, a crack does something to an executable file that you use. Malware would do the exact same thing.

Wrap it up folks, we’re done here.

It’s actually a classic programmer move to start over again. I’ve read the book “Clean Code” and it talks about a little bit.

Appereantly it would not be the first time that the new start turns into the same mess as the old codebase it’s supposed to replace. While starting over can be tempting, refactoring is in my opinion better.

If you refactor a lot, you start thinking the same way about the new code you write. So any new code you write will probably be better and you’ll be cleaning up the old code too. If you know you have to clean up the mess anyways, better do it right the first time …

However it is not hard to imagine that some programming languages simply get too old and the application has to be rewritten in a new language to ensure continuity. So I think that happens sometimes.

There’s so many distro’s to choose from that can all be productive.

If the question is this short, my answer is too: Go try at least 10 and then come back to tell us what you liked and what not.

Without any further information it’s like going into a forest and asking people to point out a tree. Unless you look for some specific tree all will do…

Edit: Fat fingers

While it probably isn’t the issue for you, I have once been chasing a hard freeze that was caused by some APM setting in the BIOS. If you are on AMD right now you could check it.

It was very weird, setting it to automatic would cause random freezes. Setting it to on or off would both work just fine. Somehow the automatic setting gave me issues.

Just a random thing for you to check I guess.

Just wait. In 10 years 32 gig is on the low side to just run the OS. Hardware getest faster and bigger, but software scales with it.

The more resources are available, the more people will program computers to use them.

My first graphics card had 128mb memory. These days it goes in gigabyte and they use the memory and processing power to produce amazing things.

On the other hand, they also are not as critical on efficiëncy as used to be, because there are simply more resources available anyway. As a consequence, some programs use a silly amount of resources for basically doing nothing. Sometimes I really feel like my browser is eating RAM…

As far as I know, other distributions just don’t show these errors, but Ubuntu choose to show them.

Most of them are just due too a BIOS implementation that is not entirely up to standards, from what I understand. It seems some manufacturers have chosen to make their system easier to use with Windows instead of strictly enforcing standards.

I just ignore the errors. As long as everything works properly, I feel fine with that.

Looks like the network mount is the problem.

Now you need to find out more. You can try setting up a mount outside the VPN network and check if that causes the same problem.

If it does, there is something going wrong with mounting over a network.

If it does not, you can try mounting a different location on the same drive through VPN. If a different folder or location does not cause problems, you know you have to look at the specific location that is causing problems.

If a different location on the same drive still causes problems, it could be your VPN connection causing problems or maybe the drive is failing. Check the drive for errors, and check if your VPN does work properly overall.

This should be a decent start to figuring out where the problem is.

Also make sure to check permissions, since it sounds like the Save as screen is trying to access the location but it does not get the proper response. See if you can access the location in a file explorer.

If that is the only thing saving you from RSI you’re going to get it anyway.

I’ve had the pleasure, and your body posture and mental state of mind are much more important. Getting up every now and then is also important, changing seat position helps, and doing some sport also helps.

Both of my arms did hurt so much I could not cut my own meat. Mouse or no mouse:(.

Am much better now though.

You are correct, but then Windows will get the boot entirely. It can stay as long as it behaves. It literally has it’s own fate in it’s hands.

And I know how to get the bootloader working again, so that will be just fine.

I was installing Ubuntu for the first time on my laptop. My laptop had two hardisks, an SSD with Windows and a drive that I could switch out for a CD-rom drive by hand.

I decided to install Linux on the second drive. So I install, reboot, and Grub loads up…and tells me it cannot find the drive.

I eventually find the command fwsetup, which lets me boot into the BIOS again. Of course I don’t know what is going on, zo I just reboot and now it loads my Windows installation on the SSD.

So at least that is intact. I reboot again, and I’m stuck in the Grub bootloader again. The second drive just would not load properly to boot from it. Very annoying. I tried everything I could think of, everything I found on the Internet, it just would not boot the Linux drive.

In the end I just split my SSD and installed Linux next to Windows. I did split the second disk too, so my home directory is on the second disk and now everything works.

However, it’s a Toshiba laptop that gave me lots of trouble before with installing Windows before. I have decided that this is how it will run and I’m not messing with it again. The panic when I feel I broke it again is just not worth it.

I suspect most vendors just dgaf about being linux certified. They just build their hardware to work with Windows since that is what most people will use. If the hardware happens to work with Linux too, great. But it’s much more important to make sure it works with a system that over 90% of your users use.

If you build laptops that you deliver with a Linux system on it, then yes, you will make sure it is Linux certified and it works properly.

It’s not difficult to imagine that for most laptops that are made, Linux wasn’t even considered for a second.

Going a little overboard there in my opinion. If one of the major distributions would catch something sketchy, a whole bunch of tech savy would be all over it in no time.