Created attachment 121635 [details] screenshot during sync / at the end SUMMARY attempt to synchronize 2 Thunderbird folders of 10 GB on 2 different DDs. Recursive, ignore date, by contents ignore case, display =>, <=, #, duplicate. Krusader mills a few minutes and stops with message "result 0 files" STEPS TO REPRODUCE 1. restart sync 2. 3. OBSERVED RESULT no sync of yet different files EXPECTED RESULT display different folders. display command synchronize or quit SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.5.5 Qt Version: 5.5.1 noyau 4.4.0-154 généric OS 64 bits ADDITIONAL INFORMATION LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial
same malfunction with or without duplicates. Always worked so far with smaller directories
If you are using (K)Ubuntu 16.04.6, then are you using Krusader 2.4.0~beta3? In that case, the aforementioned version is no longer supported. Can you try using a new version of Krusader? In order to use the git version of Krusader there are instructions in https://commits.kde.org/krusader?path=INSTALL
Thank you Toni I do not understand what the link says you gave me. I will rather update my Kubuntu version in 19.04. And I will retry the synchronization. Best regards
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Created attachment 122109 [details] attachment-4212-0.html Bonjour à tous j'ai mis à jour Kubuntu 16.04 => 18.04. Le bug persiste. J'ai terminé les essais hier et je vais mettre mettre le site à jour dans les heures suivantes. Merci Meilleures salutations Hello everyone I updated Kubuntu 16.04 => 18.04. The bug persists. I finished the tests yesterday and I am going to put update the site in the following hours. Thank you Best regards Daniel Le 14/08/2019 à 06:33, Bug Janitor Service a écrit : > https://bugs.kde.org/show_bug.cgi?id=410006 > > --- Comment #4 from Bug Janitor Service <bug-janitor@kde.org> --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! >
Thanks for the update; changing status.
Created attachment 122203 [details] .tar screen prints file description of malfunctions
Hello dear debugger I put Kubuntu in version 18.04. Krusader Version 2.6.0 "Stiff Challenges" plasma 5.12.8 KDE frameWorks 5.44.0 QT 5.9.5 Core 4.15.0.58 Generic μP 2xAMD Athlon II X2 250 Mem 5.8 GB I describe the propleme using screen prints that I comment below. Tell me if I have to do other manipulations. [X] = image number [1] start comparison.jpg [2] comparison in progress. The charge of the hearts of the μP ~ identical.jpg [3] comparison in progress. red files # different.jpg okay [4] comparison in progress. missing files or # .jpg same names but different sizes. comparison choice: ignore the different date. OKAY) [5] comparison in progress loading the hearts of the μP # .jpg [6] example of different marked files (in red) but Kdiff says binary identical.jpg => Malfunction? [7] comparison completed μ at rest.jpg [8] synchro waiting to start.jpg [9] 2 identical photos source destination ??. Jpg The destinationdir is a copy of the source directory; it is not possible to have 2 identical files. I did not think to check with Kdiff in every directory. [10] choice renomination.jpg I chose to give a new name and applied to all [11] validated renaming: krusader crash.jpg Krusader crash.