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 525715 - crash in Tasks: Opening evolution after ...
crash in Tasks: Opening evolution after ...
Status: RESOLVED DUPLICATE of bug 544110
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.12.x
Other All
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2008-04-02 08:42 UTC by jonathanwestlake
Modified: 2008-12-22 13:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description jonathanwestlake 2008-04-02 08:42:15 UTC 
Version: 2.12

What were you doing when the application crashed?
Opening evolution after boot, gnome keyring authorised...
Seems ??? to be do with ms-exchange access and tasks / calendars ??
Also using IMAP as primary mail, ms-exchange for calendar sharing etc.
( In attached bug report name / mail-URLs etc are replaced with <<SNIP SNIP>> - all urls look good, as do usernames etc.)


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.24.3-50.fc8 #1 SMP Thu Mar 20 14:47:10 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 87871488 vsize: 87871488 resident: 29913088 share: 9035776 rss: 29913088 rss_rlim: 4294967295
CPU usage: start_time: 1207124433 rtime: 47 utime: 39 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208342240 (LWP 2941)]
[New Thread -1222255728 (LWP 3411)]
[New Thread -1211495536 (LWP 2953)]
0x00110402 in __kernel_vsyscall ()

+ Trace 193982

Thread 1 (Thread -1208342240 (LWP 2941))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 __kernel_vsyscall
  • #10 raise
    from /lib/libc.so.6
  • #11 abort
    from /lib/libc.so.6
  • #12 g_logv
    from /lib/libglib-2.0.so.0
  • #13 g_log
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libgthread-2.0.so.0
  • #15 e_cal_backend_sync_dispose
    at e-cal-backend-sync.c line 978
  • #16 dispose
    at e-cal-backend-exchange.c line 1939
  • #17 dispose
    at e-cal-backend-exchange-calendar.c line 2370
  • #18 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_value_unset
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #23 e_cal_backend_remove_client
    at e-cal-backend.c line 393
  • #24 listener_died_cb
    at e-cal-backend.c line 387
  • #25 ??
    from /usr/lib/libORBit-2.so.0
  • #26 ??
    from /usr/lib/libORBit-2.so.0
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 ??
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #32 main
    at main.c line 238
  • #33 __libc_start_main
    from /lib/libc.so.6
  • #34 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7 sec old) ---------------------
(evolution-alarm-notify:2754): libecal-WARNING **: e-cal.c:318: Unexpected response
alarm-notify.c:385 (alarm_notify_add_calendar) exchange://<<SNIP SNIP>>;auth=Basic@<<SNIP SNIP>>/;personal/Calendar - Calendar Open Async... 0xb5d006a0
alarm-notify.c:216 (load_calendars) - Loading Calendar file:///home/<<SNIP SNIP>>/.evolution/tasks/local/system 
alarm-notify.c:385 (alarm_notify_add_calendar) file:///home/<<SNIP SNIP>>/.evolution/tasks/local/system - Calendar Open Async... 0x9922750
alarm-notify.c:216 (load_calendars) - Loading Calendar exchange://<<SNIP SNIP>>;auth=Basic@<<SNIP SNIP>>/;personal/Tasks 
get <<SNIP SNIP>> exchange://<<SNIP SNIP>>;auth=Basic@<<SNIP SNIP>>/
Find Items 0
(evolution-alarm-notify:2754): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution-alarm-notify:2754): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running...
alarm-notify.c:385 (alarm_notify_add_calendar) exchange://<<SNIP SNIP>>;auth=Basic@<<SNIP SNIP>>/;personal/Tasks - Calendar Open Async... 0xb5d02ad0
alarm-notify.c:216 (load_calendars) - Loading Calendar file:///home/<<SNIP SNIP>>/.evolution/memos/local/system 
alarm-notify.c:385 (alarm_notify_add_calendar) file:///home/<<SNIP SNIP>>/.evolution/memos/local/system - Calendar Open Async... 0x99264d0
--------------------------------------------------
Comment 1 Milan Crha 2008-12-22 13:37:07 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.

It's the same issue as in the other bug I'm marking as a duplicate of. One thread is opening the calendar, bug the other one wants to free that backend. The lock is locked at the moment, thus it crashes.

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