brasero crashed with SIGSEGV

[Nic]

Binary package hint: brasero

Brasero crashed while buring a video DVD

ProblemType: Crash
Architecture: i386
Date: Fri Jan 18 15:38:14 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 0.7.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: brasero
ProcCwd: /home/nt271
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 11
SourcePackage: brasero
Stacktrace:
 #0 0xb729c0f3 in ?? () from /usr/lib/libglib-2.0.so.0
 #1 0x00000002 in ?? ()
 #2 0x08143d58 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: brasero crashed with SIGSEGV
Uname: Linux constantines 2.6.24-4-generic #1 SMP Mon Jan 14 17:30:39 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner video

[Apport retracing service (apport)]

StacktraceTop:g_build_path_va (separator=0x80dd83d "/", first_element=0x2f6e6f69 <Address 0x2f6e6f69 out of bounds>,
IA__g_build_path (separator=0x80dd83d "/", first_element=0x2f6e6f69 <Address 0x2f6e6f69 out of bounds>)
brasero_data_disc_inotify_monitor_cb (channel=0x82dccf8, condition=G_IO_IN, disc=0x82d1550)
g_io_unix_dispatch (source=0x8266200, callback=0x8089600 <brasero_data_disc_inotify_monitor_cb>,
IA__g_main_context_dispatch (context=0x81155a0) at /build/buildd/glib2.0-2.15.3/glib/gmain.c:2071

[Pedro Villavicencio (pedro)]

known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=524375
also a comment from upstream:

"Can you please explain the steps to crash brasero ? And please try brasero
0.7.1 maybe this bug is already fixed"

can you test the same with 0.7.1 and confirm that's fixed there? thanks.

[Pedro Villavicencio (pedro)]

ping? any response on this? upstream bug was closed because the lack of information, if there's no response here in a few weeks i'm going to close this too, thanks.

[Sebastien Bacher (seb128)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!