Clock applet crashes upun confirming latitude/longitude (entered with 4 decimals)

StacktraceTop:create_cities_section (cd=0x8432b38) at clock.c:1142
cities_changed (client=0x80f2b68, cnxn_id=1711276105, entry=0x8223338, cd=0x8432b38)
notify_listeners_callback (listeners=0x80f67a8,
gconf_listeners_notify (listeners=0x80f67a8,
notify_one_entry (client=0x80f2b68, entry=0x8223338) at gconf-client.c:2409

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=525754

Could you describe steps to trigger the bug? What values did you use in this dialog?

Sebastien,

In the clock preferences, I first added a location (Gent, in timezone Europe/Brussels).
Later, I reentered the clock preferences and edited the location entry (labeled Gent) my (almost) exact coordinates: 51.0854 North, 3.7175 East.
I could exit the edit-location pane, but when exiting (OK-ing) the changed preferences, the panel did not disappear. It stayed on the desktop.
As I installed Hardy on a rather "slow" machine by todays' standards (dual PII 333MHz), I just continued browsing until, after a minute or so, the top panel
(gnome-panel, I presume) suddenly disappeared and quicky reappeared - with apport notifying me of the crash that had happened.
After the crash-bug-submit, I returned to the clock preferences, only to find an empty list of locations. I immediately tried to reproduce the crash by recreating a location Gent, timezone Europe/Brussels. Closed everything and reentered the preferences, this time to find 2 location entries labeled Gent (!). I removed the second one and went on to edit the first (adding my longitude/latitude). This time around, no crash occurred.

I'm reinstalling Hardy on the machine as I write this (my /var separate partition being way too small and thus not coping too well with the hundreds of updates every week), and I will try to reproduce the problem afterwards - anything I should be on the lookout for?

BTW: thx for the support.

Sebastien,

I reconfigured my location yesterday evening (after installing and updating - took a wee bit of time on this machine), but nothing spectacular happenend. However, after booting the machine and logging in this evening, I found my location I entered to be gone. So, I re-add it (first, without longitude/latitude), but when confirming the new location and returning to the location tab of the clock prefs, I now find two (2) entries!
My, my, my. I'd think there's something fishy going on with the storage/database of locations (maybe due to my somewhat cramped config - 512 MiB)...

Good luck! Let me know if there's anything more I can do for you - I'm pretty sure I can reproduce the "missing/invisible" location at will...

This bug was fixed in the package gnome-panel - 1:2.22.1-0ubuntu1

---------------
gnome-panel (1:2.22.1-0ubuntu1) hardy; urgency=low

  * New upstream version:
    Panel
    - Convert username/login to UTF-8 in logout dialog
    - Fix applet processes not quitting when the applet is removed (lp: #195915)
    Misc
    - Remove old and useless files
    - Require gweather 2.22.1
    - Don't explicitly require libxml for the weather applet anymore
    Clock Applet
    - Fix crash when there are no locations available
    - Fix locations not appearing in the preferences dialog
    - Make find location window larger
    - Handle escape to close the dialog in the time/timezone dialogs
    - Fix various issues with adding/removing locations
    - Fix crash when PolicyKit helper can't be called (lp: #208791)
    - Fix crash when closing the calendar popup when a city is blinking
      on the map (lp: #200881, ##207954)
    - Improve the blinking on the map when clicking on various locations
    - Cleanups
    - Correctly redraw the map outline on expose events
    - Fix crash when the location doesn't have coordinates (lp: #201102)
    - Fix crash when updating locations while calendar popup is not shown
      (lp: #210470)
    - Fix initial visibility of the appointments to actually follow the
      state of the expander (lp: #206118)
    - Make sure we always use data from the right country (lp: #185190)
    - Show caldav appointments in the calendar
    - Ignore dbus errors when setting the time and there's no reply on the bus
      (lp: #207890)
    - Open evolution on the right day, in all timezones (lp: #66028)
    - Fix crash when an evolution-data-server dies (lp: #122590)
    - Correctly set time, even when DST is on (lp: #208598)
    - Handle multiple locations in the same timezone in a better way
    - Fix weather tooltip to show the real temperature and the apparent
      temperature, instead of only the apparent one (lp: #188183)
    - Do not lose the weather location information when changing the
      timezone of a location (lp: #200911)
    - Don't show weather information of the last location once it has been
      removed
    - Remove empty space on the left of the clock when there's no location
      (lp: #203691)
    - Potential fix for another crash in the calendar code
    - When adding a location, make it the current one if it makes sense
  * debian/control.in:
    - updated libgweather requirement
  * debian/patches/17_expose_wm_keybindings.patch:
    - dropped, the current version has some issues and need to be rework
      during next cycle (lp: #211112)
  * debian/patches/80_from_bugzilla_use_correct_current_timezone.patch:
    - dropped, fixed in the new version

 -- Sebastien Bacher <email address hidden> Tue, 08 Apr 2008 01:47:12 +0200

Came with the updates tonight (08 april 2008), and indeed seems to solve the problem. I removed, recreated, edited,... my location and latitude/longitude, but could not force a crash. Congrats and thanks.

(Sebastien, you may mark this problem as solved - I do not seem to be authorized to do this)