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 621777 - Crash in brasero_session_span_get_max_space at brasero-session-span.c:100
Crash in brasero_session_span_get_max_space at brasero-session-span.c:100
Status: RESOLVED INCOMPLETE
Product: brasero
Classification: Applications
Component: general
2.28.x
Other Linux
: High critical
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-06-16 12:53 UTC by Linus Hoppe
Modified: 2011-12-22 04:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Linus Hoppe 2010-06-16 12:53:23 UTC 
Reported by apport in https://bugs.launchpad.net/brasero/+bug/595084!

Binary package hint: brasero

Brasero crashed after succesfully burning a cd when trying to close the program.

ProblemType: Crash
Architecture: i386
Date: Sat Jun 12 23:43:42 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: fglrx wl
Package: brasero 2.28.2-0ubuntu1
ProcCmdline: brasero
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-22.60-generic
SegvAnalysis:
 Segfault happened at: 0x656803 <g_type_check_instance_is_a+83>: testb $0x40,0x7(%edi)
 PC (0x00656803) ok
 source "$0x40" ok
 destination "0x7(%edi)" (0x6373654b) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 g_type_check_instance_is_a ()
 brasero_session_span_get_max_space ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: brasero crashed with SIGSEGV in g_type_check_instance_is_a()
Uname: Linux 2.6.31-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
Comment 1 Akhil Laddha 2010-06-16 12:58:36 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Linus Hoppe 2010-06-16 13:34:13 UTC 
I'm sorry, but I can't reproduce the crash. I'll try to obtain a backtrace, but I'm not sure if I can reproduce it.
Comment 3 Linus Hoppe 2010-06-17 11:07:00 UTC 
Lets wait for apport retracer on launchpad to show the backtrace...
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/595084
Comment 4 Linus Hoppe 2010-07-16 15:38:54 UTC 
See https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/595084 for the backtrace of the apport retracer.
Comment 5 Akhil Laddha 2010-07-19 04:52:02 UTC 
Pasting traces from downstream bug

+ Trace 222898

  • #0 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #1 brasero_session_span_get_max_space
    at brasero-session-span.c line 100
  • #2 brasero_project_is_valid
    at brasero-project.c line 954
  • #3 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #8 brasero_session_cfg_update
    at brasero-session-cfg.c line 1302
  • #9 brasero_session_cfg_track_removed
    at brasero-session-cfg.c line 1383
  • #10 brasero_marshal_VOID__OBJECT_UINT
    at libbrasero-marshal.c line 625
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 brasero_burn_session_remove_track
    at brasero-session.c line 410
  • #17 brasero_audio_disc_delete_selected
    at brasero-audio-disc.c line 958
  • #18 brasero_audio_disc_key_released_cb
    at brasero-audio-disc.c line 1877
  • #19 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmarshalers.c line 84
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwidget.c line 4767
  • #25 IA__gtk_window_propagate_key_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwindow.c line 5144
  • #26 gtk_window_key_release_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwindow.c line 5192
  • #27 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmarshalers.c line 84
  • #28 ??
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #33 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwidget.c line 4767
  • #34 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 2391
  • #35 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 1622
  • #36 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkevents-x11.c line 2369
  • #37 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #38 ??
    from /lib/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #40 IA__gtk_main
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 1218
  • #41 brasero_app_run_mainwin
    at brasero-app.c line 1691
  • #42 main
    at main.c line 424 






Comment 6


Luis Medinas





          2010-07-29 22:15:06 UTC
        



Can you reproduce this bug often ? Or you just reproduced once ?






Comment 7


Linus Hoppe





          2010-07-30 09:42:47 UTC
        



I didn't try to reproduce it often. I could reproduce it two times, I did not try more.






Comment 8


Akhil Laddha





          2011-11-08 10:04:21 UTC
        



Can you please check again whether this issue still happens in brasero 3.0.0 or 3.2.0 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.






Comment 9


Akhil Laddha





          2011-12-22 04:39:06 UTC
        



Please feel free to reopen this bug if the problem still occurs with a newer
version of Brasero.