[Bug 14303] Evolution crashes on startup

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Thu Sep 22 22:24:46 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14303
Ubuntu | evolution





------- Additional Comments From debzilla at ubuntu.com  2005-09-22 23:24 UTC -------
Message-ID: <f5d848060508290551e7dc8d1 at mail.gmail.com>
Date: Mon, 29 Aug 2005 08:51:44 -0400
From: David Hugh-Jones <davidhughjones at gmail.com>
To: submit at bugs.debian.org
Subject: Evolution crashes on startup

Package: evolution
Version: 2.2.2-4
Severity: grave

Evolution crashes after startup and gives the usual Gnome crash dialog.=20

This first happened after allowing evolution 2.2 to delete my old
evolution folders. Now it happens whenever I start evolution.

Here's the output from "gdb evolution" (just the ordinary binary, HTH;
I have replaced repeated "(no debugging symbols found)" with "..."):

Starting program: /usr/bin/evolution
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1073876704 (LWP 8665)]
(no debugging symbols found)
...
(no debugging symbols found)
es menu class init
(no debugging symbols found)
...
(no debugging symbols found)
adding hook target 'source'
(no debugging symbols found)
...
(no debugging symbols found)
[New Thread 1088248752 (LWP 8671)]
[New Thread 1118202800 (LWP 8673)]
[New Thread 1126595504 (LWP 8674)]
[Thread 1118202800 (LWP 8673) exited]
[New Thread 1118202800 (LWP 8675)]
[Thread 1126595504 (LWP 8674) exited]
[Thread 1118202800 (LWP 8675) exited]
---Type <return> to continue, or q <return> to quit---

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1073876704 (LWP 8665)]
0x420e517a in e_canvas_hide_tooltip () from /usr/lib/libgal-2.4.so.0
(gdb) c
Continuing.
Program exited with code 01.

cheers




-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list