nautilus-cd-burner crashed with SIGSEGV in g_source_attach()

[Stéphane Marguet]

Binary package hint: nautilus-cd-burner

Trying to burn an iso file

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nautilus-cd-burner
Package: nautilus-cd-burner 2.23.90-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/nautilus-cd-burner --source-iso=/home/username/livecd/ubuntu-8.04.1-desktop-i386-custom.iso
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus-cd-burner
StacktraceTop:
 g_source_attach () from /usr/lib/libglib-2.0.so.0
 g_idle_add_full () from /usr/lib/libglib-2.0.so.0
 gdk_threads_add_idle_full ()
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 gdk_window_invalidate_maybe_recurse ()
Title: nautilus-cd-burner crashed with SIGSEGV in g_source_attach()
Uname: Linux 2.6.27-3-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner src tape users video

[Apport retracing service (apport)]

StacktraceTop:IA__g_idle_add_full (priority=120, function=0xb7b055d0 <gdk_threads_dispatch>, data=0x91c2040,
IA__gdk_threads_add_idle_full (priority=120, function=0xb7b221d0 <gdk_window_update_idle>, data=0x0, notify=0)
gdk_window_schedule_update (window=<value optimized out>) at /build/buildd/gtk+2.0-2.14.1/gdk/gdkwindow.c:2533
IA__gdk_window_invalidate_maybe_recurse (window=0x9286308, region=0x93a5ba0, child_func=0, user_data=0x0)
IA__gdk_window_invalidate_region (window=0x9286308, region=0x93a5ba0, invalidate_children=0)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.