When overwriting files, Dolphin doesn’t offer me any information to determine which file version to keep.
How can I fix this? Thank you in advance.
http://s28.postimg.org/b0p3uakah/Dolphin_Dialog.jpg](http://postimg.org/image/b0p3uakah/)
When overwriting files, Dolphin doesn’t offer me any information to determine which file version to keep.
How can I fix this? Thank you in advance.
http://s28.postimg.org/b0p3uakah/Dolphin_Dialog.jpg](http://postimg.org/image/b0p3uakah/)
I do not quite understand your problem.
You tell Dolphin to write the contents of /Vorlagen/Textdatei to /Musik/Textdatei. Dolphin detects that /Musik/Textdatei does already exist. Instead of simply overwriting it (as a CLI command would do) it so kind to report this to you and gives you three possibilities:
Now please explain what you are missing.
By some convoluted magic involving baloo the dialogue previously displayed some of the metadata associated with the source and destination files.
Like this, for example:
http://paste.opensuse.org/view/raw/5424eb6e
There’s a bug report raised already: 356278 – dolphin does not show any file information in copy dialog
In the past the dolphin overwrite/rename dialog gave certain details about the two files like date, size ,etc. which would assist in making a decision. I found this quite helpful.
So i filed those bugs …
https://bugzilla.opensuse.org/show_bug.cgi?id=957959
https://bugs.kde.org/show_bug.cgi?id=356278
… and hope they will be fixed soon. Because without such information a file manager seems quite useless to me.
Best regards
susejunky
Thanks both of you for the explanation. I now do understand better what the OP is missing.
Well, that is my idea for all file managers in general. A lot of fuzz and still nothing usefull (I saw a file manager identifying a GIF file as a JPEG file because the name ended in .jpeg. When it is that easy to fool you, better do not call yourself “file manager.”).
Actually this never was ported to Baloo, the kdelibs4 version always used and still uses Nepomukv1 and strigi.
And that’s probably the reason why it is still missing in KF5.
You could use Konqueror or dolphin4 as file manager instead, those are still KDE4 based and will display that information, but they will not be able to use KF5 service menus and thumbnailers, or communicate with the KF5 based Baloo (i.e. indexed search will not work).
As the others wrote, I’m missing additional informations regarding file size, date et cetera in order to determine which file to keep. Sorry if I didn’t make my point clear enough.
Thanks for filing the bugs reports. Your effort is appreciated.
Thanks for the suggestion, I will use Konqueror.
FYI, basic file details (modification time, size, and a preview) for the file overwrite/rename dialog have been reimplemented for Frameworks 5.20.0 which is going to be released on Saturday.
I don’t know if/when 5.20 will appear as update for Leap 42.1, but you can always get the latest versions from the KDE:Frameworks5 repo.
Additional metadata will require a plugin that uses kfilemetadata though, which doesn’t exist yet.
Thank you very much for the information !
A month ago i received a message from bugzilla that the Bug was closed (resolved) but i could not work out where to get the fix. I use the KDE:Frameworks5 repo with openSUSE 42.1 and will check over the weekend to see if the update arrives and works.
Best regards
susejunky
5.20 is going to be released at some time tomorrow, and will be in the repo then as well.
And yes, it does work. I tested it a few weeks ago already…
The update is in the repo and i just installed it …
… affirmative !!! :good:
Thank you very much!
@potato:
So this should be marked as solved.
Best regards
susejunky
Unfortunately, this causes a regression:
https://bugs.kde.org/show_bug.cgi?id=360488
Therefore the planned update for Leap 42.1 is also blocked for now, until this is fixed.
Good news: this crash is fixed now in the openSUSE package in KDE:Frameworks5…
I just wanted to confirm that this bug has been fixed with the recent update for Leap 42.1 (openSUSE-2016-420). Thanks again to everyone for helping solve this issue*.*