GNOME Bugzilla – Bug 735036
Evolution crashes on creation of folder on exchange account via ews-pluging
Last modified: 2014-12-01 15:13:30 UTC
Hallo evolution-ews devs I'm on Ubuntu 14.04 LTS using Evolution 3.10.4 and evolution-ews 3.10.2 (package 3.10.3-0ubuntu2). When I try to create a new folder on my exchange account evolution first grays out and then eventually crashes (after ~1min). When I open evolution again, the folder is created and I can use it, but it would be nice to be able to create folders without having evolution crash. Steps to recreate. (1. Setup an exchange account with evolution-ews and sync.) 2. Create a new folder on the exchange account. 3. Wait for evolution to crash. If you need any additional information, like e.g. exchange server version (and maybe you have some hints as to how I can get that information from evolution) please just tell me and I will get any information you need. If this bug is known and fixed in a newer version, then I'm sorry about the noise. Regards Kenneth Nielsen
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 283968 [details] Backtrace from the crash
Hi Andre This is the first time I have tried to collect a backtrace, so I hope it is correct. I installed dbg packages for the common dependencies and for evolution, but I was not able to find a debug package for the ews evolution extension. Let me know if it is usable, otherwise I will try again or if you need any other information. Regards Kenneth
Thanks for the update. It's better to paste backtraces inline, it's much easier for searching and such.
+ Trace 234385
Thread 1 (Thread 0x7ffff7f9ca40 (LWP 10743))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 722698 ***