yes, it’s a rant. I don’t care.

Back in the days drag and drop was working perfectly fine, but now it’s a pain to use. I just installed mkvtoolnix dropped two files into it and it worked. Wanted to add another one and it didn’t. Guess it’s because it’s in a network share and for some reason that matters. Adding the file via the menu works though wtf? Reinstalled mkvtoolnix. Now natively instead of flatpack and now dropping from the network share works, too. Guess it’s some sandbox permission thing and who doesn’t love fiddling with permissions on a weekend.

Btw dropping a file into the file open dialog window also does not work when the program is installed as flatpack. Try explaining that to your mom and then think about why most people think linux is to complicated.

Also remember how you could drop a file instead of pasting its path? I just tried that to add the path of a video into a text file and it inserted the video into the text. Of course it froze the text editor. Great.

Also way too many times firefox opens a file then I drop it in instead of uploading it to the cloud storage I have opened and unzipping files by dragging them out of the archive manager is not possible for the last couple of years.

Honestly I don’t care about workarounds or if it’s a wayland, grnome or flatpack problem. These are basic functionality that I expect to just work

  • vort3@lemmy.ml
    link
    fedilink
    arrow-up
    8
    arrow-down
    9
    ·
    6 hours ago

    Flatpak:

    Sucks

    User:

    Comes to linux community to complain

    Maybe try submitting an issue to flatpak devs, contribute to it, or stop using it if it doesn’t work for you?

    I never used flatpak and have no issues with drag and drop.

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

      Try explaining that to your mom and then think about why most people think linux is to complicated.

    • Ŝan • 𐑖ƨɤ@piefed.zip
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      5
      ·
      6 hours ago

      Don’t rule out Wayland potentially being part of þe problem. Wayland’s security model comes wiþ trade-offs. Maybe someday all þe kinks will be worked out, but þe Wayland security-first design decision has caused many issues for Wayland users wiþ functions like screen savers and clipboards over þe years, and any inter-app or global service process communication is a potential area for quirky behavior.

      • pinball_wizard@lemmy.zip
        link
        fedilink
        arrow-up
        3
        ·
        4 hours ago

        Wayland’s security model comes wiþ trade-offs.

        I try not to be too quick to blame the security nerds, because I’m afraid they will shut off my access. (I joke. I love you all…and please don’t shut off my access.)

        But it is probably the security nerd stuff. (Thank you for keeping me safe, security nerds.)

    • marius@feddit.orgOP
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      6 hours ago

      I don’t know if that’s really the way to go. I don’t even know if it’s a flatpack issue. Maybe it’s just this one program and the developer packaged it wrong. The archive manager is not a flatpack, so maybe it’s a completely different issue there or the same one and it’s unrelated to flatpacks at all. I have now idea and I should not have to, because, as I said, it’s a basic feature that worked for years and should still just do.