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

[Mike Gerber]

Binary package hint: nautilus-cd-burner

May it helps track down the issue: I used (or better: tried to use) nautilus to burn a CD because Brasero didn't work either. Brasero reported 0 free bytes for each blank (really blank!) CD-R I inserted. So I switched to nautilus for a quick burn, all I got was a crash report.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nautilus-cd-burner
NonfreeKernelModules: nvidia
Package: nautilus-cd-burner 2.24.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/nautilus-cd-burner
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_PAPER=en_GB.UTF-8
Signal: 11
SourcePackage: nautilus-cd-burner
StacktraceTop:
 g_main_context_find_source_by_id ()
 g_source_remove () from /usr/lib/libglib-2.0.so.0
 gdk_window_process_all_updates ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: nautilus-cd-burner crashed with SIGSEGV in g_main_context_find_source_by_id()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mldonkey netdev plugdev powerdev pulse pulse-access pulse-rt scanner src video

[Apport retracing service (apport)]

StacktraceTop:g_main_context_find_source_by_id () from /usr/lib/libglib-2.0.so.0
g_source_remove () from /usr/lib/libglib-2.0.so.0
gdk_window_process_all_updates () from /usr/lib/libgdk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgdk-x11-2.0.so.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 backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) 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.