• finkrat@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    8 months ago

    “Why doesn’t this just work I never had this problem on Windows!!” leaves no necessary information to troubleshoot

    Vs.

    “I have this specific and obscure workflow I use with this one package nobody has heard of, I perform XYZ action and after I ran pacman -Syu I’m seeing that the application is segfaulting and leading to this call trace…”

    Five page dump of dmesg

    “I mapped this to line 748 of the Linux-Zen kernel source file can somebody help explain how I can work around this?”

    No responses for eternity, thread archived

  • bbuez@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    ProtonDB comments… at the very least say if you’re using an nvidia or AMD card ffs

    • hamFoilHat@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      The two hardest problems in programming are cache invalidation, naming things, and off by one errors.

  • bisby@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    This was fixed ages ago, but you are using Debian because it is “stable” and thus software from ages ago and don’t have the fix.

    • MyNamesNotRobert@lemmynsfw.com
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      The best part is when I check to see what exact version of the package I really have and despite it being old, it’s the version a month after the one where the bug was fixed but I’m still getting the bug so I guess I’ll go fuck myself then.