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 80466 - gnomecal refuses to start (gnomecal Crash at 217.84.107.52)
gnomecal refuses to start (gnomecal Crash at 217.84.107.52)
Status: VERIFIED FIXED
Product: gnome-pim
Classification: Deprecated
Component: gnomecal
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pim Maintainers
gnome-pim Maintainers
: 80447 80549 80562 80565 80578 80598 80615 80624 80662 80788 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-05-01 13:18 UTC by f.kalhammer
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description f.kalhammer 2002-05-01 13:19:17 UTC 
Package: gnomecal
Version: 1.4.5
Severity: 

>Synopsis: gnomecal refuses to start
>Class: sw-bug
System: Athlon 1000MHz - Debian Woody 

>Description:
Since today gnomecal refuses to start. If I try to start it (either via menu or via command) I just see the message which led me to this site.

Yesterday it worked fine and I added some more dates. 

>How-To-Repeat:
Just try to start it in any matter. Even if I try it under another UID, it refuses to start.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-01 09:19 -------

The original reporter (f.kalhammer@online.de) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-pim-maint@bugzilla.gnome.org.
Comment 1 Christian Biesinger 2002-05-01 14:03:08 UTC 

*** This bug has been marked as a duplicate of 77521 ***
Comment 2 Sebastian Rittau 2002-05-01 23:53:22 UTC 
Actually it seems that this is a new bug; I'm also experiencing it
with GNOME-PIM 1.4.6, and there are indication that this bug is caused
by external circumstances.
Comment 3 Sebastian Rittau 2002-05-01 23:54:15 UTC 
*** Bug 80447 has been marked as a duplicate of this bug. ***
Comment 4 Sebastian Rittau 2002-05-02 00:00:43 UTC 
So, here is a stack trace from the Debian BTS:

(gdb) bt

+ Trace 21578

  • #0 gnome_calendar_get_type
  • #1 gnome_calendar_goto
  • #2 gncal_week_view_get_type
  • #3 gncal_week_view_get_type
  • #4 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #5 gtk_signal_remove_emission_hook
    from /usr/lib/libgtk-1.2.so.0
  • #6 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #7 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #8 gtk_calendar_select_month
    from /usr/lib/libgtk-1.2.so.0
  • #9 gncal_week_view_set
  • #10 gncal_week_view_new
  • #11 gnome_calendar_get_type
  • #12 gnome_calendar_new
  • #13 new_calendar
  • #14 main
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #0 get_current_page
    at gnome-cal.c line 79
  • #1 gnome_calendar_goto
    at gnome-cal.c line 113
  • #2 jump_to_day
    at gncal-week-view.c line 71
  • #3 sync_week
    at gncal-week-view.c line 92
  • #4 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #5 gtk_signal_remove_emission_hook
    from /usr/lib/libgtk-1.2.so.0
  • #6 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #7 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #8 gtk_calendar_select_month
    from /usr/lib/libgtk-1.2.so.0
  • #9 gncal_week_view_set
    at gncal-week-view.c line 223
  • #10 gncal_week_view_new
    at gncal-week-view.c line 164
  • #11 setup_widgets
    at gnome-cal.c line 54
  • #12 gnome_calendar_new
    at gnome-cal.c line 234
  • #13 new_calendar
    at main.c line 697
  • #14 main
    at main.c line 1049 
74
}
75

76
static GtkWidget *
77
get_current_page (GnomeCalendar *gcal)
78
{
79
	return GTK_NOTEBOOK (gcal->notebook)->cur_page->child;
80
}
81

82
char *
83
gnome_calendar_get_current_view_name (GnomeCalendar *gcal)
(gdb) p gcal->notebook 
$1 = (GtkWidget *) 0x80f9340
(gdb) p ((GtkNotebook *) gcal->notebook)->cur_page
$2 = (GtkNotebookPage *) 0x0
(gdb)
Comment 5 Sebastian Rittau 2002-05-02 00:20:04 UTC 
I still haven't got a clue, why this started to occur now, but I've
worked around the problem.
Comment 6 Christian Biesinger 2002-05-02 10:47:33 UTC 
*** Bug 80549 has been marked as a duplicate of this bug. ***
Comment 7 Christian Biesinger 2002-05-02 16:20:38 UTC 
*** Bug 80562 has been marked as a duplicate of this bug. ***
Comment 8 Christian Biesinger 2002-05-02 16:21:08 UTC 
*** Bug 80565 has been marked as a duplicate of this bug. ***
Comment 9 Christian Biesinger 2002-05-02 17:38:15 UTC 
*** Bug 80578 has been marked as a duplicate of this bug. ***
Comment 10 Christian Biesinger 2002-05-02 21:30:36 UTC 
*** Bug 80615 has been marked as a duplicate of this bug. ***
Comment 11 Sebastian Rittau 2002-05-02 22:20:47 UTC 
*** Bug 80598 has been marked as a duplicate of this bug. ***
Comment 12 Sebastian Rittau 2002-05-02 23:33:45 UTC 
*** Bug 80624 has been marked as a duplicate of this bug. ***
Comment 13 Sebastian Rittau 2002-05-04 16:00:15 UTC 
*** Bug 80662 has been marked as a duplicate of this bug. ***
Comment 14 Sebastian Rittau 2002-05-04 16:00:35 UTC 
*** Bug 80788 has been marked as a duplicate of this bug. ***