• Septimaeus@infosec.pub
    link
    fedilink
    English
    arrow-up
    3
    ·
    13 hours ago

    And you’d be technically correct, the best kind of correct.

    To the inquisitor:

    any distro that’s fully OSS can be fully compiled from scratch with any modifications you choose).

    Though yes, if you’re still using Windows, the learning curve may look like a wall.

    I really want to know what they changed to break the clipboard service

    Guessing the X11 [X]Wayland migration KDE Plasma bug report? Should be fixed in 6.5.2.

    • DevDave@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 hours ago

      Adjacent comment. I’ve found working in a true posix environment is drastically better than the oddities I dealt with Win32. One annoyance is Microsoft has never been able to implement fork().

      Though i never messed with x11 as I was never motivated to see what it was like under the figurative hood.

      • Septimaeus@infosec.pub
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 hours ago

        It really is a hell of a lot more sane, instantly missed once you don’t have it. And yeah Fork’s a blessing when used with care lol

    • DevDave@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 hours ago

      Sorry, switched contexts there. Microsoft broke their clipboard service recently which makes me think they added “telemetry” collecting logic somewhere in there.

      • Septimaeus@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 hours ago

        Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything.

        • DevDave@piefed.social
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 hours ago

          From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a “quick patch” to legacy code.