IMHO, this is may not be a bug in HAL, but a bug in nautilus-cd-burner, probably introduced at version 2.15.
I have successfully written CD using nautilus-cd-burner 2.14.3 on my Feisty system.
The problem appears to be that alternative strategies used to be adopted if volume.disc.capacity was not present, and this is no longer the case (see the function nautilus_burn_drive_get_media_size in nautilus-burn-drive.c (2.14.3), and compare with monitor_set_drive_media in nautilus-burn-drive-monitor.c (2.18.2))
I think it is a nautilus problem because the volume.disc.capacity property is optional in HAL, as can be seen from the spec http://webcvs.freedesktop.org/hal/hal/doc/spec/hal-spec.html?view=co#device-properties-volume-disc
An alternative approach may be to add some config to HAL for the missing drives, but this is going to be very piece-meal.
IMHO, this is may not be a bug in HAL, but a bug in nautilus-cd-burner, probably introduced at version 2.15. disc.capacity was not present, and this is no longer the case (see the function nautilus_ burn_drive_ get_media_ size in nautilus- burn-drive. c (2.14.3), and compare with monitor_ set_drive_ media in nautilus- burn-drive- monitor. c (2.18.2)) disc.capacity property is optional in HAL, as can be seen from the spec http:// webcvs. freedesktop. org/hal/ hal/doc/ spec/hal- spec.html? view=co# device- properties- volume- disc
I have successfully written CD using nautilus-cd-burner 2.14.3 on my Feisty system.
The problem appears to be that alternative strategies used to be adopted if volume.
I think it is a nautilus problem because the volume.
An alternative approach may be to add some config to HAL for the missing drives, but this is going to be very piece-meal.
David