[Bug 176152] cancelling massive konqueror file operations does not cause konqueror to properly cease disk operations

[N7DR]

Public bug reported:

Binary package hint: konqueror

This is in gutsy, but was in dapper (and presumably every release in
between).

1. Create a large file hierarchy (by "large", I mean one that contains
hundreds of thousands of directories and a million or more files).

2. Using konqueror, initiate a copy of the entire hierarchy to another
destination.

3. After a while, hit cancel. (konqueror takes forever even to figure
out what to copy, but that's a different bug)

4. konqueror will *appear* to have ceased the operation after you hit
"cancel". At this point you can even quit konqueror and it will *appear*
to close.

5. However, konqueror will continue to perform disk operations for many
hours. Running "top" confirms that the process consuming the CPU time is
konqueror; and the hard drive stays continuously lit.

This is completely reproducible.

(Running amd64 gutsy on a dual-core machine.)

** Affects: kdebase (Ubuntu)
     Importance: Undecided
         Status: New

-- 
cancelling massive konqueror file operations does not cause konqueror to properly cease disk operations
https://bugs.launchpad.net/bugs/176152
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kdebase in ubuntu.