GNOME Bugzilla – Bug 590385
Fails to recognize blank disk media
Last modified: 2018-09-21 16:38:47 UTC
Please describe the problem: Riddle me this, Brasero. For some reason, the program will not recognize some blank disc media. (The media in question here is a Memorex music CD-R). Nautilus recognizes the blank disc, but Brasero cannot use it. Steps to reproduce: 1. Buy a stack of Memorex music CD-Rs. Insert one into your PC. 2. Get an audio CD image (in this case, a TOC for a CDDA disc). 3. Right-click and choose "write to disc". 4. Brasero says "there is no recordable disc inserted." Actual results: I cannot actually burn the CD, since Brasero can't recognize the blank disc. Expected results: Brasero (or its underlying libraries) should always be able to recognize a blank disc. Since Nautilus recognizes the blank disc, it makes no sense why Brasero cannot. Does this happen every time? This happens sporadically. Some of my memorex CDs, for example, are recognized, but some aren't. Other information: I have no idea why Brasero cannot use some disc media, but since Nautilus is obviously saying "there's a blank disc here", Brasero must see something wrong that Nautilus does not. (Or Brasero is just wrong.) Maybe Brasero could have a useful message like "This blank CD media cannot be used", rather than contradicting Nautilus (and common sense).
Created attachment 139635 [details] Screenshot of Brasero not recognizing disc As you can see, this screenshot is very confusing. Nautilus sees a blank disc, but Brasero does not.
In any case of doubt, the best idea is to ask cdrecord to report the media manufacturer and the current media state. The media manufacturer is retrieved by calling: cdrecord -atip The current media state is retrieved by calling: cdrecord -minfo or both information in one call to: cdrecord -v -minfo The -minfo option has been added in November 2006 and as many Linux distributors publish extremely oudated software, you may need to first install recent cdrtools from: ftp://ftp.berlios.de/pub/cdrecord/alpha/ http://cdrecord.berlios.de
I apologize, but I'm running Fedora's cdrkit from Rawhide, rather than cdrtools, so I'm not sure I can do that. wodim --version says it is cdrtools-2.01.01a03-dvd compatible, but it does not have the -minfo option in cdrecord. However, I must ask, if you don't mind. What does this option have to do with Brasero? I finally tried K3B and it recognized the media just fine, and I thought it used the same command-line tools that Brasero does. If Brasero and K3B get different results using the same command-line tools, I don't think it's the command-line tools at fault.
Thanks for the report. I'm having some hard time recently with the port from HAL to GIO. The idea was to associate a GDrive to a BraseroDrive and a GVolume to a BraseroMedium. Unfortunately when the disc is blank (and only then), GIO does not create a GDrive object, just a GVolume. This is what is at the heart of the problem for now. I'm on it but it may require changes to GVFS to work perfectly. @Jud: I'm running Fedora too and I can see the problem too. k3b uses a different way (still HAL probably) to find all drives and media. What Joerg suggested was to check with cdrecord if your drive was recognized with cdrecord and I'm sure it will be. That's not relevant though in this case.
*** Bug 590101 has been marked as a duplicate of this bug. ***
If you are running wodim, you are running more than 5 year old software with plenty of well known bugs (most of them have been introduced into wodim by the creators of this cdrtools fork) and wodim misses most of the features that are needed in order to debug problems. k3b for good reasons first looks for the original cdrtools before loking for other CD/DVD/BluRay writing software. If you look at the brasero bug list, it seems that 1/4 of all problems are directly or indirectly related to wodim. If you don't know the reason for a problem, it is a good idea to first check for the constraints of the problem using software that definitely works. cdrecord therefore is a good choice. @Philippe: hald in general has well known design bugs, hald on Linux in addition has fatal implementation bugs. As Sun did cooperate with me, we could avoid to duplicate the hald implementation bugs from Linux when hald was ported to Solaris.... If there is a new system, it seems to be a good idea if the people behind that software cooperate with me in order to avoid to duplicate mistakes from the past. I have 24 years of experience with SCSI devices and driver implementations, I wrote the first known SCSI pass through kernel driver in 1986 and for this reason I know many if not all of the problems in this area.
@Philippe: I had heard about that transition. If I may ask, why would this cause problems with some blank discs and not others? If you're right, I would expect Brasero to never detect a blank disc, since GIO won't show any GDrive objects for blank media (from your explanation). But I am certain it detected some of the three CD-Rs that I toasted yesterday (although this was brasero 2.26.3. I upgraded to 2.27.5 to see if it would help before I filed the bug, so perhaps 2.27.5 truly cannot detect blank discs anymore. Not sure if you started the HAL emigration in 2.26.3).
This is a GVFS problem: I haven't had any certain explanation so far. But I saw the same problem and I monitored the signals emitted by GVolumeMonitor ("drive-disconnected", "drive-connected") and the GDrive returned by g_volume_monitor_get_connected_drive (). It turns out that (and those are certainly bugs but I want to discuss the issue with one of the GIO maintainer before and he is not available at the moment): - GVFS emits "drive-disconnected" and "drive-connected" signals on ejection and insertion - GVFS for some reason does not return GDrive when they are blank or at least, from your comments, not always. It does only return a GVolume (and nautilus only uses these GVolumes which maps volumes on the medium not drives). This is not true when there is data or when the drive is empty. I'm working on a workaround based on the fact that it still does return a GVolume for blank discs. But I want to test it thoroughly first and I hope fix it with the help of a GVFS maintainer in GVFS in a near future. Why GIO you may ask? for portability reasons as some OSes will keep HAL and linux distros will now use DeviceKit; thanks to GIO I don't have to write two backends. NOTE: brasero 2.26.3 only relies on HAL not GIO for disc monitoring and is perfectly fine. That's only brasero 2.27.x series.
I finally managed to work around the GIO/GVFS problem in master for 2.27.90. Please as soon as you can make sure it does work for you too and feel free to reopen the bug if the problem is still there. Thanks
Philippe: I pulled git and it fixes it for me. This should be passed on to Ubuntu. Thank you! To those testing, ensure you remove existing libbrasero libraries by doing "sudo apt-get remove brasero libbrasero-media0", or equiv. in your distro. Otherwise the new brasero binary will be looking at your old brasero libraries.
Sorry, minor sequitur: How exactly do you pull the master branch of Brasero? "git clone git://git.gnome.org/brasero" only gives 2.27.5.
(In reply to comment #11) > Sorry, minor sequitur: > > How exactly do you pull the master branch of Brasero? "git clone > git://git.gnome.org/brasero" only gives 2.27.5. > Yes that's the current brasero master.
Pulling from master fixes the CD detection...almost. I pulled from master last night, so here's my result. When I right-click on a disc-image (TOC) file... 1. Select "Open with Brasero." "Image Burning Setup" window comes up. Briefly says "Searching for available discs...", then detects the blank CD. Success! BUT. 2. Instead, select "Write to Disc" from the Nautilus menu. "Image Burning Setup" window comes up. Never says "searching for discs." Never detects the blank CD. So this bug is still broken for one menu option. Why does Brasero fail to detect the blank disc when I specifically choose the "Write to Disc" option, but works normally otherwise?
Yes, the bug still happens for burning a DVD from contents. But, the image burn works.
I can still burn the image as well, if I plainly open the file. But it does not make sense that -opening the image with Brasero- works while -selecting 'Burn Image' on context menu- does not.
I am currently experiencing this bug with brasero 2.27.9 Ubuntu Karmic aplhas It will not recognize the blank disk under any condition, if u need any info from me let me know. top of cdrecord: Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'LG ' Identification : 'CD-RW CED-8042B ' Revision : '1.07' Device seems to be: Generic mmc CD-RW.
Just in case you do not know...... this is not the output from cdrecord but from the defective fork "wodim". If you like to use the original cdrecord, get it from: ftp://ftp.berlios.de/pub/cdrecord/alpha/ http://cdrecord.berlios.de
I reopened the bug then. The comment from Jud Craft makes me hopeful. I had reports that indeed on ubuntu the problem is still there so eric, could you attach a log (brasero --brasero-media-debug > log 2>&1) to this bug please?
Created attachment 141665 [details] Brasero log Here is the output. Also Gnomebaker doesn't seem to have a problem if that helps rule anything out. Thanks for your work on this.
Glad to hear it's reopened. I'm not familiar with using patches, but I can try pulling from master to help test if something changes.
Have the latest changes (in brasero-2-28 branch) fixed the problem?
(In reply to comment #21) > Have the latest changes (in brasero-2-28 branch) fixed the problem? The problem has not been fixed for me in 2.28 on Ubuntu. If you need any information from me just let me know. Thanks. Brasero still does not detect my blank CD
@Eric Hickman: Since a lot has changed could you run "brasero --brasero-media-debug > log" and attach log to this bug while a blank disc is inserted please? Thanks in advance.
Created attachment 143930 [details] brasero debug log 2.28
Thanks I read your log and it's really strange; the problem seems to be different in your case as some MMC commands entirely fails (which could mean bad firmwares or too old drives). Could you correct this assumption if it is false please? You have two optical drives (/dev/sr0 and /dev/sr1). Now a couple of questions: which one is the burner? sr0, sr1, both? Your burner(s), how old are they/is it? Can they write DVDs for example? What is its/their brand/model? Does brasero not recognising blank discs happen with all types of discs or just some? Thanks.
Created attachment 150430 [details] out put of dmesg with annotation
Sorry Philippe for vanishing on you. Ill take my lumps. Sr0 is a DVD reader only brand: Pioneer corp model: DVD-115 age: manufactured Nov of 2000 Sr1 is a cd-rom CD-R/RW (reads and writes) brand: LG model:CED-8042B age: manufactured Oct 1999 Iv added what i think are the important bits from dmesg in an attachment
(In reply to comment #27) Sorry for the extra email spam. I have tried 3 different blank cds both cd-R and cd RW and both are not detected.
Bringing this bug back up. A bug has been reported on Ubuntu's Launchpad that appears to match this bug. The affected system is Ubuntu 9.10 64-bit, running Brasero 2.28.2. Details about this bug can be found at https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/514782
Reopening as I think the requested information has been provided.
when I ran brasero from terminal there was this warning: GVFS-RemoteVolumeMonitor-WARNING **: cannot open directory /usr/share/gvfs/remote-volume-monitors: Error opening directory '/usr/share/gvfs/remote-volume-monitors': No such file or directory Brasero saw the blank cd after installing gvfs-backends. I also removed existing libbrasero libraries by doing "sudo apt-get remove brasero libbrasero-media0" but maybe it is not needed.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/59.