[kde-linux] k3b won't verify data

Anne Wilson cannewilson at googlemail.com
Fri Feb 22 19:12:54 UTC 2008


On Friday 22 February 2008 19:06:50 Gaffer. wrote:
> Hi Anne,
>
> On Friday 22 February 2008 11:33, Anne Wilson inscribed thus:
> > On Thursday 21 February 2008 19:28:04 Gaffer. wrote:
> > > Hi Anne,
> > >
> > > On Thursday 21 February 2008 09:36, Anne Wilson inscribed thus:
> > > > On Wednesday 20 February 2008 22:04, Gaffer. wrote:
> > > > > Yes I agree!  But it would help if I knew where it kept them.
> > > > >  I've not found any, there is nothing in the system log.
> > > >
> > > > From the horse's mouth :-)
> > > >
> > > > 1. In K3b's progress dialog you get the "debugging output"
> > > > button which shows the log.
> > > > 2. This log is also saved in ~/.kde/share/apps/k3b/lastlog.log
> > > > 3. The console output gives a lot of information for harder
> > > > problems such as devices not recognized and so on.
> > > >
> > > > If you get useful stuff to add to the bug report, please give
> > > > us the bug number, so that we can follow its progress.  Thanks
> > > >
> > > >
> > > > Anne
> > >
> > > I thought I had looked in there !   Any way here is the last few
> > > lines.   The first line below gets repeated periodically from the
> > > start of the burn.
> > >
> > > [growisofs] 4484431872/4525946880 (99.1%) @4.0x, remaining 0:07
> > > RBU 100.0%
> > > [mkisofs]  99.84% done, estimate finish Thu Feb  7 21:00:30 2008
> > > [mkisofs]  99.87% done, estimate finish Thu Feb  7 21:00:30 2008
> > > [mkisofs]  99.89% done, estimate finish Thu Feb  7 21:00:29 2008
> > > [mkisofs]  99.91% done, estimate finish Thu Feb  7 21:00:29 2008
> > > [mkisofs]  99.94% done, estimate finish Thu Feb  7 21:00:30 2008
> > > [mkisofs]  99.96% done, estimate finish Thu Feb  7 21:00:30 2008
> > > [mkisofs]  99.98% done, estimate finish Thu Feb  7 21:00:30 2008
> > > [mkisofs] Total translation table size: 0
> > > [mkisofs] Total rockridge attributes bytes: 6522
> > > [mkisofs] Total directory bytes: 10610
> > > [mkisofs] Path table size(bytes): 32
> > > [mkisofs] Max brk space used 0
> > > [mkisofs] 2209935 extents written (4316 MB)
> > > [K3bIsoImager] Pipe throughput: 4525946880 bytes read, 4525946880
> > > bytes written.
> > > [growisofs] 4503535616/4525946880 (99.5%) @4.0x, remaining 0:03
> > > RBU 66.8%
> > > [growisofs] 4522639360/4525946880 (99.9%) @4.0x, remaining 0:00
> > > RBU 9.9%
> > > [growisofs] /dev/hdc: flushing cache
> > > [growisofs] /dev/hdc: updating RMA
> > > [growisofs] /dev/hdc: closing disc
> > >
> > > As you can see there is no mention of any verification at all.
> > >
> > > :-(
> >
> > I've had a reply from the developer.  He says that most of the bug
> > reports for k3b refer to verification, but he has not been able to
> > reproduce it on any of the hardware he has access to, which makes
> > it difficult to trace.  Just what we expected really.
> >
> > He's in the middle of a project for KDE4, but hopes to finish that
> > soon and have more time to look again at k3b.
> >
> > Sorry that it doesn't help the current situation, be we have to
> > accept that developers are human, with the same time constraints as
> > the rest of us.  He's doing what he can.  :-)
> >
> > Anne
>
> I'm just sorry that I can't be more help. :-)

You're doing what you can, too :-)  Don't underestimate the importance of 
that.  Developers get a lot of mindless flak.  An attempt to help, even if 
not successful, is an incentive to a developer.

Anne


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-linux/attachments/20080222/010c7494/attachment.sig>


More information about the kde-linux mailing list