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 641032 - MAPI Calendar crashes (along with memo and tasks)
MAPI Calendar crashes (along with memo and tasks)
Status: RESOLVED DUPLICATE of bug 629836
Product: evolution-mapi
Classification: Applications
Component: Calendar
0.30.x
Other Linux
: Normal critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2011-01-31 14:07 UTC by Dave Sampson
Modified: 2011-02-07 11:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
evolution-calendar-mapi-backtrace (1.43 KB, text/plain)
2011-01-31 14:07 UTC, Dave Sampson
Details

Description Dave Sampson 2011-01-31 14:07:12 UTC
Created attachment 179718 [details]
evolution-calendar-mapi-backtrace

Open Evolution with at least one MAPI account configured
click on Calendar

error on mapi:user@server
error fetching changes from server

The evolution tasks have quit unexpectedly
your tasks will not be available until Evolution is restarted

The evolution calendar have quit unexpectedly
your calendars will not be available until Evolution is restarted

The evolution memo has quit unexpectedly
your calendars will not be available until Evolution is restarted

tried:
* deleting .evolution/cache/calendar
    No change
* restarting evolution
    No Change

running Ubuntu 10.10, evolution 2.30.3
Comment 1 Milan Crha 2011-01-31 15:17:46 UTC
Thanks for a bug report. The attachment doesn't contain any backtrace, probably because it was attached to the evolution, instead of crashing e-calendar-factory process. Please run e-calendar-factory under gdb, then run evolution from another terminal, and when it crashes (you get a gdb prompt in the e-calendar-factory) invoke the gdb command "t a a bt" (quotes for clarity only). And then paste all below this and say 10 lines above this gdb command. Make sure you'll not expose any private data, like server names, passwords and such, because the backtrace can contain them. Please also note that 2.30.3 is quite old, the latest sable evolution is 2.32.1 and there is planned an update on it to 2.32.2 next week.
Comment 2 Dave Sampson 2011-02-04 15:05:57 UTC
process I followed on ubuntu 10.10. I hope this helps... I don't think any personal info is found bellow. GDB did dump out items from my personal calendar but I did not include snippets bellow.

Hope this helps.
NOTE: it was a challenge to figure out how to launch e-cal factory, now I know though.

open terminal 1:
==================
gdb /usr/lib/evolution/e-calendar-factory
(gdb) run


open Terminal 2:
==================
gdb evolution
(gdb) run

Evolution opens.
Click on Calendar button
Calendar crashes....

from e-cal terminal 1:
======================
(gdb) t a a bt


10 lines above gdb command before crash:
==============================
 PR_INTERNET_CPID: 1252
unhandled conversion case in cast_SPropValue(): 0x1048
e-calendar-factory: libmapi/property.c:732: cast_SPropValue: Assertion `0' failed.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe3569700 (LWP 11776)]
0x00007ffff7443ba5 in raise () from /lib/libc.so.6
Comment 3 Milan Crha 2011-02-07 11:23:19 UTC
> unhandled conversion case in cast_SPropValue(): 0x1048
> e-calendar-factory: libmapi/property.c:732: cast_SPropValue: Assertion `0'
> failed.

Thanks for the update. The above is our issue, and the corresponding bug
is bug #629836, which I'm marking this one as a duplicate.

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