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 600660 - Brasero cannot burn an image on blank DVD
Brasero cannot burn an image on blank DVD
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: libbrasero-burn
3.2.x
Other Linux
: Normal major
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-11-04 10:38 UTC by Dams
Modified: 2018-09-21 16:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
LC_ALL=en_US.UTF-8 brasero -g >brasero-g.log 2>&1 (91.90 KB, text/plain)
2012-06-04 18:56 UTC, Dams
Details
session log of the same brasero invokation. (4.25 KB, text/plain)
2012-06-04 18:57 UTC, Dams
Details

Description Dams 2009-11-04 10:38:34 UTC
I've created a 4.0GiB big ISO file, and attempted to burn it with brasero,
which complained that "Something went wrong" and that "An error occured while
writing to disc". This makes brasero.. useless.

Full description and more information available in Fedora / Red Hat Bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=532896
Comment 1 Luis Medinas 2010-01-14 03:34:06 UTC
I'm getting the impression that is something related with SELinux.
Can you provide a brasero log of the bug ? (brasero -g)
Comment 2 Fabio Durán Verdugo 2010-02-17 18:50:36 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Dams 2010-02-19 11:09:36 UTC
Sorry, I completely had forgotten.
This is not related to SELinux, as we it doesn't work in non-enforced modes. I'll provide the log during the week-end.
Comment 4 André Klapper 2012-02-08 14:09:12 UTC
Hi Dams, 
if you have time, could you please check again whether this issue still happens in Brasero 3.2 or 3.0 and update this report by adding a comment and changing the "Version" field and provide information about your distribution?

Also, could you please provide a debug log? To do this, open a terminal and type the following line to start the Brasero application: "cd ~; brasero -g 2>&1 | tee brasero-debug-log.txt". After reproducing the problem please attach the text file "brasero-debug-log.txt" to this bug report. The file will be in your home directory.
Comment 5 Akhil Laddha 2012-03-23 14:36:00 UTC
Dams, did you get a chance to reproduce the problem with latest Brasero version ?
Comment 6 Dams 2012-06-04 18:55:14 UTC
Yep. Running up-to-date Fedora 16 x86_64.

brasero-libs-3.2.0-1.fc16.x86_64
brasero-3.2.0-1.fc16.x86_64
brasero-nautilus-3.2.0-1.fc16.x86_64
Comment 7 Dams 2012-06-04 18:56:24 UTC
Created attachment 215579 [details]
LC_ALL=en_US.UTF-8 brasero -g >brasero-g.log 2>&1

The brasero -g output.
Comment 8 Dams 2012-06-04 18:57:05 UTC
Created attachment 215580 [details]
session log of the same brasero invokation.
Comment 9 Paul Menzel 2012-10-10 07:58:36 UTC
I am sorry that this bug exists for such a long time. To summarize what is written in the downstream report. This problem is not reproducible with cdrskin, indicating this is a Brasero issue.

It looks like the developers are really busy right now, so until nobody steps up to investigate this by for example adding more debug statements to find out exactly what the error is.
Comment 10 GNOME Infrastructure Team 2018-09-21 16:52:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/77.