Re: Many bugs in latest version

[Philippe Rouquier <bonfire-app wanadoo fr>]

Le dimanche 27 septembre 2009 à 04:23 +0200, Maxim Levitsky a écrit : 
> > 
> > 3 - brasero doesn't refresh its view of the world, after it writes a
> > disk, thus I have to restart it.
> > For example if I blank a disk, or want to write two disks...
> > https://bugzilla.gnome.org/show_bug.cgi?id=596247
> This is indeed gvfs problem. I take a closer look at it.
> Sometimes now brasero does eject the disk.
> I think that devkit somehow sees the end of writing, and then mounts the
> disk, thus preventing the eject. I take much more careful look at that.
That's very likely, DeviceKit/GDU do very strange things like: recreating a Drive object every time a medium is inserted or removed; not creating a drive object when the medium is blank; when the medium can't be mounted, it sometimes does not even create a drive or volume object; ...

This is meant to be a feature (from what I heard) ??? Probably to filter what should be shown in nautilus.

> > 
> > 
> > 4 - My DVD DL writer destroyed already many DL disks, reporting errors
> > in very beginning.
> > Since every disks costs money, it is really unpleasant that breasero
> > doesn't include output of tools it uses in logs.
> > https://bugzilla.gnome.org/show_bug.cgi?id=596243
>
> I didn't indeed knew about -g --brasero-media-debug
> and these options indeed fix this problem.
> However if these are omitted, I think that stdout of tools isn't saved
> anywhere, right?
>
> If so I think it would be much better to save the stdout of tools, by
> default, to lower costs of testing of write once disks.

As I answered when closing the bug:
"it is saved in a temp file stored in the designated temp directory; the file should be brasero_tpm_{6 letters/numbers}. This file will be used in case the session fails and presented to the user. Once the BraseroSession object is finalized (when you change the project view), the file is destroyed. So you can indeed see the output of the session even when it succeeds" 
> However one minor thing I noticed that if I add the session, options in
> this dialog, are all unchecked. If I check them, they all work just
> fine.
Yes, I saw it as well. That's annoying but should be fixable (what is not..).

> Also I noticed that writing a DVD+RW makes the 'Leave disk blank' always
> selected and gray. Is this intended? (In fact as long as this option is
> set, its just fine, probably there is no sense in closing a DVD+RW)
> (growisofs is used in this case)

Yes, that's perfectly normal as you can't "close" DVD+RW discs. You can always rewrite them again and again. There is no way to prevent a rewriting of them. That's why this option is shown in grey and ticked.

> > * brasero can't blank DVD+RW disks (it should at least write zeros at
> > beginning of the disk if the low level format isn't needed)
> This isn't a trivial bug.
>
> As I understand it, there is no way to return a DVD+RW in 'pristine'
> state. It can be formatted again, but this doesn't make sense, and
> sometimes I have seen a warnings on the web (I think dvd-rw-tools
> mention that, that format can actually lower the durability of this
> disk, and can fail after ~30 cycles)
>
> However, this means that gnome would never display the CD/DVD creator
> page. 
> More that that, if I somehow blank the disk (using dvd+rw-format for
> example, or burn /dev/zero over the disk), then gnome will cease to see
> the disk altogether, since it is nether technically blank, nor has a
> valid filesystem on it).
> By the way, the above can happen with other media types, thus I think
> they should introduce new disk state, something like 'damaged' maybe?

> And of course, DVD+RW which have first say 1MB zeroed out should be
> treated as blank.
See the above comment on GIO/GVFS/GDU/DeviceKit, this is probably linked to what I described. This is indeed a problem since brasero won't be able to re-blank/format so they can be restored to a workable state.

Philippe.