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 522438 - gnome-panel crashes when selecting location without coordinates
gnome-panel crashes when selecting location without coordinates
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: clock
2.22.x
Other Linux
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 521155 522742 523270 524645 524877 524970 525025 525826 529993 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-03-14 15:34 UTC by Pedro Villavicencio
Modified: 2008-04-25 22:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Pedro Villavicencio 2008-03-14 15:34:12 UTC 
This bug has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gnome-panel/+bug/201102

"Click on the date/time on the deskbar to show the calendar. Click on 'Locations', 'Add', 'Find' and choose Bristol (Europe > UK). Click 'OK' and the deskbar disappears. On Hardy up to about Alpha 3 the deskbar disappeared for good. More recently, the deskbar disappears then reappears after about five seconds but the location is not updated. This is repeatable. I can add London (UK) to the list with no problems."

"Same crash when selecting North America -> United States -> Texas -> Houston -> Clover"

"The common factor is that neither location entry in /usr/share/libgweather/Locations.xml has a <coordinates/> tag."

"Thread 1 (Thread 0xb6d56720 (LWP 8387)):

+ Trace 192403

  • #0 clock_zoneinfo_get_coords
    at clock-zoneinfo.c line 196
  • #1 run_find_location_save
    at clock.c line 3202
  • #2 IA__g_cclosure_marshal_VOID__VOID
    at /build/buildd/glib2.0-2.16.1/gobject/gmarshal.c line 77
  • #3 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 490
  • #4 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2440
  • #5 IA__g_signal_emit_valist
  • #6 IA__g_signal_emit
    at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2243
  • #7 IA__gtk_button_clicked
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 889
  • #8 gtk_real_button_released
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 1484
  • #9 IA__g_cclosure_marshal_VOID__VOID
    at /build/buildd/glib2.0-2.16.1/gobject/gmarshal.c line 77
  • #10 g_type_class_meta_marshal
    at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 567
  • #11 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2370
  • #13 IA__g_signal_emit_valist
  • #14 IA__g_signal_emit
    at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2243
  • #15 IA__gtk_button_released
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 881
  • #16 gtk_button_button_release
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 1377
  • #17 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmarshalers.c line 84
  • #18 g_type_class_meta_marshal
    at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 567
  • #19 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2478
  • #21 IA__g_signal_emit_valist
  • #22 IA__g_signal_emit
    at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2243
  • #23 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkwidget.c line 4678
  • #24 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 2336
  • #25 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1556
  • #26 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c line 2351
  • #27 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2003
  • #28 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2636
  • #29 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2844
  • #30 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
  • #31 main
    at main.c line 100 






Comment 1


Philip Withnall





          2008-03-16 12:21:05 UTC
        



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






Comment 2


Philip Withnall





          2008-03-18 23:38:52 UTC
        



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






Comment 3


Anthony Waters





          2008-03-23 05:33:26 UTC
        



You appear to be correct that when the cities don't have that <coordinate> tag they cause the clock-applet to crash.  I tested it by inserting a bogus <coordinate> tag for Clover and the clock applet behaved as expected.  So from this I can think of a few solutions

1. Since we can detect when this error will occur we can catch it before the crash and show an error message about missing coordinates
2. Never show cities in the first place that have missing coordinates
3. Select the parent location and ignore the error (for example in the case of Clover it would select the city Houston)






Comment 4


Philip Withnall





          2008-03-27 14:35:28 UTC
        



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






Comment 5


Philip Withnall





          2008-03-28 23:22:35 UTC
        



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






Comment 6


Philip Withnall





          2008-03-29 14:34:21 UTC
        



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






Comment 7


Philip Withnall





          2008-03-29 21:06:24 UTC
        



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






Comment 8


Philip Withnall





          2008-04-02 19:43:56 UTC
        



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






Comment 9


Vincent Untz





          2008-04-03 16:34:16 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 10


Vincent Untz





          2008-04-03 16:40:21 UTC
        



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






Comment 11


Philip Withnall





          2008-04-25 22:49:33 UTC
        



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