Bug 297057

Summary: double-layer media not recognized
Product: [Applications] k3b Reporter: Steve Kelem <steve>
Component: Burning/HardwareAssignee: k3b developers <k3b>
Status: REPORTED ---    
Severity: major CC: daliz, trueg
Priority: NOR    
Version: 2.0.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Steve Kelem 2012-03-29 16:23:48 UTC 
User-Agent:       Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Build Identifier: 

I have a Pioneer BDR-206D dual-layer blu-ray writer. I'm trying to write to a new Verbatim 50GB BD-R DL blu-ray disk.
I'm trying to write a 26.6GB iso image to the drive.
K3b complains:
Waiting for Disk - D3b
Found medium: Empty BD-R medium
Please insert an empty medium of size 26.5 GiB or larger into drive
PIONEER BD-RW BDR-206D (/dev/sr1). 

Reproducible: Always

Steps to Reproduce:
0. Use K3B to create an ISO image of the Data Project files.
1. Insert blank 50GB BD-R into drive.
2. Select "Burn Image" from inside k3b.
3. Select any speed (2X, 4X, auto).
Actual Results:  
I get the error popup that indicates that it knows there's an empty BD-R medium, but it doesn't recognize that it's big enough for the 26.6GB image, even though it's a 50GB disk.

Expected Results:  
It should have recognized the disk size and written the image.

OS:
3.0.0-17-generic #30-Ubuntu SMP Thu Mar 8 20:45:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Hannu T 2015-01-20 10:30:40 UTC 
I have noticed this also on k3b 2.0.2 / OpenSUSE 13.2 64bit / external Samsung SE-506CB drive. I can not proceed from the "insert blank media" popup even though there is a proper empty media in the drive. It happens with single layer BD-R too. Burning the same image on to the same disc with growisofs works ok.
Comment 2 Justin Zobel 2021-03-09 06:28:24 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.