Evolution frequently displays "Your Calendar/Tasks will not be available until Evolution is restarted." (Ubuntu 8.04 Alpha 4)

Thanks for your report, may you please run evolution as: E2K_DEBUG=5 CAMEL_DEBUG=all evolution >& evolution.log and attach that log to the report? thanks in advance.

Here's the log.

Still happening in hardy. Please let me know if I can be of any help to resolve this issue.

could you get an evolution-data-server stacktrace?

Hi Sebastien,

I'll be happy to do that, I just don't know how I do that. Please tell me
how I can do it and I will send you the stacktrace tonight (PST).

Thanks for working on this issue,
Johannes

On Fri, May 23, 2008 at 12:32 AM, Sebastien Bacher <email address hidden>
wrote:

> could you get an evolution-data-server stacktrace?
>
> --
> Evolution frequently displays "Your Calendar/Tasks will not be available
> until Evolution is restarted." (Ubuntu 8.04 Alpha 4)
> https://bugs.launchpad.net/bugs/191548
> You received this bug notification because you are a direct subscriber
> of the bug.
>

you can read http://wiki.ubuntu.com/DebuggingProgramCrash about how to get a stacktrace

I created the stack trace for the evolution process. I am not sure if that is right one. I assume that it has something to do with the exchange plugin. The calendar does not crash when I look only at my google calendar. Let me know if I should create a strace for the evolution-exchange process as well.

In the log you will see that at 11:07:11 I started to look at the calendar. I got the "Your Calendar will not be available until Evolution is restarted." message 10 seconds after that. I closed evolution after another 10 seconds.

I hope that helps

how did you get the stacktrace? the way you should get it is:
- start evolution
- open a command line
- gdb --pid $(pidof evolution-data-server)
(gdb) continue
- switch to evolution and get the crash
- switch back to gdb and enter "thread apply all bt full"
- copy the stacktrace to the bug

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

I have the same issue with Ubuntu Lucid and Evolution 2.28.3
When I go in the calendar, my exchange calendar is not displayed and I have to tick the box next to it.
After ticking it is synching the cal and after few seconds it crashes with a message saying "The Evolution calendars have quit unexpectedly" and clicking on that message gives the one above.

The syslog is giving:
kernel: [ 2203.955844] evolution-excha[2711]: segfault at 0 ip 046777a0 sp b5dfc128 error 4 in libc-2.11.1.so[4604000+153000]

And the gdb trace is:
Thread 6 (Thread 0xb73ffb70 (LWP 2653)):
#0 0x00385422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x00b27342 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#2 0x002a80ce in ?? () from /usr/lib/libgthread-2.0.so.0
No symbol table info available.
#3 0x08505bbc in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#4 0x08557d53 in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#5 0x08555def in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#6 0x00b2296e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#7 0x038d3a4e in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.

Thread 4 (Thread 0xb63fdb70 (LWP 2646)):
#0 0x038797a0 in ?? () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#1 0x00159000 in e_cal_component_set_attachment_list () from /usr/lib/libecal-1.2.so.7
No symbol table info available.
#2 0x0807450c in ?? ()
No symbol table info available.
#3 0x08074e6a in ?? ()
No symbol table info available.
#4 0x08555def in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#5 0x00b2296e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#6 0x038d3a4e in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.

Thread 2 (Thread 0xb760bb70 (LWP 2616)):
#0 0x00385422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x038c5b86 in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x0853c4eb in g_poll () from /lib/libglib-2.0.so.0
No symbol table info available.
#3 0x0852f0ac in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#4 0x0852f817 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5 0x00b2296e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#6 0x038d3a4e in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.

Thread 2 (Thread 0xb760bb70 (LWP 2616)):
#0 0x00385422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x038c5b86 in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x0853c4eb in g_poll () from /lib/libglib-2.0.so.0
No symbol table info available.
#3 0x0852f0ac in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#4 0x0852f817 in g_main_loop_run () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#5 0x00991400 in ?? () from /usr/lib/libORBit-2.so.0
No symbol table info availabl...

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.