Bug 518621 – Brasero crash during ISO burn - burn OK

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 518621 - Brasero crash during ISO burn - burn OK


Summary:	Brasero crash during ISO burn - burn OK


Status:	RESOLVED INCOMPLETE

Product:	brasero
Classification:	Applications
Component:	general
Version:	0.7.1
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	0.7
Assigned To:	Brasero maintainer(s)
QA Contact:	Brasero maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-25 14:22 UTC by Pedro Villavicencio
Modified:	2008-07-08 02:11 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Pedro Villavicencio 2008-02-25 14:22:04 UTC

This bug has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/brasero/+bug/184231

"I was burning a DVD iso image using the default settings. The burning went well and, in the end, Brasero came up with this error. I've burned a few images in the last 2 days and this is the first time this happens."

".

+ Trace 190400

Thread 1 (process 26069)

#0 brasero_project_type_chooser_recent_changed_cb
at brasero-project-type-chooser.c line 321
#1 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.15.3/gobject/gmarshal.c line 75
#2 IA__g_closure_invoke
at /build/buildd/glib2.0-2.15.3/gobject/gclosure.c line 490
#3 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.15.3/gobject/gsignal.c line 2285
#4 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.15.3/gobject/gsignal.c line 2187
#5 IA__g_signal_emitv
at /build/buildd/glib2.0-2.15.3/gobject/gsignal.c line 245
#6 IA__gtk_recent_info_unref
at /build/buildd/gtk+2.0-2.12.5/gtk/gtkrecentmanager.c line 1499
#7 gtk_recent_manager_init
at /build/buildd/gtk+2.0-2.12.5/gtk/gtkrecentmanager.c line 333
#8 gtk_recent_manager_set_property
at /build/buildd/gtk+2.0-2.12.5/gtk/gtkrecentmanager.c line 552
#9 g_timeout_dispatch
at /build/buildd/glib2.0-2.15.3/glib/gmain.c line 3502
#10 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.15.3/glib/gmain.c line 2071
#11 g_main_context_iterate
at /build/buildd/glib2.0-2.15.3/glib/gmain.c line 3003
#12 IA__g_main_loop_run
at /build/buildd/glib2.0-2.15.3/glib/gmain.c line 2907
#13 IA__gtk_main
at /build/buildd/gtk+2.0-2.12.5/gtk/gtkmain.c line 1136
#14 main
at main.c line 735

Comment 1 Philippe Rouquier 2008-06-13 07:04:05 UTC

I have honestly no idea how this bug is triggered. =(

Comment 2 Luis Medinas 2008-07-08 02:11:03 UTC

Marking as incomplete i have no idea too what to do. Ubuntu now ships 0.7.91 on intrepid maybe it should be pushed to hardy as a backport or something.
Thanks