Plasma is great. But it’s missing an important feature. Apps, such as backup or sync, cannot navigate to network shares, to use as a backup target. Dolphin sees the shares ok, but its important to backup. Windows lets apps select network targets. Plasma should too.
Dolphin shows you places that are not in your file system, such as network shares or your phone‘s media directory. Those are fake files, illusions of Satan, temptations designed to stray you from the path of God. Avoid anything that is not opened with open and not read with read system calls, for doing so is a sin before eyes of God (fopen and fread are permitted). Mount your network shares using sudo mount -t cifs.
hear me out. what do you do when the network share server is not always available? like because your system is a laptop, or because you are doing maintenance on your server and its off.
what I do is suffer the consequences of many software that does not handle it well, and freeze for a minute (or worse) when it tries to open the mounted share even when it shouldn’t even try. multiple KDE apps are guilty of that, including dolphin and kate, but to some extent almost everything else too.
but that is not ideal.
It’s a shame Dolphin gets it wrong. I hope that bug has been reported. And I’d love to find a way for non IT users to mount the share as a workaround to the missing functionality. But that’s missing too.
Dolphin does mount it …somewhere. Supposedly. I expect only KDE developers know where exactly.
You can get the same functionality using Gnome file manager and gio command, and you get your network share properly mounted in a file system, but then you won’t be using KDE.
Nice. Kup actually lets me see the Network. But then complains if I select a samba share. There is a popular bug report about this.
I prefer sync backup to access documents directly, instead of kups scrambled backup files.
Plasma is great. But it’s missing an important feature. Apps, such as backup or sync, cannot navigate to network shares, to use as a backup target. Dolphin sees the shares ok, but its important to backup. Windows lets apps select network targets. Plasma should too.
Dolphin shows you places that are not in your file system, such as network shares or your phone‘s media directory. Those are fake files, illusions of Satan, temptations designed to stray you from the path of God. Avoid anything that is not opened with
openand not read withreadsystem calls, for doing so is a sin before eyes of God (fopenandfreadare permitted). Mount your network shares usingsudo mount -t cifs.hear me out. what do you do when the network share server is not always available? like because your system is a laptop, or because you are doing maintenance on your server and its off.
what I do is suffer the consequences of many software that does not handle it well, and freeze for a minute (or worse) when it tries to open the mounted share even when it shouldn’t even try. multiple KDE apps are guilty of that, including dolphin and kate, but to some extent almost everything else too.
but that is not ideal.
It’s a shame Dolphin gets it wrong. I hope that bug has been reported. And I’d love to find a way for non IT users to mount the share as a workaround to the missing functionality. But that’s missing too.
Dolphin does mount it …somewhere. Supposedly. I expect only KDE developers know where exactly. You can get the same functionality using Gnome file manager and
giocommand, and you get your network share properly mounted in a file system, but then you won’t be using KDE.I use Nixos, but my ssh mount and nfs and samba mount can be selected as backup path for kup.
Nice. Kup actually lets me see the Network. But then complains if I select a samba share. There is a popular bug report about this. I prefer sync backup to access documents directly, instead of kups scrambled backup files.