xarchiver crashed with SIGSEGV in g_closure_invoke()

[trastosp]

Binary package hint: xarchiver

uncompress rar archive

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: xarchiver 1:0.5.2+20090319+dfsg-4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic-pae 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 11 15:29:32 2010
ExecutablePath: /usr/bin/xarchiver
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcCmdline: xarchiver
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6f6a790: pcmpeqb (%esi),%xmm0
 PC (0xb6f6a790) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xarchiver
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: xarchiver crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 __strlen_sse2 () from /lib/tls/i686/cmov/libc.so.6
 xa_remove_level_from_path (path=0x0) at string_utils.c:151
 drag_data_get (widget=0x8c64078, dc=0x8ca4d70,
 _gtk_marshal_VOID__OBJECT_BOXED_UINT_UINT (
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

This bug has been reported to the developers of the software. You can track it and make comments at: https://sourceforge.net/tracker/?func=detail&aid=3158914&group_id=140153&atid=745600

 Thanks for taking the time to make Ubuntu better!

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version.