After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 490853 - Brasero refuses to start burning showing a "File not found" error, sometimes (weird)
Brasero refuses to start burning showing a "File not found" error, sometimes ...
Status: RESOLVED FIXED
Product: brasero
Classification: Applications
Component: general
0.6.1
Other All
: Normal normal
: 0.6
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-27 17:12 UTC by Ariel
Modified: 2007-11-14 21:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ariel 2007-10-27 17:12:34 UTC
Please describe the problem:
Depending on the order I add my files, at times Brasero refuses to start burning, showing a "File not found" error. I think this has to do with the "Increase Windows compatibility" option being checked (which BTW, it would make Brasero more user friendly for newbies to have this checked by default). 



Steps to reproduce:
1. Open Brasero (you have to start from scratch) ... Create a a new data dvd project, add the follwing (you can create the files below with "touch", you don't need the real files to reproduce this)
2. Folder with name:
     Rugby World Cup 2007 - France vs Argentina (September 7,2007)
     containing these files:

Rugby World Cup 2007 - France vs Argentina (September 7,2007) [ SDTV (XviD) Freak ] 1st Half.avi

Rugby World Cup 2007 - France vs Argentina (September 7,2007) [ SDTV (XviD) Freak ] 2nd Half.avi

Then, drop files with this names and IN THIS ORDER:

Rugby Union-RWC(2007)-26-Pool D-Argentina vs Namibia-22 September.avi
RWC07-Arg-Ireland.1709352.divx
RWC(2007)-Pool D-Argentina vs Georgia-11 September.avi
 
3. Click Burn
4. To save a DVD, you can reproduce the error writing to a file image
5. Ensure "Increase compatibility with windows" is checked
6. Click burn
7. You will see "some files don't have a suitable name" etc; click OK 
8. You get the error message "File not found" and you are sent back to square one.





Actual results:
8. You get the error message "File not found" and you are sent back to square one.


Expected results:
Burn my disk! :)

Does this happen every time?
Yes

Other information:
Using ubuntu 7.10 final, fresh install.
Comment 1 Luis Medinas 2007-10-29 01:47:00 UTC
can you try to reproduce with svn trunk ?
Comment 2 Ariel 2007-10-29 23:56:11 UTC
I was able to check out the svn trunk sources, but when I run the ./autogen.sh to get the configure script, I get the error below, any hint on what I am doing wrong?

TIA



ari@ntl:~/Desktop/Builds/brasero-svn/brasero$ ./autogen.sh /usr/bin/gnome-autogen.sh
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.61
checking for automake >= 1.7...
  testing automake-1.10... found 1.10
checking for libtool >= 1.5...
  testing libtoolize... found 1.5.24
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.14.1
checking for intltool >= 0.30...
  testing intltoolize... found 0.36.2
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 0.22
Checking for required M4 macros...
Checking for forbidden M4 macros...
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.

Processing ./configure.in
Running libtoolize...
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Running glib-gettextize... Ignore non-fatal messages.
Copying file mkinstalldirs
Copying file po/Makefile.in.in

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

