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 605085 - creating a filesystems gives no progress, remaining time
creating a filesystems gives no progress, remaining time
Status: RESOLVED NOTGNOME
Product: gnome-disk-utility
Classification: Core
Component: Disks UI
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2009-12-20 19:49 UTC by Lars Wirzenius
Modified: 2012-11-12 21:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lars Wirzenius 2009-12-20 19:49:08 UTC
When creating a filesystem, palimpsest seems to give no indication of progress or remaining time. There is a spinning wheel that keeps rotation, which indicates it has not crashed, but there is no way for the user to know how far it has reached, or how long it will still take.

In my specific case, I am creating an ext4 filesystem on an encrypted partition on a terabyte-sized USB hard drive. I expect it to take a long time, but I would like to know if I should wait for a few more minutes or go sleep.

mke2fs does provide progress indication.
Comment 1 David Zeuthen (not reading bugmail) 2012-11-12 21:17:02 UTC
All the interfaces for this are in place, see

 http://people.freedesktop.org/~david/gnome-disks-long-running-operations.png
 http://udisks.freedesktop.org/docs/latest/gdbus-org.freedesktop.UDisks2.Job.html

what is needed is "just" to hook up udisks to use it. So closing NOTGNOME.

Thanks for taking the time to report this bug.
However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!