On Wed, 2014-06-18 at 10:25 +0300, Robert Munteanu wrote:
> I'm not sure what causes this behaviour, any help would be
> appreciated.
Hi,
you can see what evolution-ews does when you run evolution like:
$ EWS_DEBUG=2 evolution
then let it settle with its activities after start and send the
message. It's better to make it settle, to not overlap the send
activity with other activities.
When you get to that state of long-waiting composer window, then grab a
backtrace of running evolution, to see what it actually does. Make
sure you'll have installed also debug info packages for
evolution-data-server, evolution and evolution-ews and check the
resulting bt.txt for any private information. The gdb command is:
$ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
It may show whether you face similar issues as Andre or a completely
different.
Hope it helps,
Milan
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
