| View previous topic :: View next topic |
| Author |
Message |
papandreoos
Apprentice
Joined: 17 Dec 2014
Posts: 163
|
 Posted: Sun May 15, 2016 9:48 am Post subject: can't burn in brasero or with xfburn (iso9660 third version) |
 |
|
i have files i want to burn to a DVD+R as a data DVD.
when i insert the files to brasero, i get a popup windows that tell me that:
Do you really want to add "MY FILES" to the selection and use the third version of the ISO9660 standard to support it?
then it explain further and in the end i can "always add such file", or "never add such file".
i click to add always and then i get a message in main window of brasero:
please replace the disc with a supported cd or dvd.
and i can't burn.
the burn button is not clickable
the version of brasero is: 3.12.1
i also can't burn as root(same broblem).
my user is in 'optical' and 'cdrom', groups
if i start my machine on archlinux(same machine, dual boot) i can burn those same files, that i can't in gentoo.
and the verison of brasero is the same in gentoo and arch.
in arch i also get the message:
Do you really want to add "MY FILES" to the selection and use the third version of the ISO9660 standard to support it?
and after i press always add such file, it don't give me the "error" message: "please replace the disc with a supported cd or dvd."
and i can press burn and burn...
i enabled all the kernel options as they detailed here:
https://wiki.gentoo.org/wiki/CDROM#Kernel
they all compiled into the kernel(no M . just *).
i also installed udftools and cdrtools (and also dvd+rw-tools)
i also tried a different DVD disc but i got the same error message.
here is the output of: "brasero -g --brasero-media-debug" till i get the "please replace the disc with a supported cd or dvd:
http://pastebin.com/e7VaHdXZ
p.s.
the problem is just with the third version of iso9660.
if i add smaller size files, i can burn the disk in gentoo without a problem (and of course i don't get into the popup window that ask me if i want to burn it with the third version of iso9660). |
|
| Back to top |
|
 |
scdbackup
n00b
Joined: 19 Oct 2014
Posts: 23
Location: Germany
|
| Posted: Mon May 16, 2016 7:54 am Post subject: |
|
|
Hi,
i'm the developer of libburn and libisofs which work at least under
Xfburn and in this case under Brasero, too.
First question: Is your file small enough to fit into the 4482 MB
of a DVD+R medium ?
-----------------------------------------------------------------------
In the Brasero log, the drive /dev/sr0 is found.
I suspect these lines to be the immediate reason for refusal
| Code: |
BraseroBurn: (at burn-basics.c:203) Created 0 links pointing to Data ISO Level 3 JOLIET DEEP
...
BraseroBurn: (at brasero-caps-session.c:567) Found link (with 0 links): Data ISO Level 3 JOLIET DEEP
|
(whatever "link with links" shall mean, "0" is a low number.)
If the problem is with the "third version" of ISO 9660 (actually "Level 3",
which allows files of more than 4 GB), then it can hardly be about
recognition of burner or inserted medium.
The suspicious messages are about Brasero entrails, not libburn or
libisofs. libburn is supposed to operate DVD+R media, libisofs
offers the capability for large files.
It would not be the first time that Brasero's plugin glue code
does not use the libraries properly.
Does the Brasero log on Archlinux talk about "mkisofs" or "genisoimage" ?
This would possibly indicate the difference which distinguishes both
Braseros.
-----------------------------------------------------------------------
What error indications do you get from Xfburn ?
I just tried with Xfburn 0.5.2 on Debian 8. It burns an 8 GB file in an
ISO 9660 filesystem onto BD-RE.
(Xfburn traditionally crashes deep inside GTK if i do not use the file
browser from menue "View" but rather click the "+" button directly.
The author of Xfburn answers to my mails but cannot help against buggy
GTK. I myself mostly burn by command line programs xorriso.)
-----------------------------------------------------------------------
How inconvenient would it be to try this xorriso run:
| Code: |
xorriso -for_backup -outdev /dev/sr0 -map "MY FILES" /MY_FILES
|
More commands
| Code: | | -map disk_path iso_path |
could be added if more files or directories shall be put into the resulting ISO.
Have a nice day 
Thomas
[/quote] |
|
| Back to top |
|
|
papandreoos
Apprentice
Joined: 17 Dec 2014
Posts: 163
|
| Posted: Mon May 16, 2016 9:26 pm Post subject: |
|
|
| Quote: | First question: Is your file small enough to fit into the 4482 MB
of a DVD+R medium ? |
i think so.
i succeeded burning the same files on windows 7 with imgburn (it used UDF to do it).
i also succeeded burning those files in archlinux with brasero.
and i also did it in xfburn(also in archlinux).
in gentoo, when i insert my files into xfburn, it give me a warning message that says:
"my file" is larger then what iso9660 level 2 allows. This can be a problem for old systems or software.
i close this message and then i press "proceed to burn".
in the burn composition i changed the burn speed to 4 and used the "dummy write".
then i press burn composition and after a couple of seconds(maybe 3) of initializing... i get Failure in red color.
| Quote: | | Does the Brasero log on Archlinux talk about "mkisofs" or "genisoimage" ? |
YES!
about mkisofs it give those lines :
about genisoimage there are a lot of braserogenisoimage in the log(a lot!)
here are some useful lines(i hope) that have genisoimage and braserogenisoimage in them:
| Quote: |
BraseroBurn: (at burn-plugin.c:335) Plugin genisoimage is active
BraseroBurn: (at burn-plugin-manager.c:203) Plugin set to active. genisoimage is active
BraseroBurn: (at brasero-caps-burn.c:418) Trying genisoimage with a priority of 1
BraseroBurn: (at brasero-caps-burn.c:469) Trying genisoimage with a priority of 1
BraseroBurn: (at brasero-caps-burn.c:806) genisoimage added to task
BraseroBurn: (at burn-task.c:336) ::activate method BraseroGenisoimage
BraseroBurn: (at burn-job.c:352) no ::activate method BraseroGenisoimage
BraseroBurn: (at burn-task.c:293) ::start method BraseroGenisoimage
BraseroBurn: (at burn-job.c:1430) BraseroGenisoimage called brasero_job_get_action
BraseroBurn: (at burn-process.c:129) BraseroGenisoimage getting varg
BraseroBurn: (at burn-job.c:1430) BraseroGenisoimage called brasero_job_get_action
BraseroBurn: (at burn-job.c:1267) BraseroGenisoimage called brasero_job_get_current_track
BraseroBurn: (at burn-job.c:1735) BraseroGenisoimage called brasero_job_get_tmp_dir
BraseroBurn: (at burn-job.c:1769) BraseroGenisoimage called brasero_job_get_data_label
BraseroBurn: (at burn-job.c:1374) BraseroGenisoimage called brasero_job_get_flags
BraseroBurn: (at burn-job.c:1430) BraseroGenisoimage called brasero_job_get_action
BraseroBurn: (at burn-job.c:1858) BraseroGenisoimage called brasero_job_set_current_action
BraseroBurn: (at burn-process.c:142) BraseroGenisoimage got varg:
BraseroBurn: (at burn-process.c:146) /usr/bin/genisoimage
BraseroBurn: (at burn-process.c:624) BraseroGenisoimage Launching command
BraseroBurn: (at burn-process.c:450) BraseroGenisoimage stderr: HUP
BraseroBurn: (at burn-process.c:417) BraseroGenisoimage stdout: 2273970
BraseroBurn: (at burn-job.c:1430) BraseroGenisoimage called brasero_job_get_action
BraseroBurn: (at burn-job.c:1922) BraseroGenisoimage called brasero_job_set_output_size_for_current_track
BraseroBurn: (at burn-process.c:450) BraseroGenisoimage stdout: HUP
BraseroBurn: (at burn-process.c:301) BraseroGenisoimage process finished with status 0
BraseroBurn: (at burn-job.c:1071) BraseroGenisoimage Finished track successfully
BraseroBurn: (at burn-job.c:1281) BraseroGenisoimage called brasero_job_get_done_tracks
BraseroBurn: (at burn-job.c:1309) BraseroGenisoimage called brasero_job_get_fd_out
BraseroBurn: (at burn-job.c:1430) BraseroGenisoimage called brasero_job_get_action
|
etc'
| Quote: | How inconvenient would it be to try this xorriso run:
Code:
xorriso -for_backup -outdev /dev/sr0 -map "MY FILES" /MY_FILES
More commands
Code:
-map disk_path iso_path
could be added if more files or directories shall be put into the resulting ISO. |
i dont understand your example.
let's say i have 3 files in a folder that is called 'PAPA'.
how do i burn the content of the folder to my DVD?
and how do i burn the folder itself(and also the content of course), to DVD?
thank you! |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Mon May 16, 2016 9:48 pm Post subject: |
|
|
Imgburn works fine with wine-1.6.2 and wine-1.8.2
That's what I use. I gave up on brasero and k3b |
|
| Back to top |
|
|
scdbackup
n00b
Joined: 19 Oct 2014
Posts: 23
Location: Germany
|
| Posted: Tue May 17, 2016 6:07 am Post subject: |
|
|
Hi,
genisoimage said "2273970" which is slightly lower than the number
of 2295104 data blocks of a DVD+R.
2273970 blocks would be a bit less than 4442 MB.
I doubt that libisofs would add 40 MB more of meta data unless
you have a hundred thousand files in the ISO.
So the problem is probably in Brasero's libisofs plugin.
(Grrrr. No maintainer or developer to see anywhere.)
I guess you can set the Gentoo Brasero to use mkisofs or genisoimage.
(Grrrr again.)
-----------------------------------------------------------------
| Quote: | let's say i have 3 files in a folder that is called 'PAPA'.
how do i burn the content of the folder to my DVD? |
If the three files are the only ones in "PAPA", then you may use
xorriso command -map to put the whole directory into the ISO:
| Code: |
xorriso -for_backup -outdev /dev/sr0 -map PAPA /PAPA
|
The first parameter of -map (here "PAPA") is the path of the directory
in your local filesystem (hard disk, network, anything that's mounted).
The second parameter (here "/PAPA") is the path in the ISO by which the
directory or file shall be accessible in the ISO.
So above example copies disk directory "PAPA" and all files and directories
underneath to directory "/PAPA" in the ISO. Sub directories and files will
get the same names as they have on disk in "PAPA".
The command -for_backup adds MD5 sums to the ISO. Three for superblock,
directory tree, and whole ISO. Further each data file gets its own MD5.
These checksums enable you to verify data health at any time later:
| Code: |
xorriso -for_backup -indev /dev/sr0 -check_media --
|
If superblock and directory tree are ok, then you can find files which
got hit by bad spots:
| Code: |
xorriso -for_backup -indev /dev/sr0 -check_md5_r sorry / --
|
If your input files are not neatly concentrated under one directory,
then you can add more directories or pick single files. You may also
use xorriso command -rm to remove files which you previously added:
In this example i separate the xorriso commands by line breaks which i
hide from the shell by trailing "\" characters:
| Code: |
xorriso -for_backup \
-outdev /dev/sr0 \
-map PAPA /PAPA \
-rm /PAPA/drunk.jpg -- \
-map /usr/home/MAMA/hug.jpg /MAMA/hug.jpg
|
(Note that command -rm needs "--" as end marker of its variable length
ISO file path list. Command -map on the other hand gets always two
parameters: disk_path and iso_path. Thus it needs no "--" at its end.)
One may interactively explore xorriso by its Tcl-Tk frontend:
http://libburnia-project.org/browser/libisoburn/trunk/frontend/xorriso-tcltk
It is part of the libisoburn tarball but does not get installed by
default.
Have a nice day
Thomas |
|
| Back to top |
|
|
scdbackup
n00b
Joined: 19 Oct 2014
Posts: 23
Location: Germany
|
| Posted: Tue May 17, 2016 8:09 am Post subject: |
|
|
Hi,
new observation in Brasero log:
| Code: |
BraseroBurn: (at brasero-caps-session.c:1075) and input is Data ISO UDF Level 3 JOLIET
|
libisofs does not produce UDF.
Did you enable it explicitely ?
Can you disable it in Brasero after your file composition is complete ?
----------------------------------------------------------------------------
Level 3 might not be the cause of the problem. But Brasero could enable
UDF by default if the need for Level 3 is detected.
I am now looking at
https://github.com/GNOME/brasero/blob/master/plugins/libburnia/burn-libisofs.c
It seems that ISO 9660 Level 3 is expected and supposed to be handled
by a call to libisofs API function iso_write_opts_set_iso_level().
I did not yet find an explanation of Brasero's concept of capabilities
or related "links".
I do see in function brasero_libisofs_export_caps() that level 3 is
announced in some way (line 1110):
| Code: |
input = brasero_caps_data_new (BRASERO_IMAGE_FS_ISO|
BRASERO_IMAGE_ISO_FS_DEEP_DIRECTORY|
BRASERO_IMAGE_ISO_FS_LEVEL_3|
BRASERO_IMAGE_FS_JOLIET);
brasero_plugin_link_caps (plugin, output, input);
g_slist_free (input);
input = brasero_caps_data_new (BRASERO_IMAGE_FS_ISO|
BRASERO_IMAGE_ISO_FS_DEEP_DIRECTORY|
BRASERO_IMAGE_ISO_FS_LEVEL_3|
BRASERO_IMAGE_FS_SYMLINK);
brasero_plugin_link_caps (plugin, output, input);
g_slist_free (input);
|
which might correspond to the messages:
| Code: |
BraseroBurn: (at brasero-caps-session.c:567) Found link (with 0 links): Data ISO Level 3 JOLIET DEEP
BraseroBurn: (at brasero-caps-session.c:567) Found link (with 0 links): Data ISO SYMLINK Level 3 DEEP
|
As one can see, no UDF is offered by the plugin.
Have a nice day
Thomas |
|
| Back to top |
|
|
scdbackup
n00b
Joined: 19 Oct 2014
Posts: 23
Location: Germany
|
| Posted: Tue May 17, 2016 9:32 am Post subject: |
|
|
Hi,
i believe to have found the code piece of Brasero where it decides
to demand UDF because of file size:
https://github.com/GNOME/brasero/blob/master/libbrasero-burn/brasero-data-project.c
| Code: |
if (node->is_2GiB) {
data->fs_type |= BRASERO_IMAGE_ISO_FS_LEVEL_3;
if (!(data->fs_type & BRASERO_IMAGE_FS_SYMLINK))
data->fs_type |= BRASERO_IMAGE_FS_UDF;
}
|
This is of course a breach of plugin encapsulation because the generic
code implicitely presumes that all ISO 9660 plugins offer .fs_type
BRASERO_IMAGE_FS_UDF.
Further there is no reason in the specs of ISO 9660 (aka ECMA-119)
why the presence of a large file would demand the presence of an
UDF filesystem in addition to the ISO 9660.
(Maybe Brasero even misunderstands the reason and real size of the
limitations of ISO 9660 Levels below 3:
A single data extend can hold 4 GiB minus 1 byte. Larger files need
more than one extent. That's known as Level 3.
The 2 GiB - 1 limit is about fseek(3) on systems which have data type
"long" as signed 32 bit integer.
ISO 9660 counts bytes and blocks by unsigned 32 bit.)
My proposal to a Brasero maintainer/developer would be to remove the
two lines
| Code: |
if (!(data->fs_type & BRASERO_IMAGE_FS_SYMLINK))
data->fs_type |= BRASERO_IMAGE_FS_UDF;
|
from source file libbrasero-burn/brasero-data-project.c.
But i do not know of any who would feel in charge.
Maybe one can ask the Gentoo maintainers of Brasero to add a patch
which does this before Brasero gets built.
Have a nice day
Thomas |
|
| Back to top |
|
|
papandreoos
Apprentice
Joined: 17 Dec 2014
Posts: 163
|
| Posted: Wed May 18, 2016 10:15 pm Post subject: |
|
|
| Tony0945 wrote: | Imgburn works fine with wine-1.6.2 and wine-1.8.2
That's what I use. I gave up on brasero and k3b |
thanks for your suggestion.
i'll also try that . |
|
| Back to top |
|
|
papandreoos
Apprentice
Joined: 17 Dec 2014
Posts: 163
|
| Posted: Wed May 18, 2016 10:22 pm Post subject: |
|
|
scdbackup:
sorry for answering late.
thanks you very much for your thorough information and your explanation of how to burn in xorriso.
i hope to try that sometime
gladly i don't burn a lot of DVD's so the "problem" with brasero is not critical . |
|
| Back to top |
|
|
|
Other Things Gentoo
