Amateur Linux Hour

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
it's a unity game, it should work well enough unless it does something weirdly out of the norm.
No clue, but I've seen other people complain of the problem on my quest for a fix, but all of them end with "it stopped doing it so I guess problem resolved" without identifying what changes they had made.
 
No clue, but I've seen other people complain of the problem on my quest for a fix, but all of them end with "it stopped doing it so I guess problem resolved" without identifying what changes they had made.
I can't Edit this long after, but I booted it up on a whim today.

It worked. No clue why this was different. Smooth as butter.
 
  • Feels
Reactions: ZMOT
I can't Edit this long after, but I booted it up on a whim today.

It worked. No clue why this was different. Smooth as butter.
So what happened to them happened to you too eh? If it was arch it would be broken forever so consider yourself lucky.
 
So Linux autism.

Regardless, I tried doing some gaming and it just doesn't feel good. Most of the games stutter hard despite making sure my drivers were good and I even bumped up the kernel. I think I'm going to try Nobara and if that doesn't help then IDK lol.
No, this was specifically late 80s/early 90s Mac and Windows autism where the 'accepted' wisdom was to give every binary an obtuse resource fork baked into the executable for things like icons and pre-rendered UI elements. The Unix/Linux philosophy is simply, "that shit isn't executable code, it doesn't really belong in the executable and putting it in there rather than on the filesystem is unnecessary obfuscation."

As usual, baby ducks mistake their nigger cattle shackles for normalcy.
 
Last edited:
So Linux autism.

Regardless, I tried doing some gaming and it just doesn't feel good. Most of the games stutter hard despite making sure my drivers were good and I even bumped up the kernel. I think I'm going to try Nobara and if that doesn't help then IDK lol.
A bit late but make sure you have installed the gamemode package.
 
