This problem was fixed a few weeks ago on brasero svn but we had a typo on brasero 0.7.1 desktop file that is creating this bug hopefully we would like to release 0.7.2 before hardy release.
This problem was fixed a few weeks ago on brasero svn but we had a typo on brasero 0.7.1 desktop file that is creating this bug hopefully we would like to release 0.7.2 before hardy release.