Bug 377515 - Ark quits after drag/dropping single file
Summary: Ark quits after drag/dropping single file
Status: CONFIRMED
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Elvis Angelaccio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-12 09:58 UTC by Fabian Vogt
Modified: 2019-02-17 19:43 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Vogt 2017-03-12 09:58:09 UTC
When the "Quit after extract" option is set, ark also quits after dropping a single file in dolphin, for example.
Comment 1 Elvis Angelaccio 2017-03-12 11:01:32 UTC
I'm not sure what to do here. If we always prevent ark from quitting after a drop, we could break someone else's workflow. Maybe we should make the option more fine grained, to allow choosing whether to quit also after drop extractions.

Partially related: after a drop extraction the "Open destination folder after extraction" is also honored, and this is surely a bug (doesn't make any sense to open Dolphin if I just dropped onto Dolphin itself or Folder View).
Comment 2 Viorel-Cătălin Răpițeanu 2019-02-12 15:09:44 UTC
I wasn't able to reproduce this issue when using the master version of Ark and KDE Framework.
Comment 3 Elvis Angelaccio 2019-02-16 13:48:12 UTC
(In reply to Viorel-Cătălin Răpițeanu from comment #2)
> I wasn't able to reproduce this issue when using the master version of Ark
> and KDE Framework.

Did you set the "Quit after extract" option?
Comment 4 Patrick Silva 2019-02-17 19:16:20 UTC
I can reproduce with Ark 18.12.2 on Arch linux when "Close Ark after extraction" is checked in preferences.
Comment 5 Viorel-Cătălin Răpițeanu 2019-02-17 19:42:52 UTC
(In reply to Patrick Silva from comment #4)
> I can reproduce with Ark 18.12.2 on Arch linux when "Close Ark after
> extraction" is checked in preferences.

I misread the ticket. The behavior described is indeed reproducing. Sorry about this.