On Sun, 23 Jul 2006 22:07:01 -0400
Francois Marier <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 03, 2006 at 02:41:38AM -0400, A. Costa wrote:
> > 2) More difficult. We rewrite the bug using what we've learned,
> > and open a new one, phrased so it's harder to misunderstand...
> I believe that your solution #2 is the best one...
#2 it is then.
> ...So what I'd like to do is to rewrite the description of the bug and
> submit a new one upstream. Of course, I'd like your opinion on the
> following before I send it over:
>
> ----------
> There is a confusing message from K3b whenever the user tries to burn
> a Data CD project on a blank DVD-R (or vice-versa).
Well, it seems the 'vice-versa' part isn't true. I just stuck a CDRW
in and tried to burn a DVD and it correctly explains:
[ Waiting for Disk - K3b ]
Found media: CD-RW (complete)
Please insert an empty or appendable Double Layer
DVD+-R medium into drive
PIONEER DVD-RW DVR-107D (/dev/hdd).
[Load] [Eject] [Force] [Cancel]
I haven't tested the opposite case, that of burning a CD onto DVD media.
To review, my first bug was caused by a special case. In hindsight, I
notice after again rereading the old bug reports, that I never
explained the hardware problem thoroughly enough to eliminate certain
doubts. (I thought everybody would somehow know what I meant, even
without such details.) My mistake, so here's a second attempt:
Last February when I submitted this bug, I was trying to burn a DVD and
had a blank DVD-R in the drive -- there was no media size conflict.
Here's the text, and a URL to a .PNG capture, of the error box:
[ Waiting for Disk - K3b ]
Found media: DVD-R Sequential (empty)
Please insert an empty or appendable CD-R(W) medium into drive
PIONEER DVD-RW DVR-107D (/dev/scd1).
[Load] [Eject] [Force] [Cancel]
http://bugs.debian.org/cgi-bin/bugreport.cgi/K3B_errror.png?bug=352005;msg=5;att=1
Note the burner. In February I had it in a USB case so it showed
up as '/dev/scd1', while today it's in an IDE bay as '/dev/hdd'. It
might be possible that the USB case interface lead to some weird
hardware incompatibility that brought on the error.
The hardware problem** isn't K3B's fault -- the K3B bug is that K3B
detected something is wrong, but printed an illogical or (at
best) rather vague error.
More hardware details. The media was a new 'HP DVD-R 16x 4.7Gb' -- I
find today I can't get the 'PIONEER DVD-RW DVR-107D (/dev/hdd)' to
detect this disk. And yet in February it did detect it, and even
wrote a few coasters with it -- might have been the USB case, or
perhaps the later Kernel version I'm running (2.6.16 now, 2.6.15
then). I believe the 16x disk media is too fast for this old 8x DVD
drive, which I probably didn't know at the time I filed the bug.
I think what I'd like to do is try to duplicate the bug, in hopes of
narrowing down exactly what conditions caused it. This may take a
while, as swapping hardware is inconvenient this week -- perhaps if
somebody reading this is familiar enough with the code to deduce how
K3b displayed its weird error message, they might be able to figure it
out before my hardware level tests could.
More on the rest of your message later, after I try to reliably
reproduce the bug, going through the various stages:
1) Media (DVD-R)
2) Hardware (DVD burner)
3) Hardware BIOS.
4) Interface (USB, IDE, or fake SCSI)
5) Low level programs that K3b calls.
6) K3b itself.
NB: again, I'd like to caution against the mistake of thinking this is
"just a hardware problem", so that it can be safely ignored because
users with the wrong hardware shouldn't blame the software. K3b is a
front end, and by design is meant to insulate users from the
idiosyncrasies of hardware. While it can't turn bad or incompatible
hardware into good or compatible hardware, it can report errors, and it
should do so as accurately as possible. This particular K3b bug is the
error message it displays when it (inevitably I think) encounters buggy
or incompatible hardware.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
