Bug 459394 - When plugins are configured in a certain way in Ark settings, Plasma shows a notification with a unhelpful ping-pong 'progress' bar while a zip archive is extracted
Summary: When plugins are configured in a certain way in Ark settings, Plasma shows a ...
Status: RESOLVED DUPLICATE of bug 382599
Alias: None
Product: ark
Classification: Applications
Component: plugins (show other bugs)
Version: 22.08.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Elvis Angelaccio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-19 13:19 UTC by Patrick Silva
Modified: 2022-10-05 09:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Video showing the unhelpful ping-pong 'progress' bar (126.40 KB, video/webm)
2022-09-19 13:20 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2022-09-19 13:19:49 UTC
STEPS TO REPRODUCE
1. open Ark
2. open Ark settings 
3. click on 'Plugins' in the left side, disable libzip plugin or disable both libzip and info-zip plugins and click on 'OK' button
4. open Dolphin
5. have a zip archive - I tested single volume and multi-volume zip archives on my system
6. extract your zip archive via context menu of Dolphin - I used 'Extract archive here, autodetect subfolder' option

OBSERVED RESULT
while the zip archive is extracted, Plasma shows a notification with the unhelpful ping-pong 'progress' bar
seen in the attached screen recording (in the video I'm creating an archive, but the same 'progress' bar appears after the provided steps).

EXPECTED RESULT
the progress bar should tell us the real progress of the extraction

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.25.90
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Graphics Platform: Wayland
Comment 1 Patrick Silva 2022-09-19 13:20:21 UTC
Created attachment 152220 [details]
Video showing the unhelpful ping-pong 'progress' bar
Comment 2 2wxsy58236r3 2022-10-05 09:07:48 UTC

*** This bug has been marked as a duplicate of bug 382599 ***