Did anyone forward this upstream?
--
k3b should fork on verify
https://bugs.launchpad.net/bugs/109095
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
https://lists.ubuntu.com/mail
** Changed in: k3b (Ubuntu)
Importance: Undecided => Wishlist
--
k3b should fork on verify
https://bugs.launchpad.net/bugs/109095
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for k3b in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECT
I suggest that this is treated as an additional feature (i.e. set to
wishlist), so I confirm it.
** Changed in: k3b (Ubuntu)
Assignee: Ralph Janke => (unassigned)
** Changed in: k3b (Ubuntu)
Status: Needs Info => Confirmed
--
k3b should fork on verify
https://bugs.launchpad.net/bugs
Good question!
I had MD5'd the image after the download. I kicked off the download and
md5 over night so that when I got up the next morning I could see how it
went. I already knew the image was good, so I went right past K3Bs pre-
burn MD5.
What you have said is true, but if I skip the auto MD
Thanks for submitting this report.
Why would you want to do this in parallel. Wouldn't you first want to
find out if the image that you want to burn is ok (through checking the
MD5) and then burn. If the MD5 fails, you wouldn't want to burn it
anyway?
Thanks
** Changed in: k3b (Ubuntu)
Assi
