GNOME Bugzilla – Bug 164352
doesn't want to write on a rewritable disc
Last modified: 2005-02-10 20:09:08 UTC
Since the update to 2.9.4: * put a RW disc in the drive * try to record some files on it => "Insert rewritable or blank disc Please put a rewritable or blank disc, with at least ... MiB free, into the drive. cancel retry disc" Retry get back on the same dialog. The drive has been mounted by gnome-volume-manager. After umounting the CD I get the dialog once and retry works. The previous version used to unmount the CD correctly and in all the case the message is wrong since a rewritable disc is in the drive.
This actually seems to be a GUI problem, as clicking retry several times does eventually burns the cd, after it was unmounted ofcourse.
This is a side-effect with checking the size of the disc before it's umounted, I think. William?
Yes, I think it is. I should be getting my rewrite-capable drive in the mail tomorrow. I should be able to look into this soon.
This should solve the problem. If you still have problems with this issue please reopen this bug. Thanks. 2005-01-26 William Jon McCann <mccann@jhu.edu> * nautilus-cd-burner.c (media_type_matches, request_media) (burn_cd): Try to unmount busy volumes before asking for media. Add comparison between media type and is_blank to media request. (Closes: #164352) * nautilus-burn-recorder.c (nautilus_burn_recorder_wait_for_insertion): Move private drive unmounting functions to burn-drive. * nautilus-burn-drive.c (nautilus_burn_drive_get_media_type_from_path_full) (nautilus_burn_drive_get_media_type_from_path) (nautilus_burn_drive_get_media_type) (nautilus_burn_drive_hal_get_media_type_full) (nautilus_burn_drive_get_media_type_full) (nautilus_burn_drive_get_media_type_and_rewritable) (free_unmount_data, unmount_done, unmount_timeout, find_command) (unmount_thread_start, nautilus_burn_drive_unmount): Add ability to query media for is_blank, has_data, has_audio. Move drive unmounting from burn-recorder to here and expose api.
right, works fine now, thanks
*** Bug 166458 has been marked as a duplicate of this bug. ***