Yes, it is definitely a dolphin/Ark integration bug. Even normal Zip compression is not working with the ‘Right Click’ And ‘Compress’ and ‘Compress Here as Zip’.
1 Like
But I have no issue with Zip compression in Dolphin. Only 7z failed. It seems, Dolphin would not be compatible with Ark 21.08.2 after Manjaro update.
The bug described in this thread happens to me regardless of compression method used. Maybe your system as a slightly different config that spares you from seeing this bug manifest when using .zip?
I must add that this is a concerning bug, since I rely heavily on Ark to create “forever archives” of converted media that I store on ZFS and M-Discs. Luckily, I already did most of that prior to these KDE updates.
Yet the uncertainty of reliability when creating permanent, error-free, integral files means I cannot fully trust Ark/Dolphin when working on these projects. That’s not a good feeling at all.
I disabled many features in Dolphin:
That’s why zip compression has no issue?
Edit: I checked it in VM, so Dolphin/Ark has this issue with only 7z. Other compressions are fine.
maybe this was ignored?..
I tracked this issue a bit, the 7z compression is ok in Dolphin, Dolphin and Ark are not fault, but Dolphin’s notication popup is.
The progress bar of any compression in the Dolphin’s notification popup has two bugs:
-
It crashes Dolphin after click Cancel/Stop if any compression is not yet complete, zip too. (Please you can check it)
-
It can’t finish .7z and .jar archives completely when both are 100% done in the progress bar.
This is GUI’s bug.
Please correct me if I am wrong.
What’s the point to do not to submit an individual bug report and to add such additional investigation info as Zecko did, but to post upstream package investigations here? So like guessing process w/ an low energy conversion efficiency instead of precise debugging?
There’s a third one, that I experience occasionally. It’s not as common but it does happen enough that it’s a great concern:
- Compression actually does fail, and no new file is created
(Such a “fail” happens shortly after you try to create a new compressed archive.)
This is what it happens on my side…
2 Likes
I am getting the same result as well.
The announcement page shows just one change for ark.
If this were simply backed out for upcoming 21.08.3 bug fix release, then I suspect our crash would be “fixed”.
If anyone on here has registered to comment on KDE Bugtracking System, then it might be very helpful to point this out to KDE.
1 Like
Good find. Thank you.
I added a comment to KDE’s Bugzilla.
1 Like
If to use ark without Dolphin (to start arc from start menu), than 7z archiving works fine.
It’s complicated and better to make separate bug reports (it is very easy for developers to mark different reports as duplicates but very hard to separate comments of one under-the-hood origin/cause from another in a single comment flow).
About my bug report: probably it took fovere to wait 5.15-rc7 to get more fixed kernel machanisms and to use them in bug report.
Yeah, I know.
True, but it seems they had a bug they “fixed” which gave birth to a new bug. In fact, I’d argue that the original bug they fixed was more of a rushed patch than truly addressing the underlying buggy code.
They went from,
- redundant new Dolphin instances when compressing via the context-menu
- phantom Dolphin processes when compressing via the context-menu
- freeze/crash or unresponsive progress indicator when compressing via the context-menu
Honestly, I lost track and I just hope the devs have it work like it did back in the KDE4 days.
1 Like
Doubt they’re focused much on efficiency in their bug tracker since they use the ancient Bugzilla… it’s a nightmare to navigate, and yet they use Gitlab for merge requests… 
2 Likes
I’m glad someone said it…
1 Like
Guys, we can blame anybody for their environment usage, but if we want a fix, we - on our side - should generate a maximum HQ report as we can. Not like a poems (as I liked before) but precise, short but descriptive with full info which possible need. I blame myself that I still reading how to make a HQ report of KDE component and still did not complete it to switch to submit a report. For now it is a week-long issue for me but I still did not report it.
OFF-TOPIC:
Simplest one I made recently not probably the cleanest one from me: 444350 – Can't to config baloo indexing: balooctl unable to exclude a folder from from included folders list and before it was a year long 429910 – Settings -> File search: Folder specific configuration list: self-reproducing, irremovable items of '/home/<username>' with 'indexed' value
It’s been reported. A debug was attached.