[ark] [Bug 524399] New: Temporary files are not deleted when Ark receives a SIGTERM

Martin <[email protected]>
Newsgroups gmane.comp.kde.devel.bugs
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=524399

            Bug ID: 524399
           Summary: Temporary files are not deleted when Ark receives a
                    SIGTERM
    Classification: Applications
           Product: ark
      Version First 26.04.3
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

DESCRIPTION
When opening an archive (tested with .tzst) and opening a file within it, a
/tmp/ark* directory is created with the extracted file.

When closing Ark, this directory is wiped.

When Ark receives a SIGTERM however, it closes without cleaning up after
itself, leaving files lingering.

STEPS TO REPRODUCE
1. Open a .tzst (or presumably any format) archive with Ark
2. Open a .txt (or presumably any format) file within that archive
3. Observe /tmp/ark* being created
4. Run `killall ark`
5. Observe the tmp directory still being present despite Ark no longer running

OBSERVED RESULT
Files present in /tmp/ark* after SIGTERM

EXPECTED RESULT
No /tmp/ark* when Ark doesn't run anymore

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.8-arch1-3 (64-bit)
Graphics Platform: Wayland
Processors: 16 Ă— AMD Ryzen 7 5800H with Radeon Graphics
Memory: 32 GiB of RAM (27.3 GiB usable)
Graphics Processor 1: AMD Radeon Graphics
Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.