Running intltoolize...
Running aclocal-1.10...
configure.in:292: warning: macro `AM_GCONF_SOURCE_2' not found in library
Running autoconf...
configure.in:292: error: possibly undefined macro: AM_GCONF_SOURCE_2
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
ari@ntl:~/Desktop/Builds/brasero-svn/brasero$ 

Comment 3 Luis Medinas 2007-10-30 00:03:15 UTC
try sudo apt-get build-dep brasero

and try running autogen.sh and configure after.
Comment 4 Ariel 2007-10-30 04:28:11 UTC
Thanks, I could build svn trunk and checkinstall it.

The new stuff is looking really good, I couldn't crash it yet :), thanks guys for keeping it up!


With the new version I notice:

1) repeating the steps without having a blank DVD in the drive, after I click "Burn" and select "File Image as destination", all "Disk Options" appear grayed out, same as the Burn button (small bug#1)

2) after inserting a blank disk, and selecting "DVD" as destination, then the Burn button returned to normal, however the "Increase compatbility with windows" stays grayed out. It should allow me to check it and cut the filenames as appropriate (the previous version attempted to do this).

3) If after 2) I select "File image" again, now the "burn" button is normal, but again the "Increase compat..." is still grayed out. If I click burn, it generates the image with no error.

But I can't test the point, as brasero never allows me to use the "increase compatibility with windows" aka cut/trim the filenames, looks like a small bug (#2).

So the problem may still be lurking there, plus now we have a couple small new issues (see bug#1 and bug#2 above)

Thanks!

Comment 5 Philippe Rouquier 2007-10-31 10:44:51 UTC
2) and 3) are fixed in trunk now =)
I'll work on 1)
Comment 6 Ariel 2007-11-01 00:41:39 UTC
Just checked out the latest trunk version (450).

Noticed that if I click Burn with no dvd the drive, the Disc Options appear grayed out (which may be on purpose). If I then insert a blank dvd, the DVD is detected and the burn button turns to active, but the Disc Options stay grayed out. (little bug)

The only way to get the Disc Options not grayed is to hit Burn in the main project window with a black DVD already in the drive.

After this I can change the Destination to Image and keep "Increase compatibility with Windows", but I get an error if I try to Burn (write the image to disk), a new error possibly unrelated to the original one in this bugzilla entry:

  "Error while Burning"

Log:

Session starting:
	flags			= 8274 
	media type	= 0
	speed		= 22160000
	track format	= 1
	output		= /home/ari/brasero.iso	number of copies = 1

Checking session consistency (brasero_burn_check_session_consistency burn.c:1719)
Some flags were not supported (8274 => 8258). Corrected (brasero_burn_check_session_consistency burn.c:1784)
Flags after checking = 8258 (brasero_burn_check_session_consistency burn.c:1832)
BraseroMd5sum called brasero_job_get_output_type
BraseroMd5sum called brasero_job_get_current_track
BraseroMd5sum called brasero_job_get_action
BraseroMd5sum called brasero_job_get_action
BraseroMd5sum deactivating
BraseroMd5sum called brasero_job_get_output_type
BraseroMd5sum called brasero_job_get_current_track
BraseroMd5sum called brasero_job_get_action
BraseroMd5sum called brasero_job_get_action
BraseroMd5sum called brasero_job_get_action
BraseroMd5sum called brasero_job_get_input_type
BraseroMd5sum called brasero_job_get_current_track
BraseroMd5sum called brasero_job_set_current_action
BraseroMd5sum called brasero_job_set_progress
BraseroMd5sum called brasero_job_error
BraseroMd5sum finished with an error
BraseroMd5sum asked to stop because of an error
	error		= 0
	message	= "no message"
BraseroMd5sum stopping
Session error : unknown (brasero_burn_record burn.c:2223)
Comment 7 Philippe Rouquier 2007-11-05 10:50:17 UTC
I committed some fixes this morning for these issues to trunk. Could you check that please. Namely:
- the bug with the properties button getting/remaining grayed out 
- the above failure to create an image


As for the burn/properties buttons being grayed out when there is no proper disc loaded that's OK
Comment 8 Ariel 2007-11-06 01:15:18 UTC
Just checked the latest trunk as of now; now it goes a bit further but we have a new error.

I'm attempting to generate the same iso image as described above, with "Increase windows compatibility" checked. Without this option checked, life is still good.  Many people will still need it, I guess; including my pioneer divx player :) 

From the below, it seems it has to do with the handling of long "folder names" (perhaps the name cutting is only applied to "file names" as of now?); this folder name has 62 chars counting the spaces as 1 char, however below I see the %20 instead of the spaces so it might well exceed 64 if each space counts as 3 chars.



-----------------------------------




Session starting:
	flags			= 8274 
	media type	= (null)
	speed		= 22160000
	track format	= 1
	output		= /home/ariel/brasero.iso	number of copies = 0

Checking session consistency (brasero_burn_check_session_consistency burn.c:1713)
Some flags were not supported (8274 => 8258). Corrected (brasero_burn_check_session_consistency burn.c:1778)
Flags after checking = 8258 (brasero_burn_check_session_consistency burn.c:1826)
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_current_track
BraseroLocalTrack called brasero_job_get_input_type
BraseroLocalTrack no foreign URIs
BraseroLocalTrack stopping
BraseroGenisoimage called brasero_job_get_action
BraseroGenisoimage getting varg
BraseroGenisoimage called brasero_job_get_action
BraseroGenisoimage called brasero_job_get_current_track
BraseroGenisoimage called brasero_job_get_tmp_dir
BraseroGenisoimage called brasero_job_get_action
BraseroGenisoimage called brasero_job_set_current_action
BraseroGenisoimage called brasero_job_start_progress
BraseroGenisoimage got varg:
	/usr/bin/genisoimage
	-input-charset
	utf8
	-r
	-J
	-graft-points
	-D
	-path-list
	/tmp/brasero_tmp_K5TY0T
	-exclude-list
	/tmp/brasero_tmp_B4TY0T
	-quiet
	-print-size
BraseroGenisoimage launching command
BraseroGenisoimage called brasero_job_get_fd_out
BraseroGenisoimage stderr: /usr/bin/genisoimage: No such file or directory. Invalid node - '/media/sda6/Video/Rugby world cup '07/Rugby World Cup 2007 - France vs Argentina (September 7,2007)/Rugby%20World%20Cup%202007%20-%20France%20vs%20Argentina%20(September%207%2C2007)%20%5B%20SDTV%20(XviD)%20Freak%20%5D%202nd%20Half.avi'.
BraseroGenisoimage stdout: HUP
BraseroGenisoimage stderr: HUP
BraseroGenisoimage process finished with status 2
BraseroGenisoimage called brasero_job_error
BraseroGenisoimage finished with an error
BraseroGenisoimage asked to stop because of an error
	error		= 1
	message	= "process BraseroGenisoimage ended with an error code (2)"
BraseroGenisoimage stopping
BraseroGenisoimage got killed
Session error : process BraseroGenisoimage ended with an error code (2) (brasero_burn_record burn.c:2266)
Comment 9 Philippe Rouquier 2007-11-11 19:43:33 UTC
I think I fixed the problem with joliet incompatible files in trunk. Could you try it please?
Comment 10 Ariel 2007-11-12 00:58:19 UTC
Hi Philippe, the error is gone and the image is now generated which is fine.

Howerver there is an issue in the way you are truncating the filenames: you are cutting off the file extensions which renders the file unusable in some cases (my divx player, for instance), and would be unintuitive for newbies. I would suggest the same behaviour as k3b and nero: whenever possible keep the extension, and trim the filename part that is before the last "dot". In most cases (99% I would say) the file extensions are just 3 or 4 chars.

Also: I notice that Brasero does not seem to "remember" the last used setting for "increase win compat.." and for the Burn Speed. It would be great if it did I think.

Thanks and keep it up! :)

Comment 11 Philippe Rouquier 2007-11-14 19:16:24 UTC
That was a good idea. I fixed in trunk the disappearance of extensions now brasero should respect them.
As for the not remembering last option thing, for joliet compat things are a bit different than for other options: if brasero detect joliet incompatible files it turn it off and leaves to user the responsibility to set it back. If no problem is detected then it turn it on by default.
Let me know if I can close this bug and thanks a lot for the heavy testing you've done.
Comment 12 Ariel 2007-11-14 21:09:39 UTC
Awesome. Just tested the new release. works fine!

Looks like finally I'll be able to replace k3b... it took long but it was well worth the wait.

I understand your view on the Joliet-not-always-on issue. I would leave it on by default all the time, I think most people would expect that (that's k3b and nero default behaviour) specially newbies, chances are the burned data will be accessed from non linux machines as well; but wost case the option is visible enough.

Thanks!!!! I'm closing this one.