[Bug 182114] Re: k3b: cdrom not recognized after burning

[Patrick McFarland]

The problem is K3B is no longer ejecting and reloading the disc,
ignoring whats set in preferences: you absolutely must eject the disc
after burning on many drives, issuing any commands afterwards (such as
trying to verify contents) will cause the drive to lock up.

You can fix this by running hdparm -w /dev/cdrom && hdparm -d1
/dev/cdrom, but it still breaks k3b's verify disc function.

I am also suffering from this bug, and manually running genisoimage,
wodim, eject, then eject -t then using md5sum or some other method to
verify works, k3b is simply not ejecting the disc and reloading. IMO
this is a critical bug.

-- 
k3b: cdrom not recognized after burning
https://bugs.launchpad.net/bugs/182114
You received this bug notification because you are a member of Ubuntu
Burning Team, which is a bug contact for k3b in ubuntu.