So, I finally decided, after years of putting it off, to try out Linux, specifically Pop_OS. I was waiting for another SSD so it would live on its own hard drive on my computer. Today it arrives.

I first heard about it from Emily (I hope this doesn’t offend anyone, just adding for clarity in case some aren’t aware, but formerly Anthony before her transition) on Linus Tech Tips a long time ago. It seemed like an interesting OS, but being the hater of change I am (ironic that I just made a huge change dropping Reddit and love it so far), I kept telling myself, “Yeah yeah yeah, I will try Linux at some point.”

So, does anyone else using Pop_OS have any advice for setting it up that isn’t in the online docs?

  • Nyanix@dataterm.digital
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    Congrats on your jump! May your move be a positive one!
    I’m on the Arch side of things and don’t touch Gnome a whole lot, so I probably won’t be a lot of help, but one thing I might suggest is to be prepared for the sheer modularity of it all. It’s no longer a Windows issue, likewise, it’s not generally a Pop_OS issue, it’s a specific app’s issue. If your desktop misbehaves, it’s likely Gnome (or Gnome extensions), if games aren’t loading in general, it’s probably Proton/Wine. I say this because it helps immensely to narrow down where an issue or incompatibility lies.

    The modularity also has some really cool benefits to it though! If you find that you don’t like your file explorer, install a different one. If you find that you prefer Plasma’s customization but not ready to make a leap off of Gnome, install it alongside Gnome so you can try it out and see what you like or don’t like about it.

    The other thing I’d suggest is to be ready to rewire your brain on what apps you default to, just like you’re doing with Lemmy & Reddit, but on a mass scale. It can be subtle differences like gNotes vs. Notepad, or as extreme as Krita vs. Photoshop. Getting familiar with the FOSS replacements for many of the common apps that you use will take you much further than trying to get familiar Windows apps to work on Linux.

    Gaming: There’s a lot to learn, but if you take it bites at a time, it’ll make sense. Start with games on Steam, play some Windows games on Linux, note how freaking cool that is. Start to make use of ProtonDB.com to make some games work that might not out of the box, or optimize games you currently have working based on people’s suggestions.
    Small jump, ProtonUp, here you can install various runners, compatibility tools, and get your hands messy with the runner side of things. While I don’t need ProtonUp very often, understanding runners can be invaluable, since you might benefit from using a GE version, or take for instance, when Overwatch 2 came out, it wouldn’t run on Wine, but you could copy the runner from Bottles into Lutris and play off of that.
    Then the big leap: Lutris and Bottles. These two are fairly similar, Lutris is predominantly for games that aren’t in Steam, and Bottles is generally for applications. I use Bottles very little, because using Linux stuff on Linux will always treat you better than trying to get a Windows thing to work on Linux. Lutris has scripts to help install games for you, but its interface allows for more exploring what those properties on ProtonDB actually are and what they do for you. At this point, you can customize some of the compatibility tools to fit your liking or contribute back to others so they can also play things that may not already have a premade script.

    Last and certainly not least: 3 expectations \

    1. Be ready to be a self starter: if things go wrong, be ready to read some (fabulously written) documentation, pulling up some (well organized) logs, and doing some good old fashioned research. \
    2. Do not be afraid to reach out for help: The Linux community is a passionate one that wants to see others thrive in it. If you have issues with Lutris, why not hop on their discord and get help directly from them for free? Most paid services (Windows) don’t even offer that kind of support! \
    3. People are people. I know this sounds obvious, but while Linux is fantastic and its community is wonderful, try not to take it personally if someone’s difficult. Most people that support the Linux ecosphere are volunteers, they’re not paid, some of them are really not good with people, and there’s always a lot to do. Be patient with folks, temper expectations, and be ready to get your hands dirty with your computer, because while someone might be able to help guide you, it’s going to be you pushing the buttons.

      Congrats again, my friend, and welcome to a big new world <3
    • socphoenix
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      To add to this, unlike windows if an app crashes it will give you a real error log. Taking that and googling to error will likely give you a fix in the first few google hits.

      I moved to Debian (then FreeBSD though that’s a different story) after about 30 seconds of using windows Vista. The OS has gotten much easier to install and use, really plug and play at this point and finding solutions to errors is way easier than windows nowadays. Most important is to ask if there’s questions, and provide what information you can.

      • tumulus_scrolls@lemmy.fmhy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        To add even more, to get the real error log you often have to go to console (GNOME terminal) and run the program from here (command name + enter). It will crash and leave the message you can copy. Not that different from Powershell in windows.

        How to know the command name? In KDE you right click the program in the app menu (it’s called Activities in GNOME as far as I remember) and go to “Edit program”, where it is in the text field. For example to run Firefox, you run “firefox” from the console. People can correct me about how it works in GNOME and if there are easier ways. I’ve often tried to guess it, lol. Not only experts use Linux.