I have an LG Blu-ray burner HL-DT-ST - BD-RE BH12LS30 (hw identical to BH10LS30), with the latest firmware (VER. 1.01-C0), and I've tried to burn several BD50 ISO images using K3b without success. K3b recognizes the drive and empty media but when I open 'Burn image' dialog and select a path to a BD50 ISO image it says 'Seems not to be a usable image'. I've tried changing 'Image type' but it doesn't seem to matter.

I'm using openSUSE 13.2 x86-64, KDE 4.14.4 and the latest K3b from Packman repo (k3b-2.0.80+git20150209.2250-1.1.x86_64.rpm). I've updated all relevant burning programs and libraries using openSUSE's Multimedia:apps and Multimedia:libs repos.

I've also tried using openSUSE's stock (OSS) version of K3b (k3b-2.0.2-33.1.8.x86_64.rpm), as well as the one from KDE:Extra (k3b-2.0.3-25.1.x86_64.rpm), and tried many different BD50 ISO images with all three K3b version but it always ends with: Seems not to be a usable image. I should also mention that I've added my user account to 'cdrom' group and changed permissions on relevant programs through K3b Settings dialog.

Finally, I've rebooted to WinXP and burned those images using ImgBurn without any troubles. I've also verified burned disks and tested them in standalone BD player. They are fine.

I like K3b very much and I had been using it since ever, but problem with BD50 ISO image burning is really a showstopper for me. I've not tried yet ImgBurn under Wine, nor any other burning app because BD50 coasters are not cheap.

Any ideas what might be the problem?

P.S. Here's a list of all relevant programs and their versions that I have on my system.

Code: Select all

openSUSE 13.2 (x86_64), kernel version 3.16.7-7-desktop
/usr/bin/cdrdao         1.2.3
/usr/bin/cdrecord       3.1a26
/usr/bin/dvd+rw-format  7.1
/usr/bin/growisofs      7.1
/usr/bin/mkisofs        3.1a26
/usr/bin/normalize      0.7.7
/usr/bin/readcd         3.1a26
/usr/bin/sox            14.4.1
/usr/bin/transcode      1.1.5
/usr/bin/vcdxbuil       0.7.24
/usr/bin/vcdxminfo      0.7.24
/usr/bin/vcdxrip        0.7.24

that message seems to indicate a corrupted file (at least to K3b)

have you ever burned blurays with K3b? or it just the BD50 image that is a problem

where'd you get the BD50 image? is it drm'ed?

Hi! Thanks for your reply.

The ISO files are definitely not corrupted as I have burned them successfully under Windows using ImgBurn.

I've burned one BD25 disk earlier, which I created under K3b as a 'New Data Project' and dropped in some backup files.

ISO files are downloaded using torrent client and are properly verified (all hashes are ok). As I've said, they burned just fine with ImgBurn.

I don't know about DRM, a suppose not. And even if they are would it matter?

Edit: It seems that K3b's 'Burn Image' tool/dialog has a problem with those files.

