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 112274 - Gnomecal crash
Gnomecal crash
Status: RESOLVED DUPLICATE of bug 66338
Product: gnome-pim
Classification: Deprecated
Component: gnomecal
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pim Maintainers
gnome-pim Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-05-05 11:51 UTC by nice
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nice 2003-05-05 11:51:30 UTC 
Package: gnome-pim
Severity: normal
Version: 1.4.9
Synopsis: Gnomecal crash
Bugzilla-Product: gnome-pim
Bugzilla-Component: gnomecal

Description:
Description of Problem:
Left it running for a few days, this morning when I got up, bug buddy
said it had crashed.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/local/bin/gnomecal'

0xffffe002 in ?? ()

+ Trace 36554

  • #0 ??
  • #1 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_get_show_events
    from /usr/lib/libgdk-1.2.so.0
  • #5 g_io_add_watch
    from /usr/lib/libglib-1.2.so.0
  • #6 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #8 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #10 main
    at main.c line 1050
  • #11 __libc_start_main
    from /lib/tls/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-05 07:51 -------

Reassigning to the default owner of the component, gnome-pim-maint@bugzilla.gnome.org.
Comment 1 Sebastian Rittau 2003-05-05 17:42:19 UTC 

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