xfburn crashed with SIGSEGV in gtk_selection_data_set_text()

[Martin]

Binary package hint: xfburn

don't know

ProblemType: Crash
Architecture: i386
Date: Thu Mar 25 21:06:44 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/xfburn
Package: xfburn 0.4.3-1
ProcCmdline: xfburn
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0xfe9790: pcmpeqb (%esi),%xmm0
 PC (0x00fe9790) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfburn
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 gtk_selection_data_set_text ()
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: xfburn crashed with SIGSEGV in gtk_selection_data_set_text()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev pulse sambashare vboxusers video

[Apport retracing service (apport)]

StacktraceTop:
 __strlen_sse2 () from /lib/tls/i686/cmov/libc.so.6
 IA__gtk_selection_data_set_text (selection_data=0xbf8b5200,
 cb_browser_drag_data_get (widget=0x8f24260, dc=0x90b99e0,
 _gtk_marshal_VOID__OBJECT_BOXED_UINT_UINT (
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Charlie Kravetz (cjkgeek)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Charlie Kravetz (cjkgeek)]

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!