After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 525754 - Clock applet crashes upun confirming latitude/longitude (entered with 4 decimals)
Clock applet crashes upun confirming latitude/longitude (entered with 4 decim...
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: clock
2.22.x
Other Linux
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 528107 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-02 13:11 UTC by Sebastien Bacher
Modified: 2008-04-15 06:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Sebastien Bacher 2008-04-02 13:11:22 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/210470

"Binary package hint: gnome-panel

After entering latitude/longitude with 4 digits after the decimal point - don't know if this is important - for Gent, Belgium in timezone Europe/Brussels and then clicking OK, the applet froze (and after a few minutes gnome-panel restarted)

+ Trace 194002

  • #0 IA__g_type_check_instance_cast
    at /build/buildd/glib2.0-2.16.1/gobject/gtype.c line 3177
  • #1 create_cities_section
    at clock.c line 1142
  • #2 cities_changed
    at clock.c line 2214
  • #3 notify_listeners_callback
    at gconf-client.c line 2384
  • #4 gconf_listeners_notify
    at gconf-listeners.c line 589
  • #5 notify_one_entry
    at gconf-client.c line 2409
  • #6 notify_idle_callback
    at gconf-client.c line 2449
  • #7 g_idle_dispatch
    at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 4081
  • #8 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2003
  • #9 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2636 






Comment 1


Vincent Untz





          2008-04-03 18:13:37 UTC
        



More details from launchpad:



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.







Comment 2


Vincent Untz





          2008-04-03 19:41:15 UTC
        



This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.







Comment 3


Philip Withnall





          2008-04-15 06:20:28 UTC
        



*** Bug 528107 has been marked as a duplicate of this bug. ***