Calendar closed unexpectedly

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

could you install evolution-data-server-dbg evolution-dbg libglib2.0-0-dbg and get a new one?

Done. Here's the second backtrace.

the new stacktrace has no crash

Right. In my original report I said the application does not crash. The calendar and notes portions quit (meaning they are visible, but the user can't input or view any data). The e-mail portion continues running fine.

you wrote in the description that the application closed, can you make a screenshot showing the issue?

I am sorry. I should not have used the word "closed." The calendar quit, but Evolution remained open. I'm attaching a screenshot. You can see the warning message, and that the calendar is open but there is no data in it.

This did not happen in the previous version of Evolution (under Ubuntu 8.10). I am reverting to that version (and distro) until this can be resolved. I still have the 9.04 LiveCD in case you need me to troubleshoot further.

the error indicates evolution-data-server is crashing

could you get an e-d-s stacktrace

I've tried twice unsuccessfully to do a stacktrace on evolution-data-server.

It doesn't work on evolution-data-server alone, since e-d-s is called from evolution.

It doesn't work if I identify evolution as the program to check. Evolution opens and then my system freezes. I have to cold reboot to regain control.

Here's the stacktrace log that was produced. Probably not of any value.

This one may have better data. I was able to run it with the pid.

Hi Guys,

Just like to add that I am also experiencing the same issue with OWA based exchange. After upgrading to 9.04.

Thanks
Chris

the way to get a stacktrace is either to use apport or gdb this way
- start evolution on the email component
- gdb --pid `pidof evolution-data-server`
(gdb) continue
- switch evolution to the calendar
- the gdb prompt will be stopped on the e-d-s crash
(gdb) backtrace

(gdb) backtrace
#0 0xb8010422 in __kernel_vsyscall ()
#1 0xb74276d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7429098 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb74205ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#4 0xb79f700c in icalerror_set_errno () from /usr/lib/libical.so.0
#5 0xb79e9738 in icalproperty_new_x () from /usr/lib/libical.so.0
#6 0xb6e9b396 in exchange_mapi_cal_util_mapi_props_to_comp () from /usr/lib/libexchangemapi-1.0.so.0
#7 0xb6ebc7a5 in ?? () from /usr/lib/evolution-data-server-1.2/extensions/libecalbackendmapi.so
#8 0xb6e96478 in exchange_mapi_connection_fetch_items () from /usr/lib/libexchangemapi-1.0.so.0
#9 0xb6ebf4ba in ?? () from /usr/lib/evolution-data-server-1.2/extensions/libecalbackendmapi.so
#10 0xb76207bf in g_thread_create_proxy (data=0xb5a822ee) at /build/buildd/glib2.0-2.20.1/glib/gthread.c:635
#11 0xb75654ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#12 0xb74e049e in clone () from /lib/tls/i686/cmov/libc.so.6

the new comment is an evolution-mapi issue is a different bug

I've tried to get a stacktrace but it isn't working. Here's the result:

ubuntu@ubuntu:~$ gdb --pid 'pidof evolution-data-server'
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
Illegal process-id: pidof evolution-data-server.
(gdb) quit

I've tried this with Evolution only open to e-mail, and then very quickly after I open Calendar but before it quits. Same result both times.

the ' and ` chars are not the same and you used the wrong one, you can replace `pidof evolution-data-server` by the actual pid number if you find that easier

Well, I corrected the character, but am still not having any success. First time pid said it needed an argument:

$ gdb --pid `pidof evolution-data-server`
gdb: option '--pid' requires an argument
Use `gdb --help' for a complete list of options.

So I went to the help menu and tried again with pid=PID. This time it said the program wasn't running. I even tried again very quickly after launching the calendar. Here's that result:

$ gdb --pid=PID `pidof evolution-data-server`
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
Illegal process-id: PID.
(gdb) continue
The program is not being run.

Am I still doing something wrong?

the processus is called "evolution-data-server-2.26" in jaunty in fact could you try with this one? you can also run "ps aux | grep evolution-data-server" and look to the first column number that's the pid to use

Okay, here's what I captured. Does this help?

(gdb) backtrace
#0 0xb7f24422 in __kernel_vsyscall ()
#1 0xb73ecae7 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb751d74b in IA__g_poll (fds=0x82a0a20, nfds=3, timeout=-1)
    at /build/buildd/glib2.0-2.20.1/glib/gpoll.c:127
#3 0xb750ff82 in g_main_context_iterate (context=0x826a528, block=1,
    dispatch=1, self=0x825b4c0)
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2761
#4 0xb75105ba in IA__g_main_loop_run (loop=0x828b130)
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2656
#5 0xb7746cc3 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#6 0x0804b96c in main (argc=136774728, argv=0xbfc3fe74) at server.c:417

Attaching a more thorough capture.

why did you ctrl-C? it's supposed to stop by itself when you get the bug and then you can get the stacktrace

I waited 20 minutes before hitting Ctrl-C. The Calendar had long quit, and everything had just hung.

I could try again and let it sit for hours if you think it will eventually complete.

Ken

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sebastien Bacher
Sent: Monday, April 27, 2009 12:38 PM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

why did you ctrl-C? it's supposed to stop by itself when you get the bug
and then you can get the stacktrace

--
Calendar closed unexpectedly
https://bugs.launchpad.net/bugs/366471
You received this bug notification because you are a direct subscriber
of the bug.

Status in “evolution-data-server” source package in Ubuntu: Incomplete

Bug description:
Binary package hint: evolution

In new installation of Ubuntu 9.04 "Jaunty Jackalope," using Evolution with a Microsoft Exchange server. When opening the calendar, it begins to populate with events, and then closes with this advisory note: "The Evolution calendars have quit unexpectedly. Your calendars will not be available until Evolution is restarted." Restarting Evolution reproduces the same problem. Problem reproducible in LiveCD, LiveUSB, and LiveUSB of Xubuntu 9.04 version (after installing Evolution with Synaptic).

No crash report available (Evolution didn't technically "crash"). Running on Lenovo x61s laptop (Intel Core2 Duo L7700 CPU @ 1.80GHz, 4 GB RAM.

In one instance, Evolution Tasks also closed unexpectedly.

1) Ubuntu release: 9.04 Jaunty Jackalope
2) Package: evolution 2.26.1-0ubuntu.1
3) I expected calendar to populate and remain open
4) Calendar started to populate, but closed unexpectedly.

and you got the error which is displayed on http://launchpadlibrarian.net/26006700/Screenshot.png indicated and no evolution-data-server crash? could it be that you restarted your session and had several of those running and you tried on the wrong one?

No, I only had one running. Wish I could take a movie instead of a static screenshot. When I go from e-mail to calendar (and check the block by "calendar"), events begin to populate. After a few seconds (maybe 10 seconds) they all disappear and the error message appears at the bottom ("Calendar quit unexpectedly"). I don't think anything crashes.

Ken

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sebastien Bacher
Sent: Monday, April 27, 2009 4:14 PM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

and you got the error which is displayed on
http://launchpadlibrarian.net/26006700/Screenshot.png indicated and no
evolution-data-server crash? could it be that you restarted your session
and had several of those running and you tried on the wrong one?

--
Calendar closed unexpectedly
https://bugs.launchpad.net/bugs/366471
You received this bug notification because you are a direct subscriber
of the bug.

Status in “evolution-data-server” source package in Ubuntu: Incomplete

Bug description:
Binary package hint: evolution

In new installation of Ubuntu 9.04 "Jaunty Jackalope," using Evolution with a Microsoft Exchange server. When opening the calendar, it begins to populate with events, and then closes with this advisory note: "The Evolution calendars have quit unexpectedly. Your calendars will not be available until Evolution is restarted." Restarting Evolution reproduces the same problem. Problem reproducible in LiveCD, LiveUSB, and LiveUSB of Xubuntu 9.04 version (after installing Evolution with Synaptic).

No crash report available (Evolution didn't technically "crash"). Running on Lenovo x61s laptop (Intel Core2 Duo L7700 CPU @ 1.80GHz, 4 GB RAM.

In one instance, Evolution Tasks also closed unexpectedly.

1) Ubuntu release: 9.04 Jaunty Jackalope
2) Package: evolution 2.26.1-0ubuntu.1
3) I expected calendar to populate and remain open
4) Calendar started to populate, but closed unexpectedly.

the screenshot clearly indicates that e-d-s is crashing though

could you also stop quoting a ton of extra lines at each message you send on the bug? that makes it hard to read on the webpage

Absolutely. Sorry about that. This is my first bug report, and I'm
just trying to include whatever might be helpful.

On Mon, 2009-04-27 at 22:11 +0000, Sebastien Bacher wrote:
> the screenshot clearly indicates that e-d-s is crashing though
>
> could you also stop quoting a ton of extra lines at each message you
> send on the bug? that makes it hard to read on the webpage
>

I am also experiencing this bug. I will try to supply additional information.

gdb did not log anything new when the error occurred. I was able to get the exchange calendar to appear for about 10 secs or so every time I selected "Show Only This Calendar" The attached debug log includes at least 4 passes of generating the error, but nothing new was output during this time. I exited evolution, then hit^c on gdb.

I am experiencing a similar problem:
As soon as calendar tries to get appointments from the google calendars it will quit. The calendar window is still visible but it will not show any appointments (not even from the local calendar). If I close evolution and restart it, I will be able to use the local calendars as long as I don't activate the google calendars.

This is a new problem. Last week (Jaunty release candidate) google calendar worked fine.

degrading the following packages fixed my problem:
libedataserverui1.2-8 2.26.1-0ubuntu2 -> 2.26.1-0ubuntu1
libexchange-storage1.2-3 2.26.1-0ubuntu2 -> 2.26.1-0ubuntu1

Leonard could you open a new bug about your issue so it can tracked efficiently?

I would. However, after upgrading again (in order to get all the dependencies right for the bug report) I cannot reproduce the bug. Maybe there was some difficulty contacting google involved, so, if it happens again, I will report a new bug. Thank you.

the libical upgrade on bug #368508 should workaround the bug, could you give it a try and comment on the other bug to say if it makes a difference for your issue?

I also experienced this problem and I applied the patch recommended by Kib Reed here:

https://bugs.launchpad.net/ubuntu/jaunty/+source/evolution-exchange/+bug/353187/comments/10

It solved my problem, which was very similar to the one reported.

Kib Reed's patch appears to be for an amd64 installation. Will it also work on my x86 32-bit installation?

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sebastien Bacher
Sent: Wednesday, April 29, 2009 5:24 AM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

the libical upgrade on bug #368508 should workaround the bug, could you
give it a try and comment on the other bug to say if it makes a
difference for your issue?

--
Calendar closed unexpectedly
https://bugs.launchpad.net/bugs/366471
You received this bug notification because you are a direct subscriber
of the bug.

Status in “evolution-data-server” source package in Ubuntu: Incomplete

Bug description:
Binary package hint: evolution

In new installation of Ubuntu 9.04 "Jaunty Jackalope," using Evolution with a Microsoft Exchange server. When opening the calendar, it begins to populate with events, and then closes with this advisory note: "The Evolution calendars have quit unexpectedly. Your calendars will not be available until Evolution is restarted." Restarting Evolution reproduces the same problem. Problem reproducible in LiveCD, LiveUSB, and LiveUSB of Xubuntu 9.04 version (after installing Evolution with Synaptic).

No crash report available (Evolution didn't technically "crash"). Running on Lenovo x61s laptop (Intel Core2 Duo L7700 CPU @ 1.80GHz, 4 GB RAM.

In one instance, Evolution Tasks also closed unexpectedly.

1) Ubuntu release: 9.04 Jaunty Jackalope
2) Package: evolution 2.26.1-0ubuntu.1
3) I expected calendar to populate and remain open
4) Calendar started to populate, but closed unexpectedly.

I have several issues preventing me from applying the patch. I had some difficulty with Kib Reed's process, but after adding source in my repository list, and several attempts (including apt-get update and build-dep evolution-exchange --fix-missing), I finally got to step 5. Here are the remaining issues.
1. Step 5 in Kib Reed's process says "cd evolution-exchange" but there is no file or directory with that name.
2. Step 6 calls eex.patch, but that file doesn't exist either.
3. Step 8 modifies the evolution-exchange deb file for amd64, but I'm running x86 32-bit.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of tgilbert328
Sent: Wednesday, April 29, 2009 9:46 AM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

I also experienced this problem and I applied the patch recommended by
Kib Reed here:

https://bugs.launchpad.net/ubuntu/jaunty/+source/evolution-
exchange/+bug/353187/comments/10

It solved my problem, which was very similar to the one reported.

--
Calendar closed unexpectedly
https://bugs.launchpad.net/bugs/366471
You received this bug notification because you are a direct subscriber
of the bug.

Status in “evolution-data-server” source package in Ubuntu: Incomplete

Bug description:
Binary package hint: evolution

In new installation of Ubuntu 9.04 "Jaunty Jackalope," using Evolution with a Microsoft Exchange server. When opening the calendar, it begins to populate with events, and then closes with this advisory note: "The Evolution calendars have quit unexpectedly. Your calendars will not be available until Evolution is restarted." Restarting Evolution reproduces the same problem. Problem reproducible in LiveCD, LiveUSB, and LiveUSB of Xubuntu 9.04 version (after installing Evolution with Synaptic).

No crash report available (Evolution didn't technically "crash"). Running on Lenovo x61s laptop (Intel Core2 Duo L7700 CPU @ 1.80GHz, 4 GB RAM.

In one instance, Evolution Tasks also closed unexpectedly.

1) Ubuntu release: 9.04 Jaunty Jackalope
2) Package: evolution 2.26.1-0ubuntu.1
3) I expected calendar to populate and remain open
4) Calendar started to populate, but closed unexpectedly.

I upgraded evolution-exchange-storage using -proposed as suggested in bug 353187. This fix resolved my problem also. No need to build from source, just install the -proposed update.

(sigh) I must be doing something wrong. I went to bug 353187, enabled jaunty-proposed, did an update, and checked status (dpkg --status evolution-exchange). It said the version I was running was 2.26.0-0ubuntu2, which I believe is the same version I had before. Just to be sure, I launched Evolution and went to the calendar. The problem still exists. How do I update to the -proposed version? I also searched for evolution-exchange-storage but couldn't find a package by that name.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Bruce Weyrauch
Sent: Wednesday, April 29, 2009 12:01 PM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

I upgraded evolution-exchange-storage using -proposed as suggested in
bug 353187. This fix resolved my problem also. No need to build from
source, just install the -proposed update.

--
Calendar closed unexpectedly
https://bugs.launchpad.net/bugs/366471
You received this bug notification because you are a direct subscriber
of the bug.

Status in “evolution-data-server” source package in Ubuntu: Incomplete

Bug description:
Binary package hint: evolution

In new installation of Ubuntu 9.04 "Jaunty Jackalope," using Evolution with a Microsoft Exchange server. When opening the calendar, it begins to populate with events, and then closes with this advisory note: "The Evolution calendars have quit unexpectedly. Your calendars will not be available until Evolution is restarted." Restarting Evolution reproduces the same problem. Problem reproducible in LiveCD, LiveUSB, and LiveUSB of Xubuntu 9.04 version (after installing Evolution with Synaptic).

No crash report available (Evolution didn't technically "crash"). Running on Lenovo x61s laptop (Intel Core2 Duo L7700 CPU @ 1.80GHz, 4 GB RAM.

In one instance, Evolution Tasks also closed unexpectedly.

1) Ubuntu release: 9.04 Jaunty Jackalope
2) Package: evolution 2.26.1-0ubuntu.1
3) I expected calendar to populate and remain open
4) Calendar started to populate, but closed unexpectedly.

what about trying the libical upgrade?

Again, I think I'm over my head. I have libical0 installed (ver. 0.43-2). The jaunty-proposed repository is enabled, and all my evolution-related packages report they are the latest version. Yet I still have the problem.

I upgraded to evolution-exchange version 2.26.0.0-0ubuntu3 from the -proposed repository, but still have the problem.

$ dpkg --status evolution-exchange
Package: evolution-exchange
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 3460
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: i386
Version: 2.26.0-0ubuntu3

$ dpkg --status libical0
Package: libical0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 616
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: i386
Source: libical
Version: 0.43-2ubuntu1
Depends: libc6 (>= 2.4), tzdata

One more data point. I downloaded Linux Mint 7 Release Candidate 1 and installed it in a virtual machine, then installed Evolution (and evolution-exchange) to test how it responded. It's noteworthy that I do NOT have the problem in this distribution. Here are the status results for evolution-exchange and libical:

$ dpkg --status evolution-exchange
Package: evolution-exchange
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 3460
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: i386
Version: 2.26.0-0ubuntu3

$ dpkg --status libical0
Package: libical0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 616
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: i386
Source: libical
Version: 0.43-2
Depends: libc6 (>= 2.4), tzdata

could you get a stacktrace using the current libical version? do you have the issue using an another user or a guest session?

I'm attaching it. This is the strace file for the version that still has the problem. I apologize for its size (4.1 MB), but I don't know what part of it (if any) might be valuable.

Here's a strace file for the version that does not have the problem. Again, I apologize for the size (3.9 MB).

straces are not useful, what is required is a gdb stacktrace

Well, you're over my head. Glad to help if you or someone can give me a step-by-step procedure.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sebastien Bacher
Sent: Friday, May 08, 2009 11:49 AM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

straces are not useful, what is required is a gdb stacktrace

you already did it before on this bug no?

Okay, is this what you are looking for?

yes but this one seems to show a normal run

Well, the calendar quit posting data during the run (in fact, all the data disappeared). I can't run a separate gdb backtrace for evolution-exchange or libical0--pidof won't generate a number for either of those, even when evolution is running and I've switched to calendar. Evolution does not crash. I don't know what else to try.

The following two lines in the backtrace are germane. The first one appeared when I switched to calendar. Everything was populating normally until it quit, which caused the second line to appear.

** (evolution:3450): DEBUG: EI: SHELL STARTUP
calendar-gui-Message: Check if default client matches (1240847404.3256.3@kwatson-jaunty 1240847404.3256.3@kwatson-jaunty)
calendar-gui-Message: Error occurred while existing dialog active:

did you read comment 15 on how to get an e-d-s backtrace there?

Attaching the e-d-s-gdb-backtrace. Note that gdb did not stop when the e-d-s- backend crashed. I had to ^c to stop it. Evolution frontend never crashes.

I upgraded evolution-exchange to evolution-exchange-dbg in synaptic and that fixed my problem.

Alas. I spoke too soon. My installation of ubuntu jaunty as a guest OS in VirtualBox works fine. I just tried the same thing in my full installation of xubuntu jaunty and I still have the problem. Same version of evolution-exchange in both installations (2.26.0-0ubuntu3)

there is no crash there, the bug is somewhat looping, could you redescribe clearly what issue you get using the current versions and how to trigger the bug?

The issue is exactly as in my first post. Open evolution with the account connected to a Microsoft exchange server; switch to calendar; data begins to populate the calendar, but after 10 to 20 seconds, data disappears and the "evolution calendar quit unexpectedly" warning appears. This happens in Xubuntu 9.04 with evolution-exchange version 2.26.0-0ubuntu3.

Somehow it does not happen anymore with a guest instance of Ubuntu 9.04 with evolution-exchange 2.26.0-0ubuntu3. (Calendar works fine and stays connected to the evolution-exchange backend.)

It never happened with a guest instance Linux Mint 7RC1.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sebastien Bacher
Sent: Sunday, May 10, 2009 4:32 AM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

there is no crash there, the bug is somewhat looping, could you
redescribe clearly what issue you get using the current versions and how
to trigger the bug?

the calendar quit indicates an e-d-s crash but your recent log shows a manual interruption, could you try doing that
- start your session
- start evolution on the email component
- use gdb as indicated before on e-d-s
- type "continue" on the (gdb) line
- switch to the calendar in evolution or do whatever you usually do to get the error

the gdb command should stop by itself when you run into the error without you having to Ctrl-C, when it does type "backtrace full" there

That is exactly what I did. After switching to calendar and the error occurred, gdb never stopped. I let it run for an hour before hitting Ctrl-C. I wish I knew another way to get you a backtrace.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sebastien Bacher
Sent: Monday, May 11, 2009 2:38 AM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

the calendar quit indicates an e-d-s crash but your recent log shows a manual interruption, could you try doing that
- start your session
- start evolution on the email component
- use gdb as indicated before on e-d-s
- type "continue" on the (gdb) line
- switch to the calendar in evolution or do whatever you usually do to get the error

the gdb command should stop by itself when you run into the error
without you having to Ctrl-C, when it does type "backtrace full" there

no idea how to debug it then, you might want to open a bug on bugzilla.gnome.org where the software writters will read it though

Good news. Libical0 updated today with system updates, and the problem is gone.

closing the bug since that works now, you probably didn't install the candidate version correctly before because the update is the same one

I'm experiencing this very same error reported previously (I quote original report):

"kwatson512 wrote on 2009-05-10: #62

The issue is exactly as in my first post. Open evolution with the account connected to a Microsoft exchange server; switch to calendar; data begins to populate the calendar, but after 10 to 20 seconds, data disappears and the "evolution calendar quit unexpectedly" warning appears. This happens in Xubuntu 9.04 with evolution-exchange version 2.26.0-0ubuntu3."

I'm running Ubuntu 9.10 (32 bits).
Tried many ways of installation, and the bug was still there.
Then, moved Synaptic to "proposed" level; and persists.
Would you reopen this bug?

Regards

Same bug here in Ubuntu 10.04 LTS (Lucid Lynx) with the latest updates up until 2010-05-21. I think somebody should give some massive priority to this. I guess there are quite a lot of people doomed to use Exchange. And it just doesn't work people ...