User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20061201 Firefox/2.0.0.6 (Ubuntu-feisty) Build Identifier: This was reported on Launchpad : https://bugs.launchpad.net/ubuntu/+source/xfburn/+bug/133461 by : https://bugs.launchpad.net/~l-david-andersson Xfburn ver 0.2.0 - error status propagation in xfburn or maybe wodim Create a composition in Xfburn, click "Burn composition", select a Burning device that does not support writing (a cd or dvd read-only device), click "Burn composition". The dialog "Burn data composition" immediately says "Operation finished" and no error message is shown, but nothing was burned. A similar thing if I try to burn with no cd in the tray. It opens and closes the tray and then says "Operation finished". A similar thing if I try to burn 200MB onto a CD that is already almost full. Now the drive do spin a bit, then the dialog says "Operation finished", but listing files on the cd the 200MB file is not there. Workaround: A competent user may find out if the operation succeded or not, and why, by looking at the log in "View output". These tests is in xubuntu 7.10 tribe 4, but I recall the same behaviour in xubuntu 4.07 which also uses Xfburn 0.2.0. $ xfburn --version This is xfburn version 0.2.0 for Xfce 4.4.1 built with GTK+-2.10.11, linked with GTK+-2.11.6. $ wodim --version Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd Wodim 1.1.6 Copyright (C) 2006 Cdrkit suite contributors Based on works from Joerg Schilling, Copyright (C) 1995-2006, J. Schilling $ uname -a Linux xubuntu 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux Reproducible: Always Steps to Reproduce:
Thank you for your bug report. Would you be so kind to try reproducing this with svn?
I would be pleased to, but xfburn seems to need the latest version of libisofs which fails to build on my system.
(In reply to comment #2) > I would be pleased to, but xfburn seems to need the latest version of libisofs > which fails to build on my system. > What version of libisofs did you try? 0.6.2.1? If so, please do paste the error(s) encountered when compiling. Do note that you will need libburn (0.6.2 and 0.6.4) to compile libisofs 0.6.2.1.
I finally managed to compile xfburn using the debian unstable packages for libburn and libisofs. When trying to burn with and empty drive, a nice dialog pops up says that the drive is empty. THis part of the bug is fixed. When trying to burn with a drive that cannot do it, the dialog disappeared, the files I added to the burn list were all erased from the list and replaced by my whole home directory. Nothing else happened.
Thank you for testing. Will look into this before new release.
In fact, after testing this a second time, selecting a drive that can't burn now leads me to a segmentation fault with the following error in terminal: (xfburn:22672): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed (xfburn:22672): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.14.1/gobject/gtype.c:3339: type id `0' is invalid (xfburn:22672): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced zsh: segmentation fault (core dumped) xfburn I can get a backtrace if you need it.
The drive which cannot burn composition/image shouldn't even appear in the list. Will fix before release.
Is this still present in trunk? I added code to check for burn errors, and Mario added code to only add drives that can burn to the device list, but I'd like to have a confirmation before I close this.
Fixed.