• azvasKvklenko@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    9 hours ago

    I really wish they replaced KIO with something new or make it actually mount network shares similar to gvfs, this is ridiculous it’s still like that after all those years

    • kshade@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      4 hours ago

      It’s one of the main reasons I decided not to use KDE for Linux trials at my workplace. KDE applications can use KIO with network shares and it’s actually pretty great, but I/we can’t stay strictly within the KDE ecosystem. GVFS is great because it provides a fallback, even for the terminal. KIO used to be able to do this too, through a GVFS compatibility layer, but development on that feature stopped.

      So we’re doing Cinnamon, all the Windows-like familiarity of KDE and some of the stuff from Gnome/GTK that are just better there. Hope they can reach their Wayland goals this year though, no fraction scaling is pretty bad for some laptops. On the other hand, those displays shouldn’t exist in the first place…

      • azvasKvklenko@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        19 minutes ago

        It’s not that it’s complete dealbreaker. I manage network shares on my own via fstab and it’s fine, just not very user friendly.

        Besides, what do you mean no fractional scaling? It’s supported since 6.0 and improved significantly since then with more improvements to come. Even Firefox now handles it very well (in my use). I have good time even with weird scaling factors like 180%, 155% etc

    • thatKamGuy@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      8 hours ago

      If this is the same issue as what Elijah experienced on LTT’s most recent Linux Challenge video - the. I believe the KDE developers are (finally?) acting to fix this functionality.

      • kshade@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        4 hours ago

        I think what happened there is that the share is anonymously readable, but not writeable. So he could connect to smb://srv/share and it seemed to work, but what was actually needed is smb://user@srv/share - hard to diagnose the issue just from the video though.