[kde-linux] k3b won't verify data
gnome at hawaii.rr.com
Tue Feb 5 10:51:43 UTC 2008
Anne Wilson wrote:
> On Monday 04 February 2008 19:39:40 david wrote:
>> Anne Wilson wrote:
>>> On Saturday 02 February 2008 10:20:13 david wrote:
>>>> Gaffer. wrote:
>>>>> On Saturday 02 February 2008 09:55, david inscribed thus:
>>>>>> Have k3b 1.0.4 running with KDE 3.5.8 (Debian Lenny/Sid). Whenever
>>>>>> I tell it to verify data after burning, it completes the burn, pops
>>>>>> open the CD tray, waits patiently until I push the tray back in.
>>>>>> Then it says "Verifying Track" and NOTHING NOTHING NOTHING HAPPENS.
>>>>>> The CD drive makes a few clicking noise, but no reading begins.
>>>>>> Just sits there doing nothing. If I flip to another desktop, the CD
>>>>>> icon shows up, can be mounted, opened, data read from it,
>>>>>> unmounted, ejected. And the whole time k3b sits there "verifying
>>>>>> data" but never reading anything.
>>>>>> Can't find a k3b bug database anywhere, but apparently this is well
>>>>>> documented amongst Ubuntu users in their forums.
>>>>>> Anything I can do about it?
>>>>> This bug has been there quite a while. In my experience it only seems
>>>>> to affect DVD's CD's write and verify for me just fine.
>>>> I have only a CD burner, although the drive is one of those combo drives
>>>> able to read DVDs.
>>>> Guess it's not going to get fixed ...
>>> I don't know whether it's an Ubuntu issue, but I suspect not.
>> It's not an Ubuntu issue - I'm running Debian Etch Lenny/Sid.
>>> I think that
>>> most times I've heard of it the reporter has mentioned owning a combo
>>> drive like yours. If you are able to put a standard DVD drive in I
>>> suspect the problem will go away.
>> This is a laptop - I can't change out the drive. In fact, most laptops
>> I've run into included some kind of combo drive. So having this bug
>> around so long seems a little silly to me.
> If the bug can't be reliably triggered, it can't be fixed.
>>> It certainly is fine on every system I've handled, but
>>> I've never had a combo drive.
>> To make it weird, sometime back, there was a month or so when it
>> verified data just fine.
>> Oh, well!
> It's not a simple k3b bug - verify works fine on many/most drives. It must be
> an interaction between hardware and software, being specific to certain
> hardware, but that doesn't make it any easier to track down. Your last point
> suggests that something changed, making it work, then not work. I can only
> suggest that you try, next time you see a change in behaviour, to record what
> has been updated in recent times.
Well, since that one time it worked, the system had been updated like
normal several times. Then an update broke something (not related to
burning CDs), and I decided it was time for a fresh install, so I
installed Debian Etch and updated that to Lenny/Sid, where it is now. I
don't recall it ever verified data since installing Etch.
> Of course if you only burn a dvd rarely
> that's not going to be easy.
I don't burn DVD's at all - my drive is incapable of burning a DVD. It
can READ a DVD, but the only thing it can burn is a CD. The drive is a
Toshiba DVD-ROM SD-R2512. I believe it was pretty much the standard
Toshiba optical drive used in all their laptops at the time.
> Sorry I can't suggest anything more helpful. I thought of mdsums, but a
> burned disk would have a different sum to the original iso. That's how k3b
> verifies anyway, but I think Gaffer is right, and it's not the verify that's
> failing, but communication.
I suspect it is, too. At least, k3b *thinks* it has begun the
verification process, it just never gets any action from the drive.
Possibly something in HAL, perhaps, that trips up just k3b. I haven't
tried Gnome's CD burning software. If it has the same problem, then I'd
think that would place the problem somewhere below k3b's level. If it
doesn't have a problem, then I'd think it's somewhere in KDE or k3b ...
to big an area to search.
gnome at hawaii.rr.com
authenticity, honesty, community
More information about the kde-linux