evolution crashed

Bug #195616 reported by Pete Simanyi
6
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: evolution

cat /etc/lsb-release:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

dpkg -l evolution:
||/ Name Version Description
+++-==============-==============-============================================
ii evolution 2.21.91-0ubunt groupware suite with mail client and organiz

Evolution crashes upon startup with a popup dialog entitled "Evolution Drash Detection",
"Evolution appears to have exited unexpectedly the last time it was run.
As a precautionary measure, all preview panes will be hidden. You can restore
the preview panes from the View menu."

-----
Below is the gdb stacktrace from the crash, starting gdb using:
   gdb `which evolution`
(and `which evolution` returns /usr/bin/evolution):

[Thread 0xb5b79b90 (LWP 9223) exited]
[New Thread 0xb5b79b90 (LWP 9227)]
[New Thread 0xb536fb90 (LWP 9228)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb5b79b90 (LWP 9227)]
0xb7bc9013 in camel_partition_table_lookup () from /usr/lib/libcamel-1.2.so.11
(gdb) bt
#0 0xb7bc9013 in camel_partition_table_lookup ()
   from /usr/lib/libcamel-1.2.so.11
#1 0xb7bd007a in ?? () from /usr/lib/libcamel-1.2.so.11
#2 0xb4702c00 in ?? ()
#3 0xb4700988 in ?? ()
#4 0xb7bc5ecb in camel_object_is () from /usr/lib/libcamel-1.2.so.11
#5 0xb7bab786 in camel_index_has_name () from /usr/lib/libcamel-1.2.so.11
#6 0xb5b903c9 in ?? ()
   from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#7 0xb4702a20 in ?? ()
#8 0xb4700988 in ?? ()
#9 0x0837e190 in ?? ()
#10 0x0000240b in ?? ()
#11 0x080da448 in ?? ()
#12 0x00000000 in ?? ()
(gdb)

Revision history for this message
David Mills (d-mills) wrote :

Hello, and thank you for your feedback.

We can't use the stack trace as it stands to resolve your problem.

Could you please install evolution-dbg, which contains added symbols to help us track down this bug and try opening evolution again?

Thank you

Changed in evolution:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in evolution:
status: Incomplete → Invalid
Revision history for this message
Pete Simanyi (pdsimanyi) wrote :

(1) Pedro: running evolution now does not generate a new crash file in /var/crash (which
may be a separate bug). The old crash from a day ago or so does not contain debug
symbols. Do I have to invoke /usr/bin/evolution with a wrapper script or something
to get it to generate a /var/crash log?

(2) David: I installed evolution-dbg, however the stack from 'gdb /usr/bin/evolution' still has no useful
symbols. The evolution-dbg package contains this file
/usr/lib/debug/usr/bin/evolution
that appears like it may be a debug version
of evolution, but gdb on this still does not produce any useful info:

fcdevldev01:/var/crash> ls -l /usr/lib/debug/usr/bin/evolution
-rw-r--r-- 1 root root 402499 2008-02-25 19:16 /usr/lib/debug/usr/bin/evolution
fcdevldev01:/var/crash> file !$
file /usr/lib/debug/usr/bin/evolution
/usr/lib/debug/usr/bin/evolution: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped

gdb /usr/lib/debug/usr/bin/evolution
GNU gdb 6.7.1-debian
Copyright (C) 2007 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"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) r
Starting program: /usr/lib/debug/usr/bin/evolution
/usr/lib/debug/usr/bin/evolution: Permission denied.

Program exited with code 01.
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
You can't do that without a process to debug.
(gdb) bt
No stack.
(gdb)

---
(3) Given (1) and (2), I am stuck without any obvious way to generate a meaningful
crash, and for some reason the /var/crash generator is not generating crash
logs for evolution. Any advice is greatly appreciated!

Revision history for this message
Pete Simanyi (pdsimanyi) wrote :

I know C/C++ and (non-debian) linux reasonably well, and if evolution
can be recompiled on my machine with a few "apt-get"'s and make,
I'd be happy to do so if you can provide directions. If this is complex
to explain how to do, never mind.

The question is: how simple are the commands necessary to obtain and compile the source
packages for 8.04's evolution or for the entire GNOME set of
binaries/libraries?

Revision history for this message
David Mills (d-mills) wrote :

Pete,

could you ' chmod a+x /usr/lib/debug/usr/bin/evolution' and try running the debug-version of evolution again?

Thanks

