show file name while burning image

[Kevin Hunter]

While actually burning an image to a CD/DVD, the there is no mention of *what* file is being written.

Note in the attached screenshot that Brasero doesn't say *what* image it's burning, just that it's burning an image.

I would think that this is a small, hopefully easy change, and it would have saved me 15+ minutes as I was, in fact, burning the wrong image.

[Kevin Hunter (hunteke)]

In this particular case, I had four images, and I started burning one, then forgot which one. I wanted to double check myself to make sure I wasn't on autopilot with the wrong image, and then have wasted the 15+ minutes it takes to write.

[Kevin Hunter (hunteke)]

A further thought ... if normally only make the basename were initially visible, but on some sort of interaction (mouseover? button?) display the complete path name, I'd say that could be helpful as well. I *usually* don't need the complete path name, but it would have been useful a couple of times in the past.

[Kevin Hunter (hunteke)]

Would set priority of this bug to low, but I don't seem to know how, or maybe I don't have the access ...

[Pedro Villavicencio (pedro)]

thanks for the report, is this with jaunty?

[Kevin Hunter (hunteke)]

No, Intrepid. Given the reports of lack-of-stability, I'll be waiting to upgrade for at least a month, if not just skip the cycle.

These seem to be the pertinent details devs want:

$ lsb_release -a
No LSB modules are available.
Distributor ID: . . Ubuntu
Description: . . . Ubuntu 8.10
Release: . . . . . 8.10
Codename: . . . . . intrepid

$ uname -a
Linux hani 2.6.27-11-generic #1 SMP Wed Apr 1 20:53:41 UTC 2009 x86_64 GNU/Linux

$ dpkg -l | grep brasero
ii brasero . . . . . . . 0.9.1-0ubuntu3~intrepid1 . . CD/DVD burning application for GNOME
ii libbrasero-media0 . . 0.9.1-0ubuntu3~intrepid1 . . CD/DVD burning application for GNOME - runtime librarie

[Pedro Villavicencio (pedro)]

Ok then please open an upstream report at bugzilla.gnome.org since you're not using the latest package, for forwarding the report please read https://wiki.ubuntu.com/Bugs/Upstream/GNOME ; thanks.

[Kevin Hunter (hunteke)]

Having been through this before, I'll get a very similar response. There is a very wide gap between the end-user-seeing-a-bug-in-"in-use"-software and the developer-developing-on-the-cutting-edge. As a semi-educated end-user, I don't know how to cross that bridge effectively enough for developers. In some sense, launchpad *is* that interface for me (and I imagine lots of others). I'd love to help the open source and Free software worlds, but a developer I am not. I'm an end-user, and there are folks (such as yourself?) who know how to effectively talk to developers.

In the mean time, I'm *not* running Jaunty, nor will I be in the near future. This bug will have to wait until someone either cares, or I update to the latest and greatest. Given the stability factor of Jaunty, I'm guessing my update won't be coming first.

[Pedro Villavicencio (pedro)]

There's nothing we can do if you're not willing to upgrade to a recent release, the bug is a low priority one and it won't be fixed in that release since it doesn't fit the requirements for an SRU[1]; often users think that every single bug can be backported and fixed to a release but that's not true, there's a clear policy about that.

1- https://wiki.ubuntu.com/StableReleaseUpdates

[Kevin Hunter (hunteke)]

Heh, I wasn't vying for a back-port. I was vying for a let-the-devs-know. Rereading what I wrote a couple of months ago, I suppose it came across confrontational. That was not my intent. Suffice it to say, this is a low priority bug. If it's still there in Karmic, I'll "sound the alarm". Until then, I wouldn't worry about it.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of brasero is available in both Lucid and Maverick and we are wondering if this is still reproducible in any of those versions, May you please test and give us of feedback about it? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.