[kde] [Bug 496518] New: Closing an application that is transferring a file to `trash:/` causes the notification to immediately report success, despite the transferral being cancelled by the closure.

[Roke Julian Lockhart Beedell]

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

            Bug ID: 496518
           Summary: Closing an application that is transferring a file to
                    `trash:/` causes the notification to immediately
                    report success, despite the transferral being
                    cancelled by the closure.
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: 4wy78uwh at rokejulianlockhart.addy.io
  Target Milestone: ---

SUMMARY
-------

Recently, when deleting files, a loading bar would appear in the deletion
notification (despite the fact that I was using BTRFS on a PCIe 5 NVMe SSD). If
I closed the primary window of the application which initiated the deletion,
the notification would immediately report success, despite, upon subsequent
verification, the file having not been transferred to `trash:/`. After
estimating that my 111 GiB `$HOME/.local/share/Trash/` was the reason for the
slowness, I deleted its content, and the slowness was remediated.

However, this demonstrated to me that when using a slow storage device, a user
performing a transferral to `trash:/` must wait until the process has completed
for them to be able to close the application hosting that IO operation. I don't
consider this to be intuitive, because the operation should be a separate
process. Additionally, the notification should not report success (if my
recollection is correct that it does so).

STEPS TO REPRODUCE
------------------

1. Fill the `trash:/` as aforementioned. Mine was 111 GiB *of 1.82 TiB*, so use
a similar ratio, if using similarly quick hardware. Ultimately, you'll know
it's slow enough when you can easily close an application whilst the
transferral remains commencing.
2. Open Dolphin or Gwenview.
3. Delete a file.
4. Cancel the operation whilst it's commencing. You'll know that it's
commencing because the progress bar shall be in an indeterminate state, rather
than a specific progression.

OBSERVED RESULT
---------------

When closing Gwenview or Dolphin whilst the transferral operation was active,
the notification reported success, but was cancelled.

EXPECTED RESULT
---------------

- The notification should report failure if the main application window is
closed.
- Better yet, the operation should be independent of the process which spawned
it.

SOFTWARE/OS VERSIONS
--------------------

> ```YAML
> Operating System: Fedora Linux 41
> KDE Plasma Version: 6.2.3
> KDE Frameworks Version: 6.8.0
> Qt Version: 6.8.0
> Kernel Version: 6.11.8-300.fc41.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
> Memory: 30.4 GiB of RAM
> Graphics Processor: AMD Radeon RX 5700
> Manufacturer: ASRock
> Product Name: X670E Taichi
> ```

ADDITIONAL INFORMATION
----------------------

Unfortunately, I cleared the trash to verify that its size was the problem,
without thinking to record the before and after.

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