brasero can not eject medium and process is still running

Bug #1082411 reported by Hassan Williamson on 2012-11-23
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Undecided
Unassigned

Bug Description

There appears to be a bug where-by brasero is unable to eject when it finishes burning. So I do as it says, and eject manually. I then proceed to click finish. However, I attempted to burn something else, and brasero wouldn't open at all. Using the command `htop` (or `top`), I see that brasero is still running in the background. I have to kill the process to be able to continue running another process.

Please note: I'm using Ubuntu 12.04 amd64.

1) $ lsb_release -rd
Description: Ubuntu 12.04.1 LTS
Release: 12.04

2) $ apt-cache policy brasero
brasero:
  Installed: 3.4.1-0ubuntu1
  Candidate: 3.4.1-0ubuntu1
  Version table:
 *** 3.4.1-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

3) Brasero to eject the optical medium (CD/DVD) and close gracefully when done.

4) Brasero asks to eject the optical medium manually, and doesn't close the process after clicking "finish".

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: brasero 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
Uname: Linux 3.2.0-33-generic x86_64
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
Date: Fri Nov 23 16:29:33 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
SourcePackage: brasero
UpgradeStatus: No upgrade log present (probably fresh install)

Hassan Williamson (hazrpg) wrote :
Hassan Williamson (hazrpg) wrote :

Just burned another CD, this time from the terminal and using the debug option. Thought this might help a bit.

Also the CD/DVD drive I have (as reported by `hwinfo`) is: TSSTcorp CDDVDW SN-208AB

Command used:

$ brasero ubuntu-12.04.1-desktop-i386.iso -g > brasero-debug.log

Log has been attached. Also note, I had to terminate the command with "CTRL+C" since it was still running.

Thomas Schmitt (scdbackup) wrote :

Hi,

i am glad to see that this time not the libburn plugin is
to blame. :))

Telling from the log, i would say that burning via libburn
succeeded:

> Burning from 0 to 355990
> TAO pre-track 01 : get_nwa(0)=1, d=0 , demand=729067520 , cap=736966656
> [... no visible error messages ...]
> Aync CLOSE TRACK SESSION succeeded after 4.3 seconds
> Finished successfully session
> stopped BraseroLibburn
> End of last written track address == 355990

But then program readom was started to check the readability of
the finished CD:

> readom dev=/dev/sr0 -nocorr -noerror -sectors=0-355990 -f=-
(Collected from several lines in the log.)

This program run seems not to reach the end of the medium or
at least it does not recognize that it is time to end the program.
The last message is
> BraseroReadom stderr: addr: 355840

That's 150 blocks before the end of the track.

Proposals:

- Try to disable checkreading before you burn.
  (I am not a Brasero user, but the plumber of libburn and libisofs.
   So i cannot tell how to do this disabling.)

- If you cannot disable checkreading, then kill the readom
  process rather than Brasero, when it gets stuck.
  I assume that Brasero will then finish with an error message.

- To learn more about the problem of readom, you could run

    readom dev=/dev/sr0 -nocorr -noerror -sectors=0-355990 -f=- >/dev/null

  and see what it actually reports. (>/dev/null is important to
  avoid that the whole CD content is printed to your terminal.)

Have a nice day :)

Thomas

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in brasero (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers