RE: [Bug 366471] Re: Calendar closed unexpectedly

Good news. Libical0 updated today with system updates, and the problem is gone. -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list deskt

RE: [Bug 366471] Re: Calendar closed unexpectedly

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: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of

RE: [Bug 366471] Re: Calendar closed unexpectedly

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

[Bug 366471] Re: Calendar closed unexpectedly

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) -- Calendar closed un

[Bug 366471] Re: Calendar closed unexpectedly

I upgraded evolution-exchange to evolution-exchange-dbg in synaptic and that fixed my problem. -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mail

[Bug 366471] Re: Calendar closed unexpectedly

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. ** Attachment added: "e-d-s-gdb-backtrace.txt" http://launchpadlibrarian.net/26510160/e-d-s-gdb-backtrace.txt -- Calendar closed unexpect

RE: [Bug 366471] Re: Calendar closed unexpectedly

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 cr

[Bug 366471] Re: Calendar closed unexpectedly

Okay, is this what you are looking for? ** Attachment added: "gdb-evolution.txt" http://launchpadlibrarian.net/26475026/gdb-evolution.txt -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug notification because you are a member of Ubuntu Desktop Bugs,

RE: [Bug 366471] Re: Calendar closed unexpectedly

Well, you're over my head. Glad to help if you or someone can give me a step-by-step procedure. -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Sebastien Bacher Sent: Friday, May 08, 2009 11:49 AM To: Ken Watson (kwatson) Subject: [Bug 366471] R

[Bug 366471] Re: Calendar closed unexpectedly

Here's a strace file for the version that does not have the problem. Again, I apologize for the size (3.9 MB). ** Attachment added: "strace-evolution-mint7.log" http://launchpadlibrarian.net/26470927/strace-evolution-mint7.log -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/36

[Bug 366471] Re: Calendar closed unexpectedly

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. ** Attachment added: "strace-evolution.log" http://launchpadlibrarian.net/26470213/strace-evolution.log -- Cal

RE: [Bug 366471] Re: Calendar closed unexpectedly

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-exc

RE: [Bug 366471] Re: Calendar closed unexpectedly

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 Developer

[Bug 366471] Re: Calendar closed unexpectedly

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. -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 Yo

RE: [Bug 366471] Re: Calendar closed unexpectedly

(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 Evolut

RE: [Bug 366471] Re: Calendar 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 rema

RE: [Bug 366471] Re: Calendar closed unexpectedly

Kib Reed's patch appears to be for an amd64 installation. Will it also work on my x86 32-bit installation? -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Sebastien Bacher Sent: Wednesday, April 29, 2009 5:24 AM To: Ken Watson (kwatson) Subject:

Re: [Bug 366471] Re: Calendar closed unexpectedly

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 +, Sebastien Bacher wrote: > the screenshot clearly indicates that e-d-s is crashing though > > could you also stop quoting a ton of extra lines a

RE: [Bug 366471] Re: Calendar closed unexpectedly

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

RE: [Bug 366471] Re: Calendar closed unexpectedly

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: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Sebas

[Bug 366471] Re: Calendar closed unexpectedly

Attaching a more thorough capture. ** Attachment added: "e-d-s-gdb-backtrace.txt" http://launchpadlibrarian.net/26037194/e-d-s-gdb-backtrace.txt -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug notification because you are a member of Ubuntu Desktop

[Bug 366471] Re: Calendar closed unexpectedly

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

[Bug 366471] Re: Calendar closed unexpectedly

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=

[Bug 366471] Re: Calendar closed unexpectedly

I've tried to get a stacktrace but it isn't working. Here's the result: ubu...@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 This is free software

[Bug 366471] Re: Calendar closed unexpectedly

This one may have better data. I was able to run it with the pid. ** Attachment added: "strace-evolution.log" http://launchpadlibrarian.net/26012368/strace-evolution.log -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug notification because you are

[Bug 366471] Re: Calendar closed unexpectedly

Here's the stacktrace log that was produced. Probably not of any value. ** Attachment added: "strace-evolution-data-server.log" http://launchpadlibrarian.net/26011831/strace-evolution-data-server.log -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug

[Bug 367641] Re: calendar quit unexpectedly

** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/26011811/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/26011812/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/26011813/ProcStatus.txt -- calend

[Bug 367641] [NEW] calendar quit unexpectedly

Public bug reported: Binary package hint: evolution I reported this as bug # 366471, but can't successfully execute a backtrace or stacktrace on evolution-data-server, which I believe is the component that is crashing. Attaching the debug file here. 1) Ubuntu 9.04 Jaunty Jackalope 2) evolution-

[Bug 366471] Re: Calendar closed unexpectedly

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 t

[Bug 366471] Re: Calendar closed unexpectedly

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.

[Bug 366471] Re: Calendar closed unexpectedly

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. -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You r

[Bug 366471] Re: Calendar closed unexpectedly

Done. Here's the second backtrace. ** Attachment added: "gdb-evolution.txt" http://launchpadlibrarian.net/25974288/gdb-evolution.txt -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug notification because you are a member of Ubuntu Desktop Bugs, whic

[Bug 366471] Re: Calendar closed unexpectedly

** Attachment added: "gdb backtrace" http://launchpadlibrarian.net/25971296/gdb-evolution.txt -- Calendar closed unexpectedly https://bugs.launchpad.net/bugs/366471 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs m

[Bug 366471] [NEW] Calendar closed unexpectedly

Public bug reported: 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