libbrasero-burn/brasero-data-project.c | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 fixed segfault when renaming or removing folder in project.
  When adding folder from filesystem to project and creating new folder in this folder, removing or renaming causes segfault.
  This happens because new folder must have flag 'is_grafted' (project node not from real file or folder), but code in brasero-data-project.c in function brasero_data_project_add_node_real doesn't handle nodes with flag 'is_fake' correctly (new empty folder has this flag). Node isn't marked as grafted with function brasero_file_node_graft. I've just added call of this function.

plugins/libburnia/burn-libisofs.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 [patch] libburnia plugin: fix while loop in `brasero_libisofs_write_image_to_fd_thread()` (#685983)

In commit 1b8397ee [1] a bug was introduced by forgetting to
substitude a command with a newly introduced variable in the loop
condition. This broke the loop reading out the data to be written to the
disc.

This small error had a huge impacted as writing images on the fly always
failed, because only half of the image was written to the disc. Several
bug reports exist for this problem and are most likely due to this
problem [3][4][5].

Substituting this command with the variable fixes the problem reported
in GNOME Bugzilla bug 685983 [6].

[1] http://git.gnome.org/browse/brasero/commit/?id=1b8397ee252df2d554682ca2d694d5937fbf6e39
[2] https://bugzilla.gnome.org/show_bug.cgi?id=630651
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688229
[4] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594753
[5] https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
[6] https://bugzilla.gnome.org/show_bug.cgi?id=685983

plugins/audio2cue/burn-audio2cue.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 avoid generating invalid frame number 75
 The conditional increment to the frame number, which is probably meant to
 avoid loosing the last incomplete frame in the very last track of a disk, has
 the side effect of generating frame numbers equal to 75, when they should be
 between 0 and 74 included, which results in an unburnable image.
 .
 While the code could be adapted to count the last frame, it is clearer and
 less intrusive to the original code to simply remove the conditional increment,
 and possibily loosing 1/75th a second on the very last track should not matter
 to anyone.

libbrasero-burn/burn-plugin.c | 2 1 + 1 - 0 !
src/brasero-drive-settings.c | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 2 deletions(-)

 [patch] put settings in the correct path

https://bugzilla.gnome.org/show_bug.cgi?id=674169