[Bug 514782] Re: brasero fails to recognise dvdrw drive and/or media
davydm at gmail.com
Sun Feb 7 08:52:52 GMT 2010
1 is correct -- but it seems to be the same as 2 since the dvdrw was erased
from the right-click menu that pops up on the desktop in GNOME -- afaik,
this invokes brasero?
2 was for media that wasn't blank -- Nautilus correctly mounted the media
but brasero didn't seem to handle with the fact that the media was mounted
-- until I dismounted it myself. This problem is intermittent -- about 90%
of the time, brasero dismounts the media before writing -- just these few
times it's gotten "stuck"
On 6 February 2010 22:16, Draycen DeCator <ddecator at gmail.com> wrote:
> Thank you, every bit of information is always of huge assistance! Since
> you said that you've had trouble with Brasero not recognizing discs in
> other situations, I'm not entirely sure that this bug is the same as the
> other one I found. It is very difficult to tell whether all of the
> issues you are experiencing are related or if they are separate
> problems. Consequently, I am hesitant to mark this bug as a duplicate.
> In order to help me prepare this bug for viewing by a developer, could
> you please summarize all of the issues you have had with Brasero not
> recognizing media? What you've mentioned so far seems to be...
> 1. Brasero doesn't recognize a RW media after is has been erased, but other
> applications (K3b) do.
> 2. Brasero unreliably will fail to recognize blank media mounted by
> 3. Brasero sometimes doesn't want to write to a media after it has just
> been erased using Brasero
> Do these sound correct? Please let me know if I have misunderstood any
> of them or if there are other strange behaviors you are having in
> regards to Brasero recognizing media.
> brasero fails to recognise dvdrw drive and/or media
> You received this bug notification because you are a direct subscriber
> of the bug.
There is no shame in not knowing; the shame is in not finding out.
brasero fails to recognise dvdrw drive and/or media
You received this bug notification because you are a member of Ubuntu
Burning Team, which is subscribed to brasero in ubuntu.
More information about the Ubuntu-burning