Before actually doing on-the-fly burning I tried simulation to see if Arson fails. After simulation I mounted cd in my burner and discovered that CD-RW disc has data on it identical to the source. CD-RW was new out of the packging. I blanked cd-rw and repeted same operation twice. same result. Here's output from Arson Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas@daneb.de> SCSI interface library - (C) Joerg Schilling Paranoia DAE library - (C) Monty Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables. Using libscg version 'andreas-0.5-UNIXWARE_Patch' 1,0,0: VERBATIM 321240AL Rev: X8S2 Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000) 1,1,0: Compaq DVD-ROM DVD-114 Rev: 1.14 Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000) Starting on-the-fly CD copy at speed 12... Track Mode Flags Start Length ------------------------------------------------------------ 1 DATA 4 00:00:00( 0) 73:49:39(332214) Leadout DATA 4 73:49:39(332214) PQ sub-channel reading (data track) is supported, data format is HEX. Analyzing track 01 (MODE1_RAW): start 00:00:00, length 73:49:39... Turning BURN-Proof on Executing power calibration... Power calibration successful. Wrote 332214 blocks. Buffer fill min 3%/max 100%. Writing finished successfully. On-the-fly CD copying finished successfully. Reproducible: Always Steps to Reproduce: 1.Start Arson 2.Click "Copy CD" button on tool bar 3.In dialog box select "Direct Copy" 4.Choose source drive other than your Burner. Click OK 5.In "CD Copy" dialog box choose "Burn Method : Simulation Only" and set speed 6.Click start Actual Results: Instead of simulation Arson performs actual write. Expected Results: Arson shouldn't attempt to write. Blank CDR should remain blank after simulation. Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.22-ck2) ================================================================= System uname: 2.4.22-ck2 i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.4.3.10p1 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -ffast-math -funroll-loops -msse -mfpmath=sse,387 " CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -ffast-math -funroll-loops -msse -mfpmath=sse,387 " DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg distcc sandbox" GENTOO_MIRRORS="ftp://sunsite.unc.edu/pub/linux/distributions/gentoo http://gentoo.oregonstate.edu ftp://mirror.iawnet.sandia.gov/pub/gentoo http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X X509 Xaw3d aalib acl acpi acpi4linux apm arts avi berkdb bindist bonobo cdr cups curl dga directfb dv dvd encode esd ethereal faad fbcon ffmpeg flac foomaticdb gd gdbm ggi gif gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml imap imlib java javascript jdepend jikes jpeg kde kerberos lcms ldap libg++ libwww lirc ltsp mad mmx motif mpeg mpi mysql nas ncurses nls nvidia odbc oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline samba sasl scanner sdl slang slp snmp sox spell sse ssl svga tcpd tetex tiff transcode truetype usb v4l x86 xine xinerama xml2 xmms xosd xv xvid zlib"
This has nothing to do with keychain, please re-assign
Sorry this has taken so long. What version of arson? Is arson version 0.9.8_beta2 working? What version of cdrtools?
According to genlop it was arson-0.9.7-r3 cdrtools-2.01_alpha14. I haven't used arson since filing this bug.
given both program versions are newer and there is noone else even cc'd here I'm just going to close this one and if someone has the same problem, they can reopen it and I'll take a look. Thanks for putting in the bug report gene. Sorry Gentoo didn't solve the probablem and realy negelected the bug report in the mean time. I hope you understand all gentoo devs have lots of bugs and all struggle to keep up with them all. As such many are closed with crappy depositions such as this one. Hopefully overall the main ones get solved and the distrobution is worth while.