GNOME Bugzilla – Bug 594415
brasero does not eject disc at the end of successful burning.
Last modified: 2010-06-28 19:39:20 UTC
Created attachment 142643 [details] Log of burning four-track audio disc Brasero does not eject the disc when "eject disc after burning" is checked in the burn dialog. Actual Results: Disc stays in the disc drive. Brasero's burning status says 100% Complete. Expected Results: Brasero should eject the darn disc. * If I recall correctly, Linux/kernel/GVFS/whatever will not re-read the disc as a real audio/data disc until the disc is ejected and reinserted. Why it can't figure this out, I dunno. But since that's the way it is, Brasero really should eject the disc when told to. Other Notes: At line 1991 in the attached log, Brasero tries to eject the disc but cannot: GDrive not found. Could this be because of the HAL->GVFS switch? From this bug [1] it does appear that GVFS in fact has trouble recognizing audio discs -- the drive device disappears when the audio cd is detected (both abstractedly in GVFS and quite user-visibly in Places/Computer). Perhaps after the CD is burnt, GVFS detects the audio cd (though this would violate *), glitches up, and disconnects the GDrive object. Then when Brasero tries to eject the drive, it cannot. This needs to be fixed, possibly in both GVFS (fix the stupid disc detection) and Brasero (though I'm not sure how -- a notification that the disc could not be ejected might be useful. There should be nothing that stops the disc from being ejected, so if it fails, that should trigger a user-visible error). 1. http://bugzilla.gnome.org/show_bug.cgi?id=594398
At this previous bug, I quote comment #4. [1] "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." Could it be that Brasero still depends on GDrives when ejecting? 590385 fixed the disc detection, but perhaps ejection is still looking for those non-existed GDrives (which are not available when a blank disc is in the tray). 1. http://bugzilla.gnome.org/show_bug.cgi?id=590385
(In reply to comment #1) > At this previous bug, I quote comment #4. [1] > > "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." > > Could it be that Brasero still depends on GDrives when ejecting? 590385 fixed > the disc detection, but perhaps ejection is still looking for those non-existed > GDrives (which are not available when a blank disc is in the tray). > Yes that's exactly what is at the root of the problem, the volatility of GDrives. There is actually a bug against GDU about that. This was meant as a filtering feature as far as I understood it.
I have to take back the above comment it seems. I found out by chance that brasero was leaking file descriptors (because of the above volatility but still that's brasero's fault). It seems to have improved ejection for me. Fixes are in branch gnome-2-28 in git. Could you test it and let me know if that works better? Thanks.
Created attachment 147005 [details] Dependencies.txt as generated by apport and fed into launchpad
Created attachment 147006 [details] ProcMaps.txt as generated by apport and fed into launchpad
Created attachment 147007 [details] ProcStatus.txt as generated by apport and fed into launchpad
Created attachment 147008 [details] XsessionErrors.txt as generated by apport and fed into launchpad
coming over from launchpad bug Bug #474233..... Bug Description Binary package hint: brasero When burning a disc (audio, data, or from iso-image) I always check the 'eject after burn' option, but it never does eject. I have to use the button on the drive to get my new disc out. The discs themselves are OK. I'm using Ububtu 9.10 Karmic (was beta, now stable) on Dell Latitude 131L, in the AMD64 version. enjoy Tom ProblemType: Bug Architecture: amd64 Date: Wed Nov 4 15:02:26 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/brasero Package: brasero 2.28.1-0ubuntu1 ProcEnviron: LANGUAGE=en_GB.UTF-8 LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: brasero Uname: Linux 2.6.31-14-generic x86_64
@Tom Louwrier: Why are you linking to an epiphany bug? Anyway, this bug should be fixed since 2.28.2. I added some more fixes and changes and so far it has worked for me flawlessly whereas I indeed had some problems before. Please test this version and let me know if it works better for you. Thanks
@Philippe Sorry, I wasn't pointing to bug 474233 on bugzilla but bug 474233 on Launchpad, as stated in 'launchpad bug 474233'. The link was created automagically by bugzilla from my hand typed text. I filed a bug report in launchpad that Brasero does not eject after burning. One of the maintainers there asked me - if my bug (on launchpad) was the same as this one (on bugzilla) - if yes, would i be so kind as to copy my bug report over to this one. Being so kind, I created an account on bugzilla and copied my report over, including the files that were uploaded to launchpad by the apport tool. It would be nice to be able to link bugs across different trackers so they point to the right bugs and maybe even keep comments and status synced. BTW; current version of Brasero in Ubuntu 9.10 is 2.28.2 (just checked to be sure), and I can inform you that it does not eject after burning a disc succesfully. enjoy Tom
Today I burned a DVD (just straight data files on it) and that ejected OK. The ones that didn't eject were all audio CD's, with mp3 and wma files as input. Hope this helps to narrow it down. cheers Tom
Reopening as I think the necessary information has been provided.
Hi, This is happening to me and has been for a while. Currently running ubuntu 9.10 Brasero 2.28.2 It works OK sometime and not at other times. If when I click burn is sometimes ask me to select drive, then it DOES eject, sometime I don't get that option and it doesn't. ( I only have one drive) TIA
I did some recent changes in 2.30.2 that seemed to improve things. There was especially a plugin that started whereas it should not have. Could you give it a try (it is still in git stable/master). Thanks
2.30.1 seems to be working fine thanks for all yer work on this.
Closing as OBSOLETE then. Thanks.