Bug 506641 - Switching to another drive on other panel during "Extract archive here.." starts unarchive to a location at other panel.
Summary: Switching to another drive on other panel during "Extract archive here.." sta...
Status: CONFIRMED
Alias: None
Product: krusader
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.9.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-05 16:04 UTC by Igor Mironchik
Modified: 2025-07-31 07:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Mironchik 2025-07-05 16:04:35 UTC
SUMMARY
Switching to another drive on other panel during "Extract archive here.." starts unarchive to a location at other panel.


STEPS TO REPRODUCE
1. Connect and mount external drive.
2. Download a big archive like qt-everywhere-src-6.9.1.tar.xz
3. Open in one panel folder with this archive.
4. Open in other panel folder on the same drive (let it be the same folder)
5. Start in one panel from context menu "Extract->Extract here" operation.
6. Wait a little.
7. On other panel click "Open the available media list" button.
8. Choose other drive (mounted external).

OBSERVED RESULT
Extracting starts to place files in folder on other panel, external drive.


EXPECTED RESULT
It should be no matter what I do in panels, archive should be extracted to a location where it was started to do.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250702
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.4-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 8 GiB of RAM (7,6 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: HP
Product Name: HP ProBook 640 G3
Comment 1 whiztech 2025-07-31 07:18:38 UTC
Looks similar to my report bug 503888.