ubuntu doesn't recognize my blank cd.

Bug #14840 reported by Markus Bertheau
34
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
Medium
Martin Pitt

Bug Description

I downloaded an ISO file and wanted to burn it. Ubuntu tells me to insert a
blank CD in the drive, but there already is a blank CD in the drive. It doesn't
let me burn.

http://bugzilla.gnome.org/show_bug.cgi?id=172429: http://bugzilla.gnome.org/show_bug.cgi?id=172429

Revision history for this message
Daniel Robitaille (robitaille) wrote :

Does it do that with every blank CD you put in the drive, or just a particular type?

Is it a new thing due to a recent update, or you have never been able to burn
before?

Are you using Warty or Hoary?

Revision history for this message
Markus Bertheau (twanger) wrote :

(In reply to comment #1)
> Does it do that with every blank CD you put in the drive, or just a particular
type?

Well, I just have this type of CDs around. I have ubuntu installed for just a
week now; I didn't try other blank CD types.
>
> Is it a new thing due to a recent update, or you have never been able to burn
> before?

I remember to have tried several days ago; it failed with the same error message.
>
> Are you using Warty or Hoary?

Hmm, the latest development preview thingie. I always update everything when
that icon appears in the top panel.

I'm noticing the same on FC rawhide. The device manager says, the size of the
blank cd volume is 2048. I think that number should be more like 700*1024*1024,
and if it was, nautilus-cd-burner wouldn't complain.

Revision history for this message
Sebastien Bacher (seb128) wrote :

can you look in the device manager what is the value of "volume.disc.is_blank"
for this volume ?

Revision history for this message
Markus Bertheau (twanger) wrote :

(In reply to comment #3)
> can you look in the device manager what is the value of "volume.disc.is_blank"
> for this volume ?

It says 1.

Revision history for this message
Markus Bertheau (twanger) wrote :

Created an attachment (id=1968)
Screenshot of error dialog

Revision history for this message
Markus Bertheau (twanger) wrote :

Created an attachment (id=1969)
Device Manager Screenshot for blank CD

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the screenshots and comment, I've opened a bug upstream with all
that: http://bugzilla.gnome.org/show_bug.cgi?id=172429 and I'll let you know
when they give some feedback.

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 16529 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream is asking if you can attach the output of lshal with and without the
blank CD

Revision history for this message
Sebastien Bacher (seb128) wrote :

hal bug, reassigning to the right component

Revision history for this message
Chris McGee (sirnewton-01) wrote :

Here's the diff of my lshal before and after inserting my blank rewritable CD:

2c2
< Dumping 87 device(s) from the Global Device List:
---
> Dumping 88 device(s) from the Global Device List:
3a4,36
> udi = '/org/freedesktop/Hal/devices/block_22_0'
> volume.policy.desired_mount_point = 'cdrecorder' (string)
> info.udi = '/org/freedesktop/Hal/devices/block_22_0' (string)
> volume.disc.is_rewritable = true (bool)
> volume.disc.is_appendable = false (bool)
> volume.disc.is_blank = true (bool)
> volume.disc.has_data = false (bool)
> volume.disc.has_audio = false (bool)
> volume.disc.type = 'unknown' (string)
> volume.size = 2048 (0x800) (uint64)
> volume.block_size = 2048 (0x800) (int)
> volume.num_blocks = 4 (0x4) (int)
> volume.is_disc = true (bool)
> volume.is_mounted = false (bool)
> volume.mount_point = '' (string)
> volume.label = '' (string)
> volume.uuid = '' (string)
> volume.fsversion = '' (string)
> volume.fsusage = 'filesystem' (string)
> volume.fstype = '' (string)
> info.product = 'Volume' (string)
> info.parent = '/org/freedesktop/Hal/devices/block_Hewlett-Packard CD-Writer
Plus 9300-YM0039CRZ0' (string)
> info.category = 'volume' (string)
> info.capabilities = 'block volume' (string)
> info.bus = 'block' (string)
> block.no_partitions = true (bool)
> block.have_scanned = false (bool)
> block.is_volume = true (bool)
> block.device = '/dev/hdc' (string)
> block.major = 22 (0x16) (int)
> block.minor = 0 (0x0) (int)
> block.storage_device = '/org/freedesktop/Hal/devices/block_Hewlett-Packard
CD-Writer Plus 9300-YM0039CRZ0' (string)
>
368a402
> volume.is_partition = false (bool)
406c440
< block.have_scanned = false (bool)
---
> block.have_scanned = true (bool)
1591c1625
< Dumped 87 device(s) from the Global Device List:
---
> Dumped 88 device(s) from the Global Device List:

Chris

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 16452 has been marked as a duplicate of this bug. ***

Revision history for this message
Martin Pitt (pitti) wrote :

Markus, do you still have this problem in Breezy? If so, can you please attach
the "lshal" output with the current hal again?

Revision history for this message
Nelson Benitez (gnel) wrote :

Hi,
I have this bug on gentoo and I have put a comment[1] where I came to a
conclusion this is a file permission error on the device file. Maybe someone can
test if that is what is happening on ubuntu.

[1] http://bugs.gentoo.org/show_bug.cgi?id=100460#c7

Revision history for this message
Martin Pitt (pitti) wrote :

Hi Chris!

(In reply to comment #11)
> Here's the diff of my lshal before and after inserting my blank rewritable CD:
> > volume.disc.is_rewritable = true (bool)
> > volume.disc.is_appendable = false (bool)
> > volume.disc.is_blank = true (bool)
> > volume.disc.has_data = false (bool)
> > volume.disc.has_audio = false (bool)

But that actually looks fine. What is not working for you?

Markus, I still need the lshal output from you, and also the output of 'ls -l
/dev/hd* /dev/cdrom' (to check device permissions).

Revision history for this message
Martin Pitt (pitti) wrote :

No answer for a month, so I close this bug for now to clean up Bugzilla. I will
reopen the bug if I get an answer.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.