wallpaper-tray crashed with SIGSEGV

[Wanted]

Binary package hint: wallpaper-tray

nothing

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Jul 17 17:34:27 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/wallpaper-tray
NonfreeKernelModules: nvidia
Package: wallpaper-tray 0.4.6-5
PackageArchitecture: i386
ProcCmdline: wallpaper-tray
ProcCwd: /media/Vario1/nino/minkiate
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: wallpaper-tray
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
Title: wallpaper-tray crashed with SIGSEGV
Uname: Linux Wanty 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:arena_get2 () from /lib/tls/i686/cmov/libc.so.6
_int_free () from /lib/tls/i686/cmov/libc.so.6
realloc_check () from /lib/tls/i686/cmov/libc.so.6
_nl_cleanup_time () from /lib/tls/i686/cmov/libc.so.6
f_get_dir_entry (sz_dir=0x81e9748 "/media/Vario1/nino/minkiate/Immagini/", p_dir_trgt=0xbfdde188, sz_dir_trgt=0xbfdde184) at wp_tray_util.c:147

[Hew (hew)]

Removed stacktrace containing private info, and reattached with private info removed.

[Hew (hew)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Andrew Starr-Bochicchio (andrewsomething)]

Wallpaper-tray has been completely rewritten in C++ and is now a panel applet. This new version is now in Jaunty (9.04). Can this issue be reproduced with the new version?

[Hew (hew)]

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!