[digikam] [Bug 372482] New: Empty album view during thumbnails re-creation

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372482] New: Empty album view during thumbnails re-creation

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372482

            Bug ID: 372482
           Summary: Empty album view during thumbnails re-creation
           Product: digikam
           Version: 5.3.0
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Maintenance
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

During the thumbnail re-creation job launched from maintenance, if you navigate
the album the thumbnails are not loaded, resulting in empty view (also if the
album is not involved in the re-creation)

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372482] Empty album view during thumbnails re-creation

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372482

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from [hidden email] ---
The thumbnails database is certainly locked while maintenance tool...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372482] Empty album view during thumbnails re-creation

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372482

--- Comment #2 from Stefano <[hidden email]> ---
Uhm, a background operation that makes the app unusable is a bit odd to me.
Being the thumbs container a database, I don't see the point in locking it, it
can be read and written at the same time by definition and a conflict on the
same record can be handled by the maintenance job itself.

--
You are receiving this mail because:
You are the assignee for the bug.