glunarclock-applet-2 crashed with SIGSEGV in strcmp()

[picgla]

Binary package hint: glunarclock

lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

apt-cache policy glunarclock
glunarclock:
  Installed: 1:0.32.4-11ubuntu2
  Candidate: 1:0.32.4-11ubuntu2
  Version table:
 *** 1:0.32.4-11ubuntu2 0
        500 http://ubuntu.cs.utah.edu karmic/universe Packages
        100 /var/lib/dpkg/status

i expected to be able to use this package. instead, it crashes.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Nov 2 13:10:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-panel/glunarclock-applet-2
Package: glunarclock 1:0.32.4-11ubuntu2
ProcCmdline: /usr/lib/gnome-panel/glunarclock-applet-2 --oaf-activate-iid=OAFIID:GNOME_GLunarclockApplet_Factory --oaf-ior-fd=49
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
SegvAnalysis:
 Segfault happened at: 0xb6f8c9ba <strcmp+10>: cmp (%edx),%al
 PC (0xb6f8c9ba) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: glunarclock
StacktraceTop:
 strcmp () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 panel_applet_marshal_BOOLEAN__STRING ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 bonobo_closure_invoke_va_list ()
Title: glunarclock-applet-2 crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups: adm admin audio cdrom dialout dip fax fuse libvirtd lpadmin netdev plugdev sambashare scanner tape video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #459389, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.