https://bugs.kde.org/show_bug.cgi?id=351603
Bug ID: 351603 Summary: Splash screen hangs and disappears when loading network albums Product: digikam Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: [hidden email] Reporter: [hidden email] Dear All, I'm using a network share (samba) to store all my photos (over 20,000 in 200 directories). When I indicate to Digikam the path to this share as one of my album locations, the "findNewItems" process starts. I can see that digikam is busy with referencing all the new images in its database but it seems to take ages and there is no progress bar. After 15 minutes I give up because I have no indication that this process will end successfully somehow. If I restart the program from there, the splash screen will just hang and if I click on it, it disappears. The digikam process is still running though but nothing indicates to the user what is the progress on that task. I think that a good idea would be to show a popup window with the proress of the findNewItems task. If the user interrupts this task by closing the popup window, digikam will restart its database synchronization next time your restart. Cheers, Fred Reproducible: Always Steps to Reproduce: 1. Add a network share to the digikam album paths (preferably over 10,000 photos) 2. Restart Digikam 3. Wait and/or click on the splash screen Actual Results: The splash screen disappears. The program hangs in this state for more than 30 minutes. Expected Results: Show a progress dialog on the scanning of the network share -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
https://bugs.kde.org/show_bug.cgi?id=351603
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] Status|UNCONFIRMED |RESOLVED Resolution|--- |BACKTRACE --- Comment #1 from Gilles Caulier <[hidden email]> --- We need a GDB backtrace to investiguate. Please follow instructions here : https://www.digikam.org/contrib -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Frédéric
https://bugs.kde.org/show_bug.cgi?id=351603
Frédéric <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |wishlist -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Frédéric
https://bugs.kde.org/show_bug.cgi?id=351603
Frédéric <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|BACKTRACE |--- Status|RESOLVED |UNCONFIRMED --- Comment #2 from Frédéric <[hidden email]> --- Gilles, The program doesn't actually crash, it just hangs endlessly. My report is more a wishlist to have a progress dialog. Fred -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Frédéric
https://bugs.kde.org/show_bug.cgi?id=351603
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |BACKTRACE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Gilles Caulier <[hidden email]> --- On https://www.digikam.org/contrib, there is a way to get information from the console while hang out problem. The startup run in separated thread. crash in thread can be a reason of the problem. Running digiKam in GDB will indicate where the crash appears. Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Frédéric
https://bugs.kde.org/show_bug.cgi?id=351603
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|general |Database-Scan Resolution|BACKTRACE |FIXED Version Fixed In| |5.1.0 --- Comment #4 from [hidden email] --- With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Frédéric
https://bugs.kde.org/show_bug.cgi?id=351603
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Database-Scan |Database-Media -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |