[kdepim-users] K3b headache (Franco Pellegrini)

[Emanoil Kotsev]

Sorry for posting to this list, I think the kde-users is a better place for this discussion.
 I see more people get involved in the discussion.

From: Gene Heskett <gene.heskett at verizon.net>
To: kdepim-users at kde.org
Date: Thu, 24 Apr 2008 11:32:28 -0400
Subject: Re: [kdepim-users] K3b headache (Franco 
Yes, that is at least the std behavour. In my test yesterday, not ejecting and 
reloading the disk would only allow dd to access the last block of the image 
written, the last 2048 bytes.  dd returned without error for whatever that's 

this is really interesting ... on my system it checks all the bytes on both external cd/dvd and internal one.
worth.  And it was capable of repeating that read action, getting the same 
sha1sum answer each and every time at about 3 second intervals.

My intuitive reaction to this is that we WILL be forced to eject the disk, and 
that k3b will need a different patch so it will just set there and wait, say 
for a minimum of 1 minute when it gets an ENOTREADY from the drive after a 
reload operation.  Presently, it appears that k3b treats this as an instant 
real error and bails out.  Any other time its waiting for a disc, its just 
this seems to be easy doable (see below)
waits, and then updates the gui when it can in the background, but not for 
the verify pass reload, for some reason that is a failure.

Perhaps this background disc scan used in other places could be used for the 
delay for the disc ready when verifying?  It certainly seems do-able to me, 
but I've not had a chance to troll through the code yet, life keeps getting 
in the way, and younger minds more fam with C++ stuff could probably find it 
far quicker than I could.  I've never written a single line of C++ stuff in 
my 73 years.

what are the developers good for ;-) C++ like any other programming language makes a lot of fun (except you can brake your machine)

If the reason is really the wait time after reload it could be easy doable with few lines of code.
I am still preoccupied and can not spent any time on this issue, but if I have few hours I'll try to have a lookin it, as I am getting more interested in the problem.

I would recomend to try contact the developers first and reactivate the bug on this issue.
I'm pretty sure that this is due to a change of the k3b code or some underlaying library, because the issue is somehow new to me about a year now. 
I still have a debian sarge system and it works like a charm there .... no comments :-)

best regards




       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20080425/97b92fdf/attachment.html>
-------------- next part --------------
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users