Nemo extracts files from .ARC and .PAK archives and store them in /home/<user>/ instead of storing them in local folder

Open
#3,440 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, linux
Domain
desktop

Research direction

Start by reproducing the behavior with archives.tar.gz, MM34.PAK, and EGACHESS.ARC using the listed /usr/bin/unar and /usr/bin/arc x commands. Trace Nemo's archive-extraction handling for custom applications; done means both archives extract into the folder containing the original archive rather than ~/.

Written by the indexing model from the issue text.

Description

Distribution

Linux Mint Cinnamon 22

Package version

6.2.6

Frequency

Always

Bug description

When extracting files from .ARC or .PAK archives with Nemo, files are stored in ~/ instead of being stored in the same folder than the original archive folder.

Steps to reproduce
  1. Install unar (not unrar) and arc packages.
  2. Download the joined file archives.tar.gz and extract the 2 files MM34.PAK and EGACHESS.ARC from it.
  3. Open MM34.PAK or EGACHESS.ARC with Nemo, to extract files from these archives:
    • Right click on MM34.PAK or on EGACHESS.ARC,
    • Choose "Open with another application",
    • Add this new command in Nemo: '/usr/bin/unar' or '/usr/bin/arc' x
  4. Nemo extracts files from MM34.PAK or from EGACHESS.ARC and store them in /home/<user>/.
Expected behavior

Nemo extracts files from MM34.PAK or EGACHESS.ARC archive and store them in the same folder than the folder where MM34.PAK or EGACHESS.ARC is.

Additional information

Nemo additionnal applications.
userapps.zip

Dominant language
C
Stars
1.6k
Forks
368
Avg merge
4d 4h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo

All issues in linuxmint/nemo

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.