Some Debian distros (in my case, Ubuntu 22.04, I'm not jumping to 24.04 immediately) have outdated Python repos; not just the system version but the optional next version up is severely outdated, Python 3.11.0.

To my understanding, my options are to compile from source, trust the Deadsnakes repo, or jump through hoops with a version manager tool.

These all seem like security risks, pains in the ass, or both.

Am I missing something obvious?

This is the first time I hands down unequivocally miss the Windows way of doing things: go to the Python website, download an installer for the desired version, and go.
 
Some Debian distros (in my case, Ubuntu 22.04, I'm not jumping to 24.04 immediately) have outdated Python repos; not just the system version but the optional next version up is severely outdated, Python 3.11.0.

To my understanding, my options are to compile from source, trust the Deadsnakes repo, or jump through hoops with a version manager tool.

These all seem like security risks, pains in the ass, or both.

Am I missing something obvious?

This is the first time I hands down unequivocally miss the Windows way of doing things: go to the Python website, download an installer for the desired version, and go.
IMicrosoft Edge for linux is available directly from their website and installing it adds a link to the Microsoft repository so it can keep updated to the latest version right away. Any linux program developer can do the same thing, but they choose not to.
 
Adding random junk apt repos is a bad idea and you should generally avoid it
They mean that you get the latest version of the app though i can see it being better to only trust more secure repos from companies and organizations like Microsoft, instead or repos from this random guy in the Netherlands that is only known by his username and has recently ceded development to an unknown person that posts during Chinese daylight hours.
 
Some Debian distros (in my case, Ubuntu 22.04, I'm not jumping to 24.04 immediately) have outdated Python repos; not just the system version but the optional next version up is severely outdated, Python 3.11.0.

To my understanding, my options are to compile from source, trust the Deadsnakes repo, or jump through hoops with a version manager tool.

These all seem like security risks, pains in the ass, or both.

Am I missing something obvious?

This is the first time I hands down unequivocally miss the Windows way of doing things: go to the Python website, download an installer for the desired version, and go.
Most Linux distributions package applications that are built in Python, and so could encounter problems if your only system copy of Python was replaced with and older/newer version. Most of them are useless things like GNOME apps.

Your good options are:
  1. Install the higher version that you're after from deadsnakes.
  2. Compile from source and install to /usr/local/... or /opt/... so you don't overwrite important shit.
Either way you should create a venv for each of your projects with the appropriate Python version and work within that, rather than installing pip packages willy nilly to your user account/system.
 
  • Like
Reactions: Lord Xenu
Some Debian distros (in my case, Ubuntu 22.04, I'm not jumping to 24.04 immediately) have outdated Python repos; not just the system version but the optional next version up is severely outdated, Python 3.11.0.

To my understanding, my options are to compile from source, trust the Deadsnakes repo, or jump through hoops with a version manager tool.

These all seem like security risks, pains in the ass, or both.

Am I missing something obvious?

This is the first time I hands down unequivocally miss the Windows way of doing things: go to the Python website, download an installer for the desired version, and go.
Most Linux distributions package applications that are built in Python, and so could encounter problems if your only system copy of Python was replaced with and older/newer version. Most of them are useless things like GNOME apps.

Your good options are:
  1. Install the higher version that you're after from deadsnakes.
  2. Compile from source and install to /usr/local/... or /opt/... so you don't overwrite important shit.
Either way you should create a venv for each of your projects with the appropriate Python version and work within that, rather than installing pip packages willy nilly to your user account/system.
Looks like there's a thing called "pyenv" to help automagically do python versions, like a venv but for a python version.
Also, Conda/Miniconda, which appears to be shit to me, but is designed to do this sort of stuff.
Also, containers.
 
Looks like there's a thing called "pyenv" to help automagically do python versions, like a venv but for a python version.
Also, Conda/Miniconda, which appears to be shit to me, but is designed to do this sort of stuff.
Also, containers.
From my experience, Anaconda is for doing virtual python environments without thinking about it. They also switched the licensing of their software I believe.
 
I remember having a good experience using poetry but that's for dependency management not entire Python version management. I use source compilation and /usr/local for R but don't know how good it is for Python. Seems like it would be totally inadequate for managing multiple versions.
 
Looks like there's a thing called "pyenv" to help automagically do python versions, like a venv but for a python version.
Also, Conda/Miniconda, which appears to be shit to me, but is designed to do this sort of stuff.
Also, containers.
From my experience, Anaconda is for doing virtual python environments without thinking about it. They also switched the licensing of their software I believe.
Some Debian distros (in my case, Ubuntu 22.04, I'm not jumping to 24.04 immediately) have outdated Python repos; not just the system version but the optional next version up is severely outdated, Python 3.11.0.

To my understanding, my options are to compile from source, trust the Deadsnakes repo, or jump through hoops with a version manager tool.

These all seem like security risks, pains in the ass, or both.

Am I missing something obvious?

This is the first time I hands down unequivocally miss the Windows way of doing things: go to the Python website, download an installer for the desired version, and go.
I wouldn't use anaconda for anything outside of scientific computing, its also frustratingly slow and contains 150 other packages including R. I've used pipx to run isolated applications (not for dev). According to stackexchange
Note: Please don't change the default version of python3. You may end up destroying Ubuntu. Instead, run python3.9 with the command python3.9.
Also, you can install python 3.9.5 in Ubuntu 20.04 even without the deadsnake PPA with the commands
sudo add-apt-repository universe
sudo apt update
sudo apt install python3.9

For other versions of Ubuntu (e.g. 22.04), you may need the deadsnakes ppa.
sudo add-apt-repository ppa:deadsnakes/ppa
sudo apt install python3.9
1717083466333.png
 
  • Feels
Reactions: Lord Xenu
I have this weird audio issue on Endeavour, sometimes if I pause a YT video or a game and come back a few minutes later, there's a crackling/static sound and then it works fine again. Is there a way to fix that shit (forever)?
 
I have this weird audio issue on Endeavour, sometimes if I pause a YT video or a game and come back a few minutes later, there's a crackling/static sound and then it works fine again. Is there a way to fix that shit (forever)?
Dunno, but I've noticed something similar with games running on WINE/Proton.
 
Could I get some opinions on atomic distros for beginners? I want to start learning how to Linux and hopefully make it my everyday OS outside of certain gaming situations. I'm intrigued by Fedora Kinoite and the universal blue Aurora and bazzite images.

It would appear to me that atomic is the way of the future. Since I have no Linux experience, would it be best to go with atomic and learn flatpak, boxes and rpm-ostree as last resort or should I go with a traditional system? My understanding is the traditional system would probably be easier and more straightforward. But maybe it would best for me to learn my way the atomic workflow now instead of having to learn later on down the road?
 
Could I get some opinions on atomic distros for beginners? I want to start learning how to Linux and hopefully make it my everyday OS outside of certain gaming situations. I'm intrigued by Fedora Kinoite and the universal blue Aurora and bazzite images.

It would appear to me that atomic is the way of the future. Since I have no Linux experience, would it be best to go with atomic and learn flatpak, boxes and rpm-ostree as last resort or should I go with a traditional system? My understanding is the traditional system would probably be easier and more straightforward. But maybe it would best for me to learn my way the atomic workflow now instead of having to learn later on down the road?
Start with a normal distro like Mint or Fedora Workstation. Acquire a lot of knowledge before jumping to those, as they're harder.

Like for example I hopped from Ubuntu to Manjaro to Fedora to Arch before finally settling on NixOS. That journey definitely helped me.

And yeah, I'd recommend NixOS over any other atomic distro.
 
  • Like
Reactions: Susanna
Back