After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 590071 - Show progress of single file operation in title bar
Show progress of single file operation in title bar
Status: RESOLVED DUPLICATE of bug 584530
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.27.x
Other All
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-28 21:39 UTC by Philip Muskovac
Modified: 2010-07-14 08:24 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Philip Muskovac 2009-07-28 21:39:55 UTC 
This was originally filed as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/384568

It's not exactly a bug but rather a feature which would greatly improve convenience for long file operations like copying large files.

My suggestion is to display actual percentage in the title bar like "50% - File operations" when there's only one operation being performed (which is in 99% the case). This way you could watch the progress even when this not-so-useful window is minimized.

The same applies to tray icon hint which now reports only number of operations taking place (which is not relevant most of the time because it's "1").

Another feature which might be very useful is to report long operation completion (if it took longer than, say, 30 seconds) with standard Ubuntu notification. Now you may not notice the operation has ended for only the (possibly background) window closes.
Comment 1 Matthijs Wensveen 2009-12-01 22:33:37 UTC 
Is this a dupe of #584530? Any way, #584530, #546949 and this bug are closely related.
Comment 2 Allan Day 2010-07-14 08:24:58 UTC 
(In reply to comment #1)
> Is this a dupe of #584530?

Yes, good catch! :) Closing as a dupe. Thanks for the bug report.

*** This bug has been marked as a duplicate of bug 584530 ***