It works for me too. Problem seems to be solved.
I'm running k3b 1.91.0~rc2-0ubuntu3 in Kubuntu Lucid Lynx
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.
--
Thanks, Frank. Given that confirmation and the old age (Jaunty or older)
of all reports of failure I think it is best to close this as fixed :-).
** Changed in: k3b (Ubuntu)
Status: Triaged = Fix Released
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this
Works for me. I just successfully burned and verified a DVD iso and a CD
iso. Ubuntu maverick 64 bit.
Maybe it is fixed now.
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b
I have enabled the option in k3b so that the disk is ejected directly
after burning. This makes that the after-burning verification is done
with a re-inserted disk. The verification still fails.
I found on the web two methods to calculate the checksum. Only method 1
gives the same value for the
After a verification failure, if I sha1sum the CD device directly, the
resulting SHA1 sum also differs from the one of the ISO image. After
ejecting and reinserting the disc, the sha1sums suddenly match properly.
This makes me wonder whether this is really a k3b issue, or something
related to the
The bug still exists in Jaunty.
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
I am marking this triaged, importance - Medium. There should be enough
information for the developers to begin working this issue.
** Changed in: k3b (Ubuntu)
Importance: Undecided = Medium
Status: Confirmed = Triaged
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
I have this bug again in Intrepid, K3b 1.0.5
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Changed to confirmed..?
** Changed in: k3b (Ubuntu)
Status: New = Confirmed
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.
--
kubuntu-bugs mailing list
I think that more than enough people verify the bug. Just check the
respective thread at ubuntu forums
http://ubuntuforums.org/showthread.php?p=5767141#post5767141
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of
Confirming that verification on k3b in Kubuntu Hardy Heron is broken for
images.
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
More people confirm this on ubuntu-fi forums: http://forum.ubuntu-
fi.org/index.php?topic=17948.0, using Hardy.
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
KDE 3.5.9 w. Hardy and same error here whilst burning Ubuntu images. I
really believe that they are ok (not md5 checked after burning) but I
get the same 'written data in track 1 differs...' message so I'd say too
that something is broke there..
--
k3b verification broken
Same problem here.
Verification of a burned data cd fails, but manual read with dd produces image
identical to original.
This same hardware, and same locale variables, worked just fine under gutsy.
LANG=en_US.UTF-8
LC_COLLATE=POSIX
LC_TIME=POSIX
linux-image-2.6.24-15-generic
To amend my earlier report, which I filed after two failures:
Following those two failures, I had four successes, so it's not consistent.
Does not seem to be data dependent (image 1 failed twice, succeeded once, image
2 succeeded three times.)
Also, I believe I only had the LANG variable set,
same problem here, k3b claims faild verification but manually created
md5sum matches.
$ locale
LANG=de_DE.UTF-8
LANGUAGE=de_DE:de
LC_CTYPE=de_DE.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES=de_DE.UTF-8
LC_PAPER=de_DE.UTF-8
i did:
$ [EMAIL PROTECTED]
$ locale
[EMAIL PROTECTED]
LANGUAGE=de_DE:de
LC_CTYPE=[EMAIL PROTECTED]
LC_NUMERIC=[EMAIL PROTECTED]
LC_TIME=[EMAIL PROTECTED]
LC_COLLATE=[EMAIL PROTECTED]
LC_MONETARY=[EMAIL PROTECTED]
LC_MESSAGES=[EMAIL PROTECTED]
LC_PAPER=[EMAIL PROTECTED]
LC_NAME=[EMAIL PROTECTED]
This bug seems to be related to UTF-8. When I run k3b using:
#!/bin/sh
export LC_ALL=pl_PL.ISO-8859-2; k3b
verification works correctly.
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Kubuntu
Team, which is
** Attachment added: k3blog.txt
http://launchpadlibrarian.net/12905320/k3blog.txt
--
k3b verification broken
https://bugs.launchpad.net/bugs/207265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
19 matches
Mail list logo
