Evolution (etch) killed by dist-upgrade

Kirmonkey · 04-03-2006, 10:00 AM

Evening,

I am currently running Debian Etch and got round to running an upgrade yesterday.

The following packages were installed:

Quote:

cpp-3.3 (1:3.3.6-10) to 1:3.3.6-13
dbus (0.61-4) to 0.61-5
debconf (1.4.71) to 1.4.72
debconf-i18n (1.4.71) to 1.4.72
debhelper (5.0.24) to 5.0.26
dpkg (1.13.16) to 1.13.17
dpkg-dev (1.13.16) to 1.13.17
dselect (1.13.16) to 1.13.17
file (4.15-2) to 4.17-1
g++-3.3 (1:3.3.6-10) to 1:3.3.6-13
gcc-3.3 (1:3.3.6-10) to 1:3.3.6-13
gcc-3.3-base (1:3.3.6-10) to 1:3.3.6-13
gconf2 (2.12.1-12) to 2.14.0-1
gconf2-common (2.12.1-12) to 2.14.0-1
gnome-keyring (0.4.8-1) to 0.4.9-1
gstreamer0.10-alsa (0.10.3-1) to 0.10.5-1
gstreamer0.10-gnomevfs (0.10.3-1) to 0.10.5-1
gstreamer0.10-plugins-base (0.10.3-1) to 0.10.5-1
initscripts (2.86.ds1-12) to 2.86.ds1-13
intltool-debian (0.34.1+20050828) to 0.34.1+20060220
libbonobo2-0 (2.10.1-1) to 2.14.0-1
libbonobo2-common (2.10.1-1) to 2.14.0-1
libdbus-1-2 (0.61-4) to 0.61-5
libdbus-glib-1-2 (0.61-4) to 0.61-5
libexo-0.3-0 (0.3.1.2alpha-r19548-2) to 0.3.1.4alpha2-r20235-1
libgail-common (1.8.10-1) to 1.8.11-1
libgail17 (1.8.10-1) to 1.8.11-1
libgconf2-4 (2.12.1-12) to 2.14.0-1
libgdome2-cpp-smart0c2a (0.2.3-5) to 0.2.3-6
libglib2.0-0 (2.8.6-1) to 2.10.1-2
libgnome-keyring0 (0.4.8-1) to 0.4.9-1
libgnomecanvas2-0 (2.12.0-2) to 2.14.0-1
libgnomecanvas2-common (2.12.0-2) to 2.14.0-1
libgpod0 (0.3.0-3) to 0.3.0-4
libgstreamer-plugins-base0.10-0 (0.10.3-1) to 0.10.5-1
libidl0 (0.8.5-1) to 0.8.6-1
libmagic1 (4.15-2) to 4.17-1
libnfsidmap1 (0.8-1) to 0.13-1
liborbit2 (1:2.12.4-1) to 1:2.14.0-1
libpango1.0-0 (1.10.4-1) to 1.12.0-2
libpango1.0-common (1.10.4-1) to 1.12.0-2
libpaper1 (1.1.14-5) to 1.1.14-6
libpisock8 (0.11.8-20) to 0.11.8-21
libpisync0 (0.11.8-20) to 0.11.8-21
libsndfile1 (1.0.12-3) to 1.0.15-1
libstdc++5 (1:3.3.6-10) to 1:3.3.6-13
libstdc++5-3.3-dev (1:3.3.6-10) to 1:3.3.6-13
libvte-common (1:0.11.20-1) to 1:0.11.20-3
libvte4 (1:0.11.20-1) to 1:0.11.20-3
libxml2 (2.6.23.dfsg.2-2) to 2.6.23.dfsg.2-3
libxml2-utils (2.6.23.dfsg.2-2) to 2.6.23.dfsg.2-3
libxslt1.1 (1.1.15-4) to 1.1.15-5
make (3.80+3.81.rc1-1) to 3.80+3.81.rc2-1
netbase (4.24) to 4.25
po-debconf (0.9.2) to 1.0
portmap (5-17) to 5-18
psmisc (22.1-1) to 22.2-1
python-libxml2 (2.6.23.dfsg.2-2) to 2.6.23.dfsg.2-3
python2.3-libxml2 (2.6.23.dfsg.2-2) to 2.6.23.dfsg.2-3
sysv-rc (2.86.ds1-12) to 2.86.ds1-13
sysvinit (2.86.ds1-12) to 2.86.ds1-13
tar (1.15.1-4) to 1.15.1-6
udev (0.085-1) to 0.087-2
xsltproc (1.1.15-4) to 1.1.15-5
xterm (208-3.1) to 210-2

I was a little wary of so many packages being there but went ahead. This has hosed my evolution package. I have posted gdb debubbing info and would be terribly grateful if someone could take a look at it and offer any suggestions.

Code:

rick@trevor:~$ gdb evolution
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/evolution
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230481728 (LWP 10903)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
adding hook target 'source'
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

(evolution:10903): camel-WARNING **: camel_exception_get_id called with NULL parameter.
[New Thread -1236751440 (LWP 10912)]
[New Thread -1245140048 (LWP 10913)]
[New Thread -1253528656 (LWP 10914)]
[New Thread -1262310480 (LWP 10915)]
[New Thread -1270699088 (LWP 10916)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread -1262310480 (LWP 10915) exited]
[Thread -1253528656 (LWP 10914) exited]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)

(evolution:10903): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed
[New Thread -1253528656 (LWP 10922)]
[New Thread -1262310480 (LWP 10923)]
(no debugging symbols found)
*** glibc detected *** double free or corruption (out): 0x085afe48 ***

Program received signal SIGABRT, Aborted.
[Switching to Thread -1230481728 (LWP 10903)]
0xb6b437c7 in raise () from /lib/tls/libc.so.6
(gdb)

Oops

Must try harder.

Help appreciated...(.)

jonaskoelker · 04-04-2006, 02:34 AM

a 'double free or corruption' is (with 99% prob.) a bug, most likely in evolution. I suggest you talk to the evolution devs. Also, as the output says, "(no debugging symbols found)". Such a log is practically useless in determining the problem, so be sure to run a version *with* debugging symbols; this probably means compiling yourself, but apt-get (source|build-dep) should be helpful. If it doesn't compile cleanly, you have probably found a debian bug; you might get help in #debian in determining whether that is really the case, and get some advice on how to report it (I fire up emacs, then `M-x debian-bug').

hth --Jonas

Kirmonkey · 04-08-2006, 12:03 AM

There is a solution here:

It gets things going again.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347672