Brasero does not detect new disc if you want to burn another disc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
brasero (Ubuntu) |
Incomplete
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: brasero
Yesterday, I wanted to make some copies of a home made movie. I got the ISO (3.0 GB, thus DVD) on my HD.
So, I started Brasero and burned the first image. As I wanted to have some more copies, I selected 'burn another disc' after the first one was finished. However, Brasero did not succeed to start the second burn. It went like this:
- first burn finished
- I selected 'burn another disc'
- Brasero sais it needs a new DVD
- I ejected the first disc and I put in a new DVD
- Now, Brasero still has the dialog that I needed to put in a new dvd. However, it was already there. Furthermore, the burn progress dialog showed 'Preparing to write', but nothing happened actually.
- If I click 'cancel' in the faulty dialog of brasero to put a new dvd in, thw whole burn process stops
So, I had to restart the burning process from the beginning. I also had to umount a "VOLUME IDENTIFIER" mount, whoch was created. I don't know what this is (maybe it is the name of the DVD, created by a Pioneer dvd home recorder and thus Ubuntu mounted the first, succesful burn). However, unmounting during the faulty dialog did not make brasero to continue.
I know I did not have a debug log attached, but as I don't have anything to burn, I want to make sure the steps I have to take to produce a correct bug report.
ProblemType: Bug
Architecture: i386
Date: Sun Oct 18 12:17:08 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: brasero 2.28.1-0ubuntu1
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: brasero
Uname: Linux 2.6.31-14-generic i686
Changed in brasero (Ubuntu): | |
importance: | Undecided → Low |
Thanks for the report, could you get a brasero debug log by running brasero as: brasero --debug --brasero- media-debug &> brasero-debug.txt ; just reproduce the issue and attach that resulting log file to the report. thanks in advance.