I'm not sure when it stopped working, but i tried burning a CD yesterday and it failed. Worked under <cough> XP, so it isn't the drive. So I reinstalled k3b and cdrdao and now it is working again. here's what I have installed: k3b-mad-0.12.10-3.pm.1 k3b-0.12.10-3.pm.1 cdrdao-1.1.9-8 -- Paul Cartwright Registered Linux user # 367800
I'm not sure when it stopped working, but i tried burning a CD yesterday and it failed. Worked under <cough> XP, so it isn't the drive. So I reinstalled k3b and cdrdao (snip) When k3b fails it gives you the option of displaying an error log. Without the info of this log it is hard to tell why it failed. The fact the reinstalment
Paul Cartwright wrote: proved to be a cure only shows that it wasn't your config file that was at fault. Occasionally it fails because some other program has a lock on the cdrom or cdrecorder. Regards, -- Jos van Kan registered Linux user #152704
On Sat February 4 2006 6:23 am, Jos van Kan wrote:
When k3b fails it gives you the option of displaying an error log. Without the info of this log it is hard to tell why it failed. The fact the reinstalment proved to be a cure only shows that it wasn't your config file that was at fault. Occasionally it fails because some other program has a lock on the cdrom or cdrecorder. you are correct. I did look at the log, but it didn't tell me anything useful. It mentioned cdrdao, and memory, but I didn't keep the log. I looked in .var/log but didn't see anything relating to that. Does K3B keep a log somewhere??
-- Paul Cartwright Registered Linux user # 367800
participants (2)
-
Jos van Kan -
Paul Cartwright