Bug 304036 - File transfer complete notification show link to the wrong place
Summary: File transfer complete notification show link to the wrong place
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: notifications (show other bugs)
Version: 4.10.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-25 07:01 UTC by Alexander
Modified: 2018-06-08 19:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2012-07-25 07:01:51 UTC
In case when you copying a few directories/files, notification show the link to the last copied file instead of target directory.

So it should behave different in cases when you copy single file and in case when there are a bunch of files. E.g. with one file it's ok to show the link to that file after operation has been finished, but in case with a lot of files it should show a link to the destination directory.

Reproducible: Always

Steps to Reproduce:
1. Create new folder
2. Copy few directories to it
3. Check the URL that will be displayed in notification
Actual Results:  
URL will point to the file that has been copied at last.

Expected Results:  
URL should point to the destination directory
Comment 1 Martin Koller 2012-08-04 13:38:10 UTC
With current 4.9-git I can not reproduce this.
When I copy some files/folders (e.g. from a fish:// source), the notification which shows the "copying [finished]" text shows the link to the target dir.
Also check bug #241451
Comment 2 Alexander 2012-08-06 07:36:32 UTC
Hi, not sure about the git build, but this is in 4.9.0-1 from Arch Linux testing repository:
http://www.youtube.com/watch?v=4gmfSanskJk

Target directory should be "/home/heaven/Desktop/tmp", but it showed the directory that has been copied at least (my guess) which is not the target dir.

Also, when I clicked on the "open" button it is opened ...I am actually not sure what it was, maybe some of those files it just copied, but even not the one that was showed as a target.

So there even 2 problems:
1. Target directory point to wrong location
2. The "Open" button doesn't open the file/directory displayed as target.

Could it be the bug has been fixed in last 4-6 days in git and not yet applied to the 4.9.0 build?

Best,
Alex.
Comment 3 Myriam Schweingruber 2013-04-12 07:59:04 UTC
Since the Notification widget was replaced with a newer QML-based one, the previous versions are now considered unmaintained. There will be no more code contribution to the older versions.

Please only report bugs and wishes to the new version, available since KDE 4.10
Comment 4 Alexander 2013-04-12 09:20:56 UTC
There are no any difference, the bug is still here and notification is still broken.

Please take a look: http://www.youtube.com/watch?v=aFvWID3f7Jg

After I copied a bunch of files it points to the last copied one (somewhere in in ca-certificates, I can't even see to which one because the path has been truncated with "..."), but should ALWAYS point me to the target directory (named "test" in this example).

It is more likely that user will not leave the window opened if copying process take longer than a few minutes and will close the Dolphin window. When the copying process is done I'd like to click the "browse" button  in notification and look at the destination "target" directory ("test" in this example).

Current behavior is wrong and makes no sense at all.
Comment 5 Nate Graham 2018-06-08 19:48:58 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham