[digikam] [Bug 313506] New: erasing files should be an independent process in digeKam

[Axel Krebs]

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

            Bug ID: 313506
           Summary: erasing files should be an independent process in
                    digeKam
    Classification: Unclassified
           Product: digikam
           Version: 2.8.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

Sometimes, there are many processes going on simultaneously. If these are kept
as individual processes, they can be treate (and stopped!) as single entities.


Reproducible: Always

Steps to Reproduce:
1. when running several processes, files erasing does not apppear as an
independent processes
2. erasing does not appear at all as a process
3.
Actual Results:  
unfortunately, there is no way within digiKam to stop  running deleting process
at all

Expected Results:  
Deleting should be kept carefully as an individual process.
Only in this case (??), the process can be stopped as a single task, without
"killing" digikam completely. in this case, the integrity of digiKam database
could be indangered.

--
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

[Smit Mehta]

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

Smit Mehta <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
         Resolution|---                         |INVALID

--- Comment #1 from Smit Mehta <[hidden email]> ---
Hi Axel

Deleting pics is a KDE's routine. digiKam just calls the API. You must have
noticed, when you delete the pics, your KDE's system tray will show you a
notification of a process which indicates deletion of pictures. You can stop
them from there. You dont need to "kill" digikam for stopping it.

@Gilles, I am closing this bug. Reopen it if you feel something is supposed to
be done here.

Smit

--
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

[Axel Krebs]

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

--- Comment #2 from Axel Krebs <[hidden email]> ---
hi Smit:

does this mean, that other processes, as given in service manager e.g.,
are digiKam internal processes?

Hmm... ?!


Thanks, Axel

, Am 20.01.2013 19:12, schrieb Smit Mehta:

> https://bugs.kde.org/show_bug.cgi?id=313506
>
> Smit Mehta <[hidden email]> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>                  CC|                            |[hidden email]
>          Resolution|---                         |INVALID
>
> --- Comment #1 from Smit Mehta <[hidden email]> ---
> Hi Axel
>
> Deleting pics is a KDE's routine. digiKam just calls the API. You must have
> noticed, when you delete the pics, your KDE's system tray will show you a
> notification of a process which indicates deletion of pictures. You can stop
> them from there. You dont need to "kill" digikam for stopping it.
>
> @Gilles, I am closing this bug. Reopen it if you feel something is supposed to
> be done here.
>
> Smit
>

--
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

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

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

--- Comment #3 from Gilles Caulier <[hidden email]> ---
Smit, closing as invalid is fine...

--
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

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Database

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

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|erasing files should be an  |erasing files should be an
                   |independent process in      |independent process in
                   |digeKam                     |digKam
          Component|Database                    |Database-Trash
         Resolution|INVALID                     |FIXED
   Version Fixed In|                            |5.7.0

--- Comment #4 from [hidden email] ---
Since digiKam 5.0.0 we have an independent database trash management with a
dedicated trash album  for each collection. The low level file processing with
trash is don through a multi-threaded interface.

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