Version: Version 1.1.80 Using KDE 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 76.3" (using Devel) Installed from: Compiled sources 1) Find a directory containing some large files that will take at least 15 seconds to copy. 2) In Dolphin, select all the files to be copied, and select Copy. 3) Go to another directory (preferably an empty test directory) and select Paste. Actual behavior: The file-copy progress popup is displayed for a few seconds and then it disappears, nowhere to be found. The file copy operation will continue with no indication of what is happening. This is very disconcerting. Desired behavior: The file-copy progress popup should be visible as long as the copy operation is in progress.
"Installed from" is wrong: should be SUSE RPM:s.
Created attachment 30525 [details] Screenshot of multiple progress dialogs If I repeat the operation I will see two progress popups: one about the current operation (good) and one about the finished operation (unwanted).
You need to click the "computer-like" icon in the system tray plasmoid to get the file-operations progress info again (at least for another secs). I think the auto-hide feature will gain more configuration in KDE4.3
I don't think that is obvious at all. The icon makes me think of display settings, and I don't want to click on icons I don't know about. I notice that this icon does not have a mouse-over tooltip like the other icons in the system tray - a tooltip would have helped. And how do I get rid of left-over copy progress popups from previous copy operations?
The icon image is gonna be changed and the behaviour be improved. However that icon should have a different background. If it doesn't have it , it's fault of your Plasma Theme (may be it isn't updated). Using "Oxygen" as Plasma Theme, you will notice the different background for that "icon". The finished file operation dialogs should be automatically removed from there (however there is another bug report for that not working some times... not sure why) Thanks
I do hope it will be done before 4.2.
*** This bug has been marked as a duplicate of bug 177708 ***