Bug 616211 – brasero crashed with SIGSEGV in g_main_context_dispatch()

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 616211 - brasero crashed with SIGSEGV in g_main_context_dispatch()


Summary:	brasero crashed with SIGSEGV in g_main_context_dispatch()


Status:	RESOLVED INCOMPLETE

Product:	brasero
Classification:	Applications
Component:	general
Version:	2.30.x
Hardware:	Other Linux

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-04-19 18:59 UTC by Pedro Villavicencio
Modified:	2010-08-26 16:49 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description Pedro Villavicencio 2010-04-19 18:59:38 UTC

this report has been filed here:

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

"While deleting something in the bin brasero crashed"

"#0  brasero_file_monitor_inotify_monitor_cb (channel=<value optimized out>, 
    condition=<value optimized out>, self=0x145a360)
    at brasero-file-monitor.c:327
	list = (GSList *) 0xf121b72
	priv = (BraseroFileMonitorPrivate *) 0x145a3a0
	event = {wd = 5, mask = 2048, cookie = 0, len = 0, 
  name = 0x7fff05f33da0 "ï¿½g"}
	callback_data = (gpointer) 0x18082a0
	err = (GError *) 0x0
	status = <value optimized out>
	name = (gchar *) 0x160fc20 "\020y|\001"
	size = 16

+ Trace 221456

#1 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#2 ??
from /lib/libglib-2.0.so.0
#3 g_main_loop_run
from /lib/libglib-2.0.so.0
#4 brasero_task_start_items
at burn-task.c line 445
#5 brasero_task_start
at burn-task.c line 626
#6 brasero_burn_check_real
at brasero-burn.c line 2290
#7 brasero_burn_record_session
at brasero-burn.c line 2500
#8 brasero_burn_record
at brasero-burn.c line 2801
#9 brasero_burn_dialog_run_real
at brasero-burn-dialog.c line 2156
#10 brasero_burn_dialog_run
at brasero-burn-dialog.c line 2437
#11 brasero_app_burn
at brasero-app.c line 541
#12 brasero_project_burn
at brasero-project.c line 1635
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 gtk_real_button_released
at /build/buildd/gtk+2.0-2.20.0/gtk/gtkbutton.c line 1725
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 ??
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_button_button_release
at /build/buildd/gtk+2.0-2.20.0/gtk/gtkbutton.c line 1617
#23 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.20.0/gtk/gtkmarshalers.c line 84
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 ??
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.20.0/gtk/gtkwidget.c line 4951
#29 IA__gtk_propagate_event
at /build/buildd/gtk+2.0-2.20.0/gtk/gtkmain.c line 2447
#30 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.20.0/gtk/gtkmain.c line 1647
#31 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.20.0/gdk/x11/gdkevents-x11.c line 2372
#32 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#33 ??
from /lib/libglib-2.0.so.0
#34 g_main_loop_run
from /lib/libglib-2.0.so.0
#35 IA__gtk_main
at /build/buildd/gtk+2.0-2.20.0/gtk/gtkmain.c line 1219
#36 brasero_app_run_mainwin
at brasero-app.c line 1848
#37 main
at main.c line 437

Comment 1 Luis Medinas 2010-07-29 22:07:04 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Comment 2 Fabio Durán Verdugo 2010-08-26 16:49:28 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!