• FauxLiving@lemmy.world
    link
    fedilink
    arrow-up
    22
    ·
    1 day ago

    I do the typical Arch troubleshooting, wait a few hours and then yay -Syu and pray they’ve released a patch.

    • Admetus@sopuli.xyz
      link
      fedilink
      arrow-up
      3
      ·
      8 hours ago

      Reminds me of an alias error in building a package on AUR. By 1am I was done looking for solutions. In the morning, lo and behold, an AUR update revealed a new package released at 3am prior to fix the alias error.

  • Ulrich@feddit.org
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    20
    ·
    1 day ago
    1. Web search it
    2. Read a bunch of technical gibberish and terminal commands
    3. Type them in
    4. Some kind of generic error
    5. Go back to using my Mac
    • Luccus@feddit.org
      link
      fedilink
      arrow-up
      1
      ·
      39 minutes ago

      I once had a problem with an ASUS notebook. I think it was the touchpad. So I looked in dmesg and found something like:

      “HID something something was configured with flag 1. If this is incorrect, try the command blah blah flag=0.”

      Ran the command and it was fixed.

      I’ve never seen such a beautiful error in Windows. And I really lost my respect when I tried to calibrate an external screen on a Mac because that felt like Linux from 2016.