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 271693 - Evolution crash
Evolution crash
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 353510 355588 359606 362801 411522 434874 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-01-24 20:24 UTC by nachimpitt
Modified: 2013-09-10 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nachimpitt 2005-01-24 20:24:43 UTC 
Distribution: Fedora Core release 2 (Tettnang)
Package: Evolution
Priority: Normal
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crash
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:


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

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.0'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -150949760 (LWP 19190)]
[New Thread 1446865840 (LWP 19319)]
[Thread debugging using libthread_db enabled]
[New Thread -150949760 (LWP 19190)]
[New Thread 1446865840 (LWP 19319)]
[Thread debugging using libthread_db enabled]
[New Thread -150949760 (LWP 19190)]
[New Thread 1446865840 (LWP 19319)]
[New Thread 1436375984 (LWP 19243)]
[New Thread 129350576 (LWP 19242)]
[New Thread 118860720 (LWP 19228)]
[New Thread 108370864 (LWP 19227)]
[New Thread 97881008 (LWP 19203)]
[New Thread 87391152 (LWP 19202)]
[New Thread 66526128 (LWP 19201)]
0x00d8a402 in ?? ()

+ Trace 54871

Thread 1 (Thread -150949760 (LWP 19190))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libglib-2.0.so.0
  • #9 e_cal_model_set_default_client
    at e-cal-model.c line 1206
  • #10 default_client_cal_opened_cb
    at gnome-cal.c line 2183
  • #11 g_cclosure_marshal_VOID
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgobject-2.0.so.0
  • #13 g_signal_emit_by_name
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgobject-2.0.so.0
  • #16 async_signal_idle_cb
    at e-cal.c line 1628
  • #17 g_child_watch_add
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libglib-2.0.so.0
  • #18 g_main_depth
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libglib-2.0.so.0
  • #21 g_main_loop_run
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libglib-2.0.so.0
  • #22 bonobo_main
    from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libbonobo-2.so.0
  • #23 main
    at main.c line 585
  • #0 ?? 



Unknown reporter: nachimpitt@yahoo.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 C Shilpa 2005-04-07 12:57:41 UTC 
*** bug 273130 has been marked as a duplicate of this bug. ***
Comment 2 C Shilpa 2005-04-08 09:54:25 UTC 
*** bug 274201 has been marked as a duplicate of this bug. ***
Comment 3 viren 2005-09-09 13:44:08 UTC 

*** This bug has been marked as a duplicate of 273205 ***
Comment 4 Karsten Bräckelmann 2006-08-30 19:31:05 UTC 
Looking at the stacktrace, I don't see how this is a duplicate of bug 273205...
Comment 5 Karsten Bräckelmann 2006-08-30 19:31:34 UTC 
*** Bug 353510 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2006-09-04 13:00:47 UTC 
updating version info, bug 353510 has an uptodate stacktrace
Comment 7 Karsten Bräckelmann 2006-09-17 13:29:46 UTC 
*** Bug 355588 has been marked as a duplicate of this bug. ***
Comment 8 Karsten Bräckelmann 2006-09-17 13:31:42 UTC 
Still valid with 2.8, see bug 355588.
Comment 9 Karsten Bräckelmann 2006-10-04 14:12:05 UTC 
*** Bug 359606 has been marked as a duplicate of this bug. ***
Comment 10 Sam Morris 2006-10-04 14:21:07 UTC 
The trace for bug 359606 has symbols and local variables
Comment 11 André Klapper 2007-02-24 14:15:00 UTC 
*** Bug 362801 has been marked as a duplicate of this bug. ***
Comment 12 André Klapper 2007-02-24 14:15:04 UTC 
*** Bug 411522 has been marked as a duplicate of this bug. ***
Comment 13 André Klapper 2007-05-21 13:11:19 UTC 
*** Bug 434874 has been marked as a duplicate of this bug. ***
Comment 14 Akhil Laddha 2008-08-22 11:13:36 UTC 
can anyone please try on current stable 2.22.3.1 and confirm that crash still happens or it had been fixed, thanks in advance.
Comment 15 Akhil Laddha 2008-10-31 12:35:42 UTC 

Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.24.x or later), please reopen. thanks in advance.