No dialog telling the user the indexing of files is in progress

[Loe Spee]

Ubuntu 6.06 Dapper Drake
Nautilus 2.14.3

Steps to reproduce:
- Insert a blank DVD (I used a DVD+RW)
- Add a lot of files (mine where on a NTFS partition and added up to 4 GB)
- Press the "Write to disc" button
- Wait a while
And creating the ISO starts, followed by burning that ISO to the disc.

What doesn't happen:
It's totally unclear to the user wether the burn process has started yes, if I didn't hear the harddisc make some noise, I would have pressed the "Write to disc" button a few more times.

What should happen:
A dialog should popup with a progressbar (be it finite or infinite) and tell the user Nautilus is busy indexing the files to be burnt (at least I think Nautilus is doing that). And the "Write to disc" button should get disabled.

This way the user gets informed what is going on, and that his/her system is budy indexing, now it seems like Nautilus burning doesn't work. Read chapter 7 of the Gnome HIG (http://developer.gnome.org/projects/gup/hig/), it tells us the user should be notified if something is going to take a little bit longer, so the user doesn't get frustrated.

[Quim Calpe (quimcalpe)]

Agreed,

Writing an ISO right-clicking on the file has the same behavior, in fact, I pressed twice before realizing (via ps) that nautilus-cd-burner was actually doing something (decompressing/indexing/? files inside ISO image?)...

The proposed solution seems doable and the correct expected behavior, so +1 here ;-)

Thanks

[Quim Calpe (quimcalpe)]

Just noticed the bug is also in bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=355889

[Loe Spee (lgespee)]

Quim Calpe, thanks for your reaction.
Indeed it has the same behavious with ISO's.

And indeed it has already been reported upstream ;).

Thanks for the clarification.

[Mario Đanić (mario-danic)]

Do you still experience the same problem in feisty/gutsy?

[Quim Calpe (quimcalpe)]

@Mario: I just tried it in gutsy and the problem seems solved

[Muelli (ubuntu-bugs-auftrags-killer)]

Seems to be fixed as per last comment.