Bug 290334 - Pressing the stop button in the notification applet to stop archive extraction/compression has no effect
Summary: Pressing the stop button in the notification applet to stop archive extractio...
Status: RESOLVED DUPLICATE of bug 287553
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.19
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-01 16:56 UTC by Jesse
Modified: 2012-08-05 23:29 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
snapshot (131.48 KB, image/png)
2012-01-01 16:56 UTC, Jesse 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse 2012-01-01 16:56:46 UTC 
Created attachment 67306 [details]
snapshot

Version:           unspecified (using Devel) 
OS:                Linux

I'm using KDE 4.8 RC1, compiled from sources on Gentoo x64 with Qt 4.8.
While extracting/compressing an archive with ark, pressing the stop button in the plasma notification applet has no effect.
I've attached a screenshot depicting the issue. Even after pressing the stop button, unrar and ark keep running and extraction is continued.

Reproducible: Always

Steps to Reproduce:
1. Select files such that compression duration is large enough to observe the issue.
2. Start ksysguard.
3. Find the processes which are compressing.
4. Press the stop button in the notifier applet.
5. Notice that the processes keep running even though the notifier says "Job canceled by user".

Actual Results:  
Compression/Decompression process is not stopped.

Expected Results:  
Compression/Decompression process should get stopped.
Comment 1 Jesse 2012-02-09 02:41:10 UTC 
Issue persists in 4.8.0.
Comment 2 Elias Probst 2012-05-17 21:02:55 UTC 
I think there are 2 problems here:

1. Ark doesn't listen to the stop request
2. Plasma notifications show the job as stopped, although the client (in this case Ark) didn't stop the job. There needs to be a bi-directional communication regarding stopping the job, not only a fire + forget "stop it".
Comment 3 Martin Koller 2012-08-05 20:47:00 UTC 
In 4.9, the notification I see says "Job canceled by user."
Still ark continues in the background - so this is an ark problem.
reassigning.
Comment 4 Raphael Kubo da Costa 2012-08-05 23:29:53 UTC 

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