Bug 471250 – crash in Evolution Mail: Hi, Evolution keeps cra...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 471250 - crash in Evolution Mail: Hi, Evolution keeps cra...


Summary:	crash in Evolution Mail: Hi, Evolution keeps cra...


Status:	RESOLVED DUPLICATE of bug 470817

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-28 18:36 UTC by Julien Valroff
Modified:	2007-08-29 18:52 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Julien Valroff 2007-08-28 18:36:42 UTC

What were you doing when the application crashed?
Hi,

Evolution keeps crashing on startup or after deleting an e-mail. It also sometimes crashes when changing the active folder.

I have tried deleting ~/.evolution folder without effect.

I wasn't able to identify a recent upgrade which could have caused this.

Cheers,
Julien


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 418443264 vsize: 418443264 resident: 30621696 share: 17629184 rss: 30621696 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188326135 rtime: 69 utime: 59 stime: 10 cutime:2 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47460850227296 (LWP 7240)]
[New Thread 1124096336 (LWP 7264)]
[New Thread 1115703632 (LWP 7263)]
[New Thread 1107310928 (LWP 7261)]
[New Thread 1098918224 (LWP 7260)]
[New Thread 1090525520 (LWP 7259)]
[New Thread 1082132816 (LWP 7257)]
0x00002b2a4f5d6c7f in waitpid () from /lib/libpthread.so.0

+ Trace 158619

Thread 1 (Thread 47460850227296 (LWP 7240))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#2 <signal handler called>
#3 __xmlParserInputBufferCreateFilename
at xmlIO.c line 2408
#4 xmlNewInputFromFile__internal_alias
at parserInternals.c line 1450
#5 xmlCreateURLParserCtxt__internal_alias
at parser.c line 12263
#6 xmlSAXParseFileWithData__internal_alias
at parser.c line 12323
#7 e_tree_table_adapter_load_expanded_state
at e-tree-table-adapter.c line 951
#8 message_list_set_folder
at message-list.c line 1729
#9 emfv_set_folder
at em-folder-view.c line 661
#10 emfb_set_folder
at em-folder-browser.c line 1842
#11 mail_msgport_replied
at mail-mt.c line 473
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#15 bonobo_main
from /usr/lib/libbonobo-2.so.0
#16 main
at main.c line 611
#0 waitpid
from /lib/libpthread.so.0

Comment 1 noel 2007-08-28 19:05:53 UTC

You are running Debian sid?

Please tell me which version of libxml2 you are using? 2.6.29.dfsg-1 or
2.6.30.dfsg-1

Comment 2 Julien Valroff 2007-08-29 15:44:38 UTC

Hi,

I have libxml2 2.6.30.dfsg-1 installed. I have this version on an another machine (i386), and have no problem on it.

Cheers,
Julien

Comment 3 noel 2007-08-29 18:46:22 UTC

ok. You have to downgrade to 2.6.29.dfsg-1 to fix the crashes. Or you wait for the new version 2.6.30.dfsg-2 which should fix the problem.

There is a Debian bug report at http://bugs.debian.org/439843 which pointed me
to the problem.
Downgrading fixed it for me.

I dont have the needed right to do it in bugzilla but this is a dupe of 470817
if the libxml downgrade fix your problem.

Comment 4 Julien Valroff 2007-08-29 18:49:56 UTC

Hi,

It seems indeed that downgrading libxml2 does fix this issue.

Thanks for your help!

Cheers,
Julien

*** This bug has been marked as a duplicate of 470817 ***

Comment 5 Julien Valroff 2007-08-29 18:52:06 UTC

I noticed in the meantime that all the bug reports seems to be on x86_64 systems, which explains why I do not suffer from the issue on my i386 laptop.

Cheers,
Julien