Brasero Freezes at "Finalizing"

nightmarcus · #1 4th April 2010, 03:15 AM

I recently tried to burn an ISO image to a DVD. Everything seemed to be going fine except Brasero froze at "Finalizing". It stayed there for about 10 minutes before I gave up. When I hit cancel nothing happened. When I tried to eject the drive nothing happened. Not until I shut the computer down and restarted was I able to open my DVD drive. Upon trying to read the disc no computer shows that it has anything on it.

mouse_runner · #2 4th April 2010, 08:21 AM

what version do you use?

nightmarcus · #3 4th April 2010, 11:54 AM

It's version 2.28.3, the one from the default F12 repos.

hugo87 · #4 9th April 2010, 04:48 AM

Same issue here, also Fedora 12, Brasero F12 "stock" version.

mouse_runner · #5 9th April 2010, 05:17 PM

k3b is a good alternative.

did you guys try that?

---------- Post added at 06:17 PM CDT ---------- Previous post was at 06:08 PM CDT ----------

version 2.30.0 has been released:
http://koji.fedoraproject.org/koji/b...buildID=164351
rebuild the rpm by rpmbuild --rebuild
and install it.

does that solve the problem

nightmarcus · #6 14th April 2010, 06:18 AM

Yeah I've used K3b before, but I'd really like to be able to use Gnome's built in "Right click, write to disc" feature. Right now I installed Gnomebaker which seems to be working pretty good.

***DBelton*** · #7 15th April 2010, 07:23 PM

I am having this same issue as well.

On CD's, it errors on finalizing but ends and the CD is usable. DVD's, it just hangs and the DVD is unusable.

F12 with the brasero in the fedora repos. everything is updated to the latest version.

MitchLoft · #8 6th May 2010, 06:15 PM

I'm having an issue with Brasero on FC11_64 - trying to copy a CD, it reads the original CD (home burned with a couple of .pdfs on it) opens and prompts for the blank disk, but when the blank is inserted and the drawer closed, it looks like it is getting ready to start writing, but never does. The drive activity light stays on - apparently forever - and the process can't be killed, or the drive returned to usability without rebooting. Standard Brasero with the FC11_64 distro.

robert-e · #9 6th May 2010, 08:19 PM

Brasero has been doing this since (at least) F8 and through to F12, except perhaps F9, which I skipped. Give up on Brasero; it does not get fixed: use Gnomebaker in Gnome, or K3b in Kde; both work. You could install Keb in Gnome, but it brings in a lot of Kde stuff, which you may not want.
I tried Brasero each time I installed a newer version of Fedora, and each time it failed. This on two laptops, one a 32 bit install, and the other a 64 bit install, and on one 32 bit desktop.

It is just one of those fedora things...indeed, try Brasero each time a new fedora come out, and if it does not work...just dont sweat it, and install another burning program.

Regards,
Bob

MitchLoft · #10 6th May 2010, 10:14 PM

I've already gone on to something else. I -used- to like Brasero because it was very simple to burn an .iso. Not so much anymore...

petermholmes · #11 14th May 2010, 05:37 AM

What was the default on F10? That was working fine for me. Brasero on F12 just plain sucks. And if they're never going to fix it, the least they could do is throw it away.

***DBelton*** · #12 14th May 2010, 03:49 PM

I have had Brasero give me all different kinds of errors so I have stopped using it and use GnomeBaker and k3b for all of my burning.

I have had Brasero tell me to insert a blank CD when there was one in the drive, error on finalizing, hang halfway through the burn, and even hang before starting to burn.

To me, that behaviour is unacceptable for a software package that has been released as a finished package. I would expect these kinds of problems from alpha or beta code, but not release code. Especially one that is set to be the default on a fresh Fedora/Gnome install. The Fedora team either needs to insure that Brasero works properly or replace it with something that works.

petermholmes · #13 14th May 2010, 10:48 PM

Quote:

Originally Posted by DBelton

I would expect these kinds of problems from alpha or beta code, but not release code. Especially one that is set to be the default on a fresh Fedora/Gnome install.

I agree completely.

I understand fully that Fedora always has been and will always be on the bleeding edge of technology, but in this case the patient's blood loss killed him long ago.

***DBelton*** · #14 16th May 2010, 04:19 AM

having grown up and being around computers for the past 45 years with 25 of those years working in the programming field, I know there is no way to make a bug free application that will still be flexible and meet different users needs. And I expect to have to do some amount of tweaking and correcting things in Fedora because it is a 'bleeding edge' distro. That's the price to pay for the new toys.

But Brasero now has been broken for the past 3 releases that I know of. I do try it out every so often to see if it is fixed, but I am getting a big stack of coasters piling up because of it.

I am probably more tolerant of programming errors than a lot of people because I am on the other side of the fence as well, but there is a point where I have to say enough is enough and hope the Fedora team pulls Brasero as the default until it gets fixed and replace it with one that works.