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 80578 - gnomecal crashed
gnomecal crashed
Status: RESOLVED DUPLICATE of bug 80466
Product: gnome-pim
Classification: Deprecated
Component: gnomecal
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pim Maintainers
gnome-pim Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-02 17:28 UTC by Gandhi
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gandhi 2002-05-02 17:28:43 UTC
Package: gnome-pim
Severity: blocker
Version: 1.4.6
Synopsis: gnomecal crashed
Bugzilla-Product: gnome-pim
Bugzilla-Component: gnomecal

Description:
gnomecal (part of debian package gnome-pim)
started to crash after i upgraded to the latest version of woody.

woody gnomecal was working fine, but now everytime, it simply
crashes even before opening.

that's all i can say for now. basically, my distribution
is debian testing (woody) and gnomecal crashes without fail.

sorry for this shabby bug report, it is the best i can do. i am
not a developer.

-gandhi



Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x40660a69 in wait4 () from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6
  • #1 __check_rhosts_file
    from /lib/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 sigaction
    from /lib/libc.so.6
  • #4 gnome_calendar_goto
  • #5 gncal_week_view_get_type
  • #6 gncal_week_view_get_type
  • #7 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #8 gtk_signal_remove_emission_hook
    from /usr/lib/libgtk-1.2.so.0
  • #9 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #10 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #11 gtk_calendar_select_month
    from /usr/lib/libgtk-1.2.so.0
  • #12 gncal_week_view_set
  • #13 gncal_week_view_new
  • #14 gnome_calendar_get_type
  • #15 gnome_calendar_new
  • #16 new_calendar
  • #17 main
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6
  • #1 __check_rhosts_file
    from /lib/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 sigaction
    from /lib/libc.so.6
  • #4 gnome_calendar_goto
  • #5 gncal_week_view_get_type
  • #6 gncal_week_view_get_type
  • #7 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-02 13:28 -------

The original reporter (Gandhi@lmm.fis.ufal.br) 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-02 17:38:17 UTC
Your bugreport is far better than others I've seen :)



*** This bug has been marked as a duplicate of 80466 ***