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 386390 - Evolution Crashes when accessing calendar
Evolution Crashes when accessing calendar
Status: RESOLVED DUPLICATE of bug 348126
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 386388 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-16 02:53 UTC by me
Modified: 2007-01-03 18:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description me 2006-12-16 02:52:46 UTC
Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution Crashes when accessing calendar
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Updated FC5. Delighted to see a prompt for a password for my Exchange
server (yes!). Enterd my password and it appears that my calendar is
synched as I can see new appointments that matches my Outlook calendar
(yes!!!). However when I try to do anything else in Evolution it
freezes. It appears that the storage part of the app may be what is
bombing.

Steps to reproduce the crash:
1. Launch and synch with Exchange server.
2. Attempt to view another day besides the one displayed on startup.

Expected Results:
Expect to see other dates' information and appointments. Expect not to
freeze.

How often does this happen?
100% of the time currently.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912535779680 (LWP 25873)]
[New Thread 1178904896 (LWP 25941)]
[New Thread 1157925184 (LWP 25924)]
[New Thread 1094986048 (LWP 25907)]
[New Thread 1094719808 (LWP 25906)]
[New Thread 1084229952 (LWP 25903)]
(no debugging symbols found)
0x0000003a9bf09766 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0

Thread 3 (Thread 1157925184 (LWP 25924))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /usr/lib64/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib64/libglib-2.0.so.0
  • #8 camel_exchange_store_connected
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #9 camel_object_trigger_event
    from /usr/lib64/libcamel-1.2.so.0
  • #10 camel_stub_send
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #11 start_thread
    from /lib64/libpthread.so.0
  • #12 clone
    from /lib64/libc.so.6
  • #13 ??




------- Bug created by bug-buddy at 2006-12-16 02:54 -------

Comment 1 André Klapper 2006-12-22 21:11:13 UTC
*** Bug 386388 has been marked as a duplicate of this bug. ***
Comment 2 palfrey 2007-01-03 18:35:46 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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