Comment 77 for bug 1713485
Revision history for this message
|
|
#77 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hi,
> Help...
I am riddling what we see with your fgrep run.
Did you copy+paste my fgrep line together with my three output lines ?
Somehow the shell "bash" tried to execute the lines which were found
by my local fgrep. Your local fgrep found only one, probably because
Leslie's change is already in your local K3B git copy.
bash complains about non-existence of the files instead of complaining
about lack of x-permission. This is because my fgrep output lines have
the filenames with trailing ':'. They only exist without that ':'.
-------
Whatever, this is not related to K3B's functionality.
Actually i did not expect that you execute that fgrep yourself. I was
just showing the query by which i found the decisive spot in the code.
Important to K3B would be the questions:
- Did the burn run with the Debian ISO succeed ?
(Your image
https:/
shows it at 68 percent.)
- Did you already verify the result as proposed by Debian CD FAQ ?
https:/
I translate it to these shell commands:
/sbin/isosize -x debian-
which is supposed to say: sector count: 11223478, sector size: 2048
and
dd if=/dev/sr0 count=11223478 bs=2048 | sha512sum
which is supposed to say: 81761e602af6d0e
according to
https:/
If the SHA-512 sum is not 8176...a1d5, then compute the SHA-512 of the ISO
by
sha512sum debian-
to verify that the .iso image indeed yields the announced 8176...a1d5
If both answers are "yes", then the next quesition would be whether it
boots on your machine. If "no" then it would not be K3B's fault, but i
myself would be the one to inspect the boot process until the first Debian
logo appears.
Have a nice day :)
Thomas