you could try brasero (Gnome's burner, not sure how many packages it would bring with it), this would tell if it's a K3b or one of the underlying programs that K3b calls that's the issue

no idea if drm matters but the more info the better

does it play in VLC or Kaffeine or Dragonplayer?

is the libbluray1 package installed ? should only matter for playback (I think)

Also, make sure that you have the original "cdrecord" and "mkisofs" (from cdrtools) installed, not "wodim" and "genisoimage" from cdrkit (and "cdrkit-cdrtools-compat").
I don't think cdrkit supports BD at all, while cdrtools should.

openSUSE 13.2 comes with both, but I'm not sure what's installed by default. (if you upgraded from a previous version, you definitely have wodim/cdrkit installed...)

See also:
http://en.wikipedia.org/wiki/Cdrtools
http://en.wikipedia.org/wiki/Cdrkit

Thanks for help you guys.

@google01103

I'm a KDE guy and Brasero has quite a large dependency list. I don't feel comfortable installing all of that only to test BD burning as this is my "production" system. Besides, K3b refuses even to call any of burning programs - I believe that problem is in it's own 'Burn image' dialog/tool.

I have libbluray1 0.7.0-36.1 from obs://build.opensuse.org/multimedia:libs but neither VLC, nor Kaffeine or Dragonplayer can't play BD ISO files. However, neither any software player nor my standalone BD player have any problem playing BD disks that I get from burning those ISO images (with ImgBurn or Nero) or when I mount them using a loopback device.

@wolfi323

I have original cdrtools (cdda2wav, cdrecord and mkisofs ver. 3.01a26) as it is now part of official openSUSE distribution. I also have genisoimage because acetone2 depends on it, but I don't believe that it gets in the way. I didn't installed cdrkit-cdrtools-compat, wodim nor icedax. However, I did zypper duped form openSUSE 13.1 but I wasn't using BD burner back then and I believe that I didn't had any of those packages installed.

In the meantime I obtained evaluation copy of Nero for Linux 4.0 and it burned couple of those ISO images that K3b wouldn't even touch. Disks are playing just fine both in VLC and on standalone player.

As I said, I strongly suspect that K3b's 'Burn image' tool is at fault.

just a note: I think your openSUSE post should have been a new thread with "Seeems not to be ...." in the thread title

Are you referring to my post in Opensuse forum under "BD-R/BD-R DL burning seems problematic on OpenSUSE 13.2 / K3b" thread? Should I start a new thread there or open a bug report in KDE Bugtracking System?

I strongly believe that problem is in K3b's "Burn image" tool, as I can burn new projects (data collection) but not an ISO image which perfectly works with ImgBurn and Nero, both under Windows and Linux.

I think both:
- your issue is different then the original poster, it might be specific to them (said might) and they have higher traffic rates so an increased possibility of a solution.
- if the issue is K3b's dialog (and you believe it so) then you should post a bug

I opened a new thread in openSUSE forum and filed a bug report in KDE Bugtracking System - Bug 344392.

I've tried mounting some BD50 ISOs using Silicon Mounter and the program halted with an error message:

Can't complete the mount operation

init: wrong standard identifier in volume descriptor 0, skipping..
...
init: wrong standard identifier in volume descriptor 16, skipping..
init: wrong standard identifier in volume descriptor 17, exiting..

I suspect that most of burning programs still expect ISO9660 and return error when confronted with an ISO image containing IEC 13346 (UDF) structure.

However, I've successfully mounted the image using loop device.

Code: Select all

sudo mount -o loop -t udf /path/to/image.iso /path/to/mount/point

I didn't mention that I have UDFtools 1.0.0b3. That lead me to realization that UDFtools don't support UDF 2.5, nor UDF 2.6. Actually, there is no OSS Linux software that has support for UDF 2.5 or 2.6 - only proprietary Nero for Linux 4.0.

I wonder, do we actually need support for UDF 2.5 file system if we have an ISO image containing one? Couldn't growisofs just dd data from a BD50 ISO image to a BD burner?

This starts to look like a feature request. Also, K3b's error report should be more informative when it comes to failing to handle UDF 2.5, especially when it claims "support for Blu-Ray disks".

any feature request to the underling tools would need to be post on their respective site(s), obviously use the busgs.kde.org for K3b related matters

you might try reaching out to the cdrtools author (http://cdrtools.sourceforge.net/private)

Actually, I think this concerns dvd+rw-tools, namely growisofs, rather then cdrtools.

I'm not familiar with K3b's internals but if it relies solely on external tools (cdrtools / dvd+rw-tools / udftools) to do it's job then it could at least be more specific about it's claims and capabilities (BD support).

I have a gut feeling that writing ANY image to ANY CD/DVD/BD media is possible with current state of technology and that this behavior should be considered K3b's bug.

I took the matter to Cdrtools user support mailing list and CD-record (cdwrite) mailing list. I got several responses which all confirmed my suspicions.

Linux has several tools which can burn ANY image to ANY media - no questions asked. It is K3b's fault that its "Burn Image" module considers perfectly normal BD50 ISO image "unusable".