He was probably supposed to mark downloaded .run file executable. Instead he went to collect errors.
this warrants a TON of upvotes, are y’all for real? THIS is what it looks like to the potential converts and I deal with them daily.
the single, giganticest, most glaring issue in every distro and DE is the complete absence of sane defaults as this dude demonstrates, his comedic chops and edge-case issues aside.
converts nowadays come from the hyper-polished world of Android and iOS devices, where you turn it on and it works. the idea that the average user needs complex setup and training and is faced with these cryptic sysadm-intended-for error messages delegates it to the narrow userbase it has, and it can be so much better.
Like, what distros? All the majors I’ve used in the last 5 years have pretty sane defaults. Except Arch, of course, because the packagers just put in what the devs send.
Hehe, it was fun to watch. It baffles me that Ubuntu still has those errors though.
That dpkg lock issue 😭
I still don’t know what’s the proper way of handling it other than just restarting the computer and deleting the lock files, then hope nothing breaks.
He was running long installation process from command line and lock warning was probably appropriate.
Remember kids, whatever Linux Distro you installed, it’s the wrong one…
The only good distribution is my distribution.
