rarian-sk-get-cl assert failure: *** glibc detected *** /usr/bin/rarian-sk-get-cl: malloc(): memory corruption (fast): 0x08db6ae0 ***

[Aggelos Karasarinis]

don't know something about the crash/bug

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: rarian-compat 0.8.1-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/rarian-sk-get-cl: malloc(): memory corruption (fast): 0x08db6ae0 ***
Date: Thu Apr 15 22:51:46 2010
ExecutablePath: /usr/bin/rarian-sk-get-cl
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/bin/rarian-sk-get-cl el scrollkeeper_cl.xml
ProcEnviron:
 LANGUAGE=el_GR:el:en_GB:en
 LANG=el_GR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: rarian
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: rarian-sk-get-cl assert failure: *** glibc detected *** /usr/bin/rarian-sk-get-cl: malloc(): memory corruption (fast): 0x08db6ae0 ***
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 __libc_message (do_abort=2,
 malloc_printerr (action=<value optimized out>,

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.