Version: 4.3.2 (using Devel) OS: Linux Installed from: Compiled sources when copying or downloading files the line with kbps and remaining time of the single task is missing. only the main remaining time is shown ok in 4.3.1 missing in 4.3.2
Created attachment 37493 [details] copy notification in 4.3.2
This is probably caused by the fix to bug 199346
SVN commit 1043127 by darioandres: - Fix the Speed and ETA of the file transfers not being shown in the Plasma notifications - The applicationjobs dataengine now should notify about speed changes * It should not affect anything else, but it may need more testing... I will investigate to backport to 4.3.x CCBUG: 210081 CCMAIL: aseigo@kde.org M +9 -1 applets/systemtray/ui/jobwidget.cpp M +1 -1 applets/systemtray/ui/jobwidget.h M +2 -0 dataengines/applicationjobs/kuiserverengine.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1043127
SVN commit 1043176 by darioandres: - Small fix to my previous fix (rev. 1043127) : only show ETA and Speed if the job is running (Otherwise, this data will override the "Paused" message setted before.) CCBUG: 210081 CCMAIL: aseigo@kde.org M +8 -6 jobwidget.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1043176
SVN commit 1043183 by darioandres: Backport to 4.3 of: SVN commit 1043127 by darioandres SVN commit 1043176 by darioandres - Fix the Speed and ETA of the file transfers not being shown in the Plasma notifications - The applicationjobs dataengine now should notify about speed changes * The ETA and Speed are only shown if the job is running * It should not affect anything else, but it may need more testing... If this is tested properly, should it be included on the already tagged 4.3.3 builds ? BUG: 210081 CCMAIL: aseigo@kde.org M +10 -0 applets/systemtray/ui/jobwidget.cpp M +1 -1 applets/systemtray/ui/jobwidget.h M +2 -0 dataengines/applicationjobs/kuiserverengine.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1043183
I find the issue existing in 4.3.3 Any proposed version by which this bug will be included in the final build?
It is fixed for 4.4 and 4.3.4 (to be released in two weeks). It wasn't critical enough to patch the current 4.3.3 packages