[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated it is closed

[Luke Horwell]

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

--- Comment #40 from Luke Horwell <code at horwell.me> ---
> Hmm, these seem broken too. :/ What a mess. I'm wondering if it might make more sense to revert the original change that caused this. Does anyone happen to know what it was?

I don't know the exact commit, but a known good version was around 01 Jun 2021,
(according to my snapshot Arch VM), running:
- Plasma 5.21.5
- Frameworks 5.82.0
- Gear 20.04.1

(It could be between 01 Jun 2021 - 12 Aug 2021, I haven't kept snapshots
between those dates. This VM uses X11)

The "close window aborts extraction crash" bug started when KDE Gear 21.08.0
was released around 13 Aug 2021. I observe the compression happens inside the
'dolphin' process, which was a separate 'ark' process before this update.

The "cancel notification continues extracting" bug is actually even older. It
happens in Plasma 5.21.5. I can see that the ark process keeps doing its thing
despite the notification being cancelled, so I think that's an ark bug, not
dolphin. The process happens inside 'dolphin' now, so that can be a bit
confusing.

Finally, the "new window/tab after extraction/compression" (this original bug
report) started around Plasma 5.22, Frameworks 5.84.0, Gear 21.08.0. I also
confirm that in earlier versions, leaving "Open new folders in tabs" checked
didn't open anything -- so an earlier variant of the regression -- but it
currently open tabs too, I believe.

Just now, I checked "Open new folders in tabs", extracted a zip and it focused
a completely irrelevant instance of dolphin without opening a new tab. I have
this unchecked normally. This might be an incentive to ditch the "steal the
focus" behaviour as mentioned in comment 31 if a clean revert is not possible.

I tried a git bisect on dolphin's repo too the other day, with no luck... only
now I just realized the problem is not exclusive to dolphin's code. It may
involve ark and kio too. Hope this helps.

-- 
You are receiving this mail because:
You are on the CC list for the bug.