Brasero crashes when making a video DVD

Bug #612251 reported by O. Emmerson
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: brasero

I open Brasero, click the 'Video Project' option.
Drag two .mp4 videos into the project.
The files load fine and preview picture shows up. I click the 'Burn...' button. I click the 'Burn' option again when the properties box has popped up.

The app immediately crashes (it doesn't even start to convert the video to DVD format) with the error message on the cmd ' **ERROR: [brasero] Horizontal size is greater than permitted in specified Level'

I have installed all the recommended dependencies for Brasero but the problem still occurs.

p.s. I have turned apport on in /var/apport and restarted but it still does not start automatically when the app crashes.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: brasero 2.30.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Sun Aug 1 13:29:13 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: brasero

Revision history for this message
O. Emmerson (oemmerson) wrote :
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in brasero (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
Lorenzo (nakis)
Changed in brasero (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Rodrigo Guariento (rodrigoguariento) wrote :
Download full text (7.5 KiB)

The same occurs with me, but there is no apport files into /var/crash, even with the crash interception component enabled:

---
rodrigo@rf511:~$ brasero

(brasero:2760): GLib-CRITICAL **: 09:05:31.742: g_key_file_load_from_file: assertion 'file != NULL' failed

** (brasero:2760): WARNING **: 09:05:31.742: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology”

(brasero:2760): Gtk-WARNING **: 09:05:46.799: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
Xlib: extension "NV-GLX" missing on display ":0".

(brasero:2760): Gtk-WARNING **: 09:05:46.951: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &

(brasero:2760): Gtk-WARNING **: 09:05:46.951: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &

(brasero:2760): Gtk-WARNING **: 09:05:47.100: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &

(brasero:2760): Gtk-WARNING **: 09:05:47.103: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &

(brasero:2760): Gtk-WARNING **: 09:05:47.103: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
Xlib: extension "NV-GLX" missing on display ":0".

** (brasero:2760): CRITICAL **: 09:05:47.420: brasero_track_type_equal: assertion 'type_B != NULL' failed

(brasero:2760): Gtk-WARNING **: 09:05:48.263: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &

(brasero:2760): Gtk-WARNING **: 09:05:48.264: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &

(brasero:2760): Gtk-WARNING **: 09:05:48.309: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &

(brasero:2760): Gtk-WARNING **: 09:05:48.310: Failed to set text from markup due to error parsing markup: Error on line 1: Entity ...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.