k3b trouble

[Seeker]

ANOTHER EDIT: Nevermind, folks. I think I figured out the problem (heh, apparently the cd had a lil info on it. Still say it's k3b's fault tho.)





Yup, I gots me another problem.

Sigh.

I was making a cd with k3b (well, adding songs to the queue in the project) when I had an error that kinda screwed me.

First, lemme start off with this: some mp3s, I can play from k3b without any trouble, but therea are also some (oddly enough, only the ones that start with 'm') that take like 20 seconds before the actually start playing. I did one of these to see what it was (xmms or whatever has no problem with these files) and after about 20 seconds it started playing... well, later, I clicked on another song in the browser and clicked the play button, forgetting that the retaded 20-second song was still in the queue, so my comp froze for about 10 seconds before giving me some sort of 'cpu overloaded' error. I kind of ignored it, since.. well, my computer's still running flawlessly as before, with one exception: whenever I try to play a song from k3b, it says

cannot open aRtds

or something to that effect.

Well, it did until I restarted my computer. But either way, I can't burn a cd with it anymore... I can get as far as clicking on 'write' in the dialog it brings up after you click the burn button, but then it just sits there with everything at 0%. It's not like my computer's frozen during this, either... there's no activity happening with the cd at all. I've used k3b to make a cd a few days ago, so really, I have no idea what the hell's going on.

Anyone else have any clue?



Edit: I tried a dummy write with cdrecord, here's everything I typed and the ensuing error...

root@box:~# cdrecord -v -dummy speed=4 dev=0,0,0 -audio audio*.wav
Cdrecord 2.01a16 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
TOC Type: 0 = CD-DA
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.7'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'MITSUMI '
Identifikation : 'CR-4804TE '
Revision : '2.6C'
Device seems to be: Philips CDD-522.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC SWABAUDIO
Supported modes: TAO PACKET RAW/R16 RAW/R96R
Drive buf size : 1343488 = 1312 KB
FIFO size : 4194304 = 4096 KB
Track 01: audio 44 MB (04:21.94) no preemp
Total size: 44 MB (04:21.94) = 19646 sectors
Lout start: 44 MB (04:23/71) = 19646 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 4
Is not unrestricted
Is not erasable
Disk sub type: Medium Type A, low Beta category (A-) (2)
ATIP start of lead in: -12508 (97:15/17)
ATIP start of lead out: 359845 (79:59/70)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 22
Manufacturer: Ritek Co.
Trying to clear drive status.
cdrecord.mmap: Drive needs to reload the media to return to proper status.
Starting to write CD/DVD at speed 4 in dummy TAO mode for single session.
Last chance to quit, starting dummy write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Starting new track at sector: 0
Track 14: 0 of 44 MB written.cdrecord.mmap: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 00 00 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 05 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.001s timeout 40s

write track data: error after 0 bytes
cdrecord.mmap: A write error occured.
cdrecord.mmap: Please properly read the error message above.
Writing time: 5.041s
Average write speed 52.1x.
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
Fixating time: 0.006s
cdrecord.mmap: fifo had 64 puts and 1 gets.
cdrecord.mmap: fifo was 0 times empty and 0 times full, min fill was 100%.


I've successfully written cds with cdrecord... earlier today.

God linux is frustrating.

[Dave_Bechtel]

As root, ' killall arts ' and see if there is a config setting to not use Artsd. This should help.

' ps ax |grep arts ' to see if the daemon is still running.