xfburn failure [Solved]

[Ric95]

I just emerged xfburn and on every try it fails.
Preferences show the correct device.
FIFO buffer fills, the device buffer creeps up to 100%, then it halts with an error window.
Here is the full text from terminal: (burning 1.55GB data onto a 4.3 GB disc)

ric@localhost ~ $ xfburn
** Message: Thunar-VFS not available, using default implementation
** Message: Using HAL
** Message: Using gstreamer transcoder.
** (xfburn:2510): WARNING **: [FATAL] 131357: SCSI error on write(656,16): [5 21 00] Lba out of range (0)

What can fix this?

[disi]

I googled a little, sounds interesting

Possible reasons:
1. bad media (tried a different CD/DVD-R)?
2. 1.55GB should fit onto the DVD-R, is it a DVD-R or CD-R or DVD-RAM?
3. cables, firmware on the burner, is it an external one via usb?
4. check your kernel config, in the device driver for scsi is cdrom supported and or sata section enable dma default?

[Rexilion]

And as a last resort you could try to install thunar to provide the thunar-vfs.

[disi]

Oh sorry

Anyway, if you do not want to use thunar, I use xcdroast as an independent cd burn gui.

[Ric95]

Thanks guys.
A little more research shows a few people having trouble with the newer version of xfburn. Its under development, I guess if it works, it works.
I like apps that aren't too dependent on gnome or kde, I do use thunar, so I'll check out thunar-vfs and xcdroast.

[Ric95]

xcdroast had gui trouble.
It turned out that emerging cdrtools enabled xfburn to do the job
Its wierd that xfburn didn't list cdrtools as a dependency. Maybe it assumed I would have already installed it??
Oh well. Thanks guys, this is solved

[Rexilion]

xcdroast had gui trouble.
It turned out that emerging cdrtools enabled xfburn to do the job
Its wierd that xfburn didn't list cdrtools as a dependency. Maybe it assumed I would have already installed it??
Oh well. Thanks guys, this is solved

Yeah, that's an error in the ebuild. Thanks for posting the solution

[96140]

--

[Rexilion]

It's not a bug in the ebuild. Xfburn requires [uri link=http://libburnia-project.org]libburn[/url], which is a separate burning library + utilities. Some apps use cdrecord or cdrkit, and some use libburn/libisofs. There is a virtual package for apps that can use cdrecord or cdrkit, since those are drop-in compatible. However, libburn's code is different from both of those. It's not as easy to replace.

So? Then how do you explain the fact that xfburn fails with libburn but works with cdrtools? I (a total n00b) would just think that the libburn backend is broken, and that the ebuild should be changed to use the virtual for cdrtools/cdrkit as a backend. Because it seems that xfburn prefers cdrtools over libburn (same for brasero, in which the libburn backend has to be explicitly activated through gconf). I know, this is a so called 'bad practice' for a distribution, because this needs to be fixed in the code, but that should not bother the user unless he insists xfburn to use the libburn backend. The user just doesn't want to figure out which combination of burning backends works, whenever one is broken it should not be used by default.

Or am I totally missing the point here?

[Anon-E-moose]

It's not a bug in the ebuild. Xfburn requires [uri link=http://libburnia-project.org]libburn[/url], which is a separate burning library + utilities. Some apps use cdrecord or cdrkit, and some use libburn/libisofs. There is a virtual package for apps that can use cdrecord or cdrkit, since those are drop-in compatible. However, libburn's code is different from both of those. It's not as easy to replace.

I'm using app-cdr/cdrkit with virtual/cdrtools and libburn-0.7.8 and xfburn-0.4.3 works fine for me (sata dvd burner)