Revision history for this message
Sebastien Bacher (seb128) wrote :

the debug version is not a binary meant to be run but symbols gdb is using automatically when they are installed

Revision history for this message
rbmorse (rbmorse) wrote :

I can confirm this behavior. From the messages log (four representative examples):

Feb 28 09:04:22 hardy kernel: [ 8842.581845] evolution[7212]: segfault at 00000000 eip b6dfba60 esp bffd07a0
error 4

Feb 28 21:54:39 hardy kernel: [54988.496359] evolution[10295]: segfault at 00000000 eip b6d24a60 esp bffbd780 error 4

Feb 29 15:20:42 hardy kernel: [ 2957.712314] evolution[6674]: segfault at 00000000 eip b6df6a60 esp bff41710 error 4

Feb 29 16:31:08 hardy kernel: [ 7177.661838] evolution[8222]: segfault at 00000000 eip b6dd4a60 esp bfecfea0 error 4

I also notice that Nautilus is also experiencing error 4 (two representative examples):

Feb 28 21:43:39 hardy kernel: [54329.425327] nautilus[7115]: segfault at aaaaaaaa eip 0808744b esp bfa931e0 error 4
Feb 28 21:54:26 hardy kernel: [54975.648355] nautilus[10235]: segfault at aaaaaaaa eip 0808744b esp bfb79ac0 error 4

Revision history for this message
Matt Davey (mcdavey) wrote :

I've been getting similar crashes from evolution. It tends to happen soon after sending a mail. I guess it is rebuilding indexes of my sent folder. Note that I use the 'mh' backend, but I doubt that is the cause.
packages:
   evolution 2.22.1-0ubuntu3.1
   evolution-dbg 2.22.1-0ubuntu3.1
   evolution-data-server 2.22.1-0ubuntu2.1

mcdavey 536 /var/crash> cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04"

I am not getting /var/crash or bug-buddy support, but have run evolution inside gdb and get this:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xaf0ffb90 (LWP 3066)]
camel_partition_table_lookup (cpi=0x8ba5810, key=0xaff0a6c4 "chance") at camel-partition-table.c:302
302 camel-partition-table.c: No such file or directory.
 in camel-partition-table.c
(gdb) bt
#0 camel_partition_table_lookup (cpi=0x8ba5810, key=0xaff0a6c4 "chance") at camel-partition-table.c:302
#1 0xb7b064d8 in hash_write_word (word=0xaff0a6c4 "chance", data=0xaff0a6c4, idn=0x97ad0f0) at camel-text-index.c:183
#2 0xb6d0e633 in g_hash_table_foreach () from /usr/lib/libglib-2.0.so.0
#3 0xb7b06296 in text_index_write_name (idx=0x8ba3190, idn=0x97ad0f0) at camel-text-index.c:649
#4 0xb7ae18b4 in camel_index_write_name (idx=0x8ba3190, idn=0x97ad0f0) at camel-index.c:209
#5 0xb7d2285a in camel_folder_summary_info_new_from_message (s=0x89dfc20, msg=0xb25c9090) at camel-folder-summary.c:1105
#6 0xb7d231ac in camel_folder_summary_add_from_message (s=0x89dfc20, msg=0xb25c9090) at camel-folder-summary.c:965
#7 0xb54c0646 in local_summary_add (cls=0x89dfc20, msg=0xb25c9090, info=0x9577e28, ci=0x866e6b0, ex=0xaf0ff26c)
    at camel-local-summary.c:429
#8 0xb54bff71 in camel_local_summary_add (cls=0x89dfc20, msg=0xb25c9090, info=0x9577e28, ci=0x866e6b0, ex=0xaf0ff26c)
    at camel-local-summary.c:303
#9 0xb54c68fe in mh_append_message (folder=0x89c5628, message=0xb25c9090, info=0x9577e28, appended_uid=0x0, ex=0xaf0ff26c)
    at camel-mh-folder.c:138
#10 0xb7d27eea in camel_folder_append_message (folder=0x89c5628, message=0xb25c9090, info=0x9577e28, appended_uid=0x0, ex=0xaf0ff26c)
    at camel-folder.c:651
#11 0xb6386aef in send_queue_exec (m=0xaeef8a0) at mail-ops.c:586
#12 0xb6382719 in mail_msg_proxy (msg=0xaeef8a0) at mail-mt.c:523
#13 0xb6d4569b in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x0aeef8a0 in ?? ()
#15 0x00000000 in ?? ()

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.