Red Hat Bugzilla – Bug 54788
xcdroast spawns unkillable cdda2wav
Last modified: 2007-04-18 12:37:39 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.3-12 i686)
Description of problem:
When I run xcdroast, most times, but not all, When hitting the 'duplicate'
or 'master' button, xcdroast freezes and slowly eats up all of the
resources so that it has to be restart via ssh and another terminal.
I have updated to the latest xcdroast and companions in rawhide, but the
problem still happens...it seems to happen when the system has been running
awhile, because it will normally run okay after a reset. The only
noticeable syslog messages refer to a missing char-major-97, but I also see
this when I succesfully burn cd's. I'm not sure what logs you need, but
I'll be glad to send anything you need.
Note that after this happens, running cdrecord -scanbus produces nothing
and must be exited with control-c
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start xcdroast (I su to root before)
2.Hit 'duplicate' or 'master'
Actual Results: system locked up
Expected Results: it should have read the cd and displayed the tracks.
Happens on blank cd's or stamped cd's
using latest stable alsa drivers on a via686a
have a philipps PCRW80 using scsi-emulation...its the only drive on the
secondary IDE channel.
using kernel 188.8.131.52 (downloading the update to 2.4.9 now)
uging the latest xcdroast-cdrecord-mkisofs-cdda2wav from rawhide
I need you to be more specific about some things. I had a go at reproducing
this but didn't see any bad effects.
Is the blank CD in the input tray? (That's what I tried.)
By 'system locked up', do you mean that the entire machine froze? I'm
guessing not from your other comments. In that case, please show me the
output of 'ps axfwww' when xcdroast gets into this state.
Let me know the result of trying kernel 2.4.9-6. Thanks.
Well, this seems to have been cured with the 2.4.9 kernel...I've tried all of
the usual tricks, but it just seems to work now. If it happens again, I'll
reopen or file another bug with your suggested output. Thanks!