[Bug 281270] New: KDE's files copying dialog show wrong information.

Alexander vo.zaeb at gmail.com
Sat Sep 3 15:01:14 BST 2011


https://bugs.kde.org/show_bug.cgi?id=281270

           Summary: KDE's files copying dialog show wrong information.
           Product: kde
           Version: 4.7
          Platform: Archlinux Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: vo.zaeb at gmail.com


Version:           4.7 (using KDE 4.7.0) 
OS:                Linux

All going fine when I copy files from my USB device and the problem occurs only
when I copy files TO it. The KDE's notification shows that copying speed is
about 50Mb/s (yes, namely megabytes), so it is about 400 megabits per second
and it is too fast for a full-speed USB device (12MB/s is maximum for USB 1.1).

Alan Stern, one of the kernel developers, described to me what actually
happens. The problem is in that actually it show the speed with which files are
copied into the RAM (it could be even faster if the HDD allow it), therefore it
shows that the copying operation is finished when it has not even been started.
Also when target files are too small the "operation progress" popup will not
appears at all.

Reproducible: Always

Steps to Reproduce:
Plug in any USB device and try to send any files to it.

Actual Results:  
The operation progress show the progress but for the wrong operation. It also
doesn't give me a possibility to pause/cancel the operation.

Expected Results:  
The operation progress notification should display actual data transfer
progress and should also allow to user to pause/stop the operation.

https://bugzilla.kernel.org/show_bug.cgi?id=41472#c7
> Yes, the information displayed in the progress window is off. This really
> isn't a kernel problem so much as a problem in KDE.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list