clock-applet crashed with SIGSEGV in g_main_context_dispatch()

[tim leavy]

Binary package hint: gnome-panel

When applying the second city to my new list (i added london, then sydney) the aplet crashed.

running 10.04 beta 2

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-panel 1:2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: wl fglrx
Architecture: amd64
Date: Mon Apr 19 09:46:11 2010
ExecutablePath: /usr/lib/gnome-panel/clock-applet
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcCmdline: /usr/lib/gnome-panel/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=30
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9eb87e2751: cmpq $0x0,(%rax)
 PC (0x7f9eb87e2751) ok
 source "$0x0" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 g_main_context_dispatch ()
Title: clock-applet crashed with SIGSEGV in g_main_context_dispatch()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1454): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:6144): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[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 #527951, 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.