Hi all. I wanted to burn a Blu-ray disk, so I tried in Fedora 11 (k3b 1.0.5). No dice. So I got the latest alpha, turned it into an RPM, and installed it. I got further this time, in that it tells me the correct media size, and lets me add files to it. But when I try to burn it, it brings up a box that says this:

Found medium: Empty BD-R medium
Please insert a suitable medium into drive
SONY BDRW BWU-300S (/dev/sr1)

The three available buttons are "Load", "Eject", and "Cancel". Whichever one I press, I don't get a burning result.

So, my question is, how do I get this thing to fly?

unfortunatly the k3b developers does not have access to blu-ray hardware themselves, meaning the support for it might be a bit bumpy It's nice to get some testing of it though.

The issue is also reported by another user on the k3b mailing list, I will report this to the developers, such that we can get some more testing going.

/Kim

Hi, the first version that is meant to work with Blu-ray disks is 1.70.0 (2.0-beta1). In earlier versions BD support was blocked in most of the places.
Edit: the bug you've described has been reported here: https://bugs.kde.org/show_bug.cgi?id=227339

This time, I tried with 1.70.0beta1 (I expect that's the one you mean). Same result.

There's now a new release of k3b which should have fixes for your issue with blu-ray:

https://sourceforge.net/projects/k3b/fi ... 2/download

Thanks, issue fixed. But now there's another similar one.

https://bugs.kde.org/show_bug.cgi?id=237324

Incidentally, it might be an idea, in the report above, to add the size of the medium (if known) to the error message.

Also, I just wanted to make a suggestion. When I tried to create my data project this time, I started out by trying to put 26GB on a blu-ray (which is only 25GB). When I clicked "Burn" on the main screen, the burning dialogue box wouldn't let me continue, saying in the Burn Medium box "Please insert an empty or appendable Blu-ray medium". When I deleted some things, so that it was under 25GB, then I could go on, but I was quite confused for a bit there, because the disc was in the drive, but k3b was not recognising it. I even almost submitted a bug report for it.

My suggested solution:
- Replace this message with a message that says "There is too much data for this disc", and a button that says "Fix this problem" that only appears with this message (and any others you need).
- When people click the "Fix this problem" button, it brings up a wizard -- a dialogue box (with radio buttons?) that says: You have three options, you can
*** Go back and remove some data from the data project
*** Insert a larger medium
*** Burn a multi-disc set
- If the people choose option 1 above, then just close the dialogue boxes, and let them do it
- If people choose option 2 above, then bring up a box that lists different media and their sizes, with the ones that are too small greyed out. That would give people some guidance as to what they need to get
- I'm under the impression that multi-disc sets are already supported, but I know nothing about them, so I'll leave that idea with you.

Hope some of this helps. Thanks for fixing the previous bug, and sorry I was slow in responding.

Apparently my followup bug has been patched already.

https://bugs.kde.org/show_bug.cgi?id=236069

When someone tests, they can report back.

Ok, I tested it, and that fix works. But now I have a different problem. I burn the disk. It gets 99% done, and then says "Fatal error during recording: Input/Output error". I tried to include the debugging output, but it wouldn't let me, so I've trimmed it. If anyone can suggest any ideas, that would be great!

Burned media
-----------------------
BD-R Sequential (SRM)

Devices
-----------------------
ATAPI DVD A DH20A3L EP58 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]
SONY BDRW BWU-300S 1.0c (/dev/sr1, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 10409137 (21317912576 bytes)

System
-----------------------
K3b Version: 1.91.0
KDE Version: 4.4.2 (KDE 4.4.2)
QT Version: 4.6.2
Kernel: 2.6.29.6-1.rt23.4.fc11.ccrma.x86_64.rt

Used versions
-----------------------
mkisofs: 1.1.9
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr1 obs=32k seek=0'
/dev/sr1: pre-formatting blank BD-R for 24.8GB...
/dev/sr1: "Current Write Speed" is 4.1x4390KBps.
47251456/21317912576 ( 0.2%) @1.8x, remaining 45:00 RBU 100.0% UBU 0.5%
71598080/21317912576 ( 0.3%) @1.6x, remaining 44:30 RBU 100.0% UBU 99.5%
[trim]
21224128512/21317912576 (99.6%) @1.7x, remaining 0:12 RBU 100.0% UBU 99.5%
21249032192/21317912576 (99.7%) @1.7x, remaining 0:09 RBU 100.0% UBU 99.5%
21274820608/21317912576 (99.8%) @1.7x, remaining 0:05 RBU 100.0% UBU 99.5%

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr1=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:10409137 -speed=4 -use-the-force-luke=bufsize:32m

mkisofs
-----------------------
10409137
I: -input-charset not specified, using utf-8 (detected in locale settings)
This size can only be represented in the UDF filesystem.
Make sure that your clients support and use it.
ISO9660, Joliet, RockRidge, HFS will display incorrect size.
Using BLAISE_EXPORTSUSERSWAYLA000.TGZ;1 for blaise/blaise-exportsuserswaylandMusicflac-2010-05-12.tgz (blaise-exportsuserswaylandMusicflac-2010-05-08.tgz)
0.00% done, estimate finish Thu May 13 21:02:13 2010
0.01% done, estimate finish Thu May 13 21:02:13 2010
=== last message repeated 2 times. ===
0.02% done, estimate finish Thu May 13 21:02:13 2010
=== last message repeated 2 times. ===
0.03% done, estimate finish Thu May 13 21:02:13 2010
=== last message repeated 2 times. ===
0.04% done, estimate finish Thu May 13 21:02:13 2010
=== last message repeated 2 times. ===
0.05% done, estimate finish Thu May 13 21:02:13 2010
=== last message repeated 2 times. ===
0.06% done, estimate finish Thu May 13 21:02:13 2010
[trim]
99.85% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 3 times. ===
99.86% done, estimate finish Thu May 13 21:48:55 2010
99.86% done, estimate finish Thu May 13 21:48:56 2010
99.87% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.88% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.89% done, estimate finish Thu May 13 21:48:56 2010
99.89% done, estimate finish Thu May 13 21:48:55 2010
99.90% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.91% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.92% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.93% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.94% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.95% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.96% done, estimate finish Thu May 13 21:48:56 2010
99.96% done, estimate finish Thu May 13 21:48:57 2010
99.97% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 3 times. ===
99.98% done, estimate finish Thu May 13 21:48:56 2010
=== last message repeated 2 times. ===
99.99% done, estimate finish Thu May 13 21:48:56 2010
99.99% done, estimate finish Thu May 13 21:48:57 2010
Total translation table size: 0
Total rockridge attributes bytes: 2499
Total directory bytes: 6626
Path table size(bytes): 42
Max brk space used 0
10409137 extents written (20330 MB)

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid baks -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-wayland/k3bpp4139.tmp -rational-rock -hide-list /tmp/kde-wayland/k3bUm4139.tmp -no-cache-inodes -allow-limited-size -udf -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-wayland/k3bjh4139.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid baks -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-wayland/k3bcp4139.tmp -rational-rock -hide-list /tmp/kde-wayland/k3bcm4139.tmp -no-cache-inodes -allow-limited-size -udf -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-wayland/k3bcP4139.tmp

I don't see any anything wrong in this log. Are you sure you haven't cut out some error messages?

Fairly sure. Is there somewhere I can post the whole file?

I have the same problem on k3b 192.0 RC3-2 on Kubuntu 10.04 and KDE 4.4.4 and I'm a developer in a position to run this down.
I'm not sure about the reproducibility, and burning blu-ray coasters is
not so cheap, not to mention hours waiting for the thing to finish burning
only to barf and leave a corrupt disc.
If you can reproduce it, submit a bug report to bugs.kde.org, and I'll pick
it up. I might even attach my own info to it, if I can reproduce it. In my
judgment, this is one of the most significant bugs impairing blu-ray
functionality.

Stuart

If you have problems with BluRay writing, I recommend you to
use cdrecord instead of growisofs. Growisofs has several
reported problems with BD-R media.

Make sure that you use a recent cdrecord (current release is 3.00)

Same error with k3b burning blu ray discs. If the bug is potentially in growisofs, Can i tweak k3b to use cdrecord instead of growisofs to burn blu ray?

K3b uses what's installed, if you install cdrecord and remove what it replaces then K3b should automatically use it. Distro's that replaced cdrecord with cdrkit made uses of links so that programs calling then didn't need to be changed (ex if you run "ls -l /usr/bin/cdrecord" the result should be a link to wodim)

you can specify which versions of a program that K3B finds on the system it should use in setting -> configure k3b -> programs. If K3b sees multiple versions of a executable you can select your preference as the default (note: In the other settings tabs you can set program parameters and change the search path K3B uses to find the programs).

You might want to Google for cdrecord and your distribution to see where to find (or how to compile), install and setup cdrecord for your system.

Interesting to note: in the program search paths on my system's K3b config there is a path (towards the bottom) set up for "/opt/schily/bin/" which I assume is there to find cdrecord if installed (as "schily" is the author).

i have tried that:installed cdrecord/ replaced wodim,genoisoimage and readom with the latest binaries for cdrecord,mkisofs, and readcd.But same error (input/ouput error). In any case, k3b always uses growisofs for bluray writing. Not sure how to force it to use cdrecord for blu ray write .