Bug 524439 – crash in Evolution Mail: selecting evolution whic...

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 524439 - crash in Evolution Mail: selecting evolution whic...


Summary:	crash in Evolution Mail: selecting evolution whic...


Status:	RESOLVED DUPLICATE of bug 324168

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.12.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-26 05:28 UTC by bugreports
Modified:	2008-06-16 22:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description bugreports 2008-03-26 05:28:00 UTC

What were you doing when the application crashed?
selecting evolution which was just receiving email


Distribution: Debian 3.1 (sarge)
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-rc6-sonne #19 SMP PREEMPT Tue Mar 25 08:07:27 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 145940480 vsize: 145940480 resident: 31055872 share: 17412096 rss: 31055872 rss_rlim: 4294967295
CPU usage: start_time: 1206509208 rtime: 184 utime: 160 stime: 24 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb689c740 (LWP 4050)]
[New Thread 0xb109eb90 (LWP 4463)]
[New Thread 0xb18ffb90 (LWP 4386)]
[New Thread 0xb2a1ab90 (LWP 4385)]
[New Thread 0xb2219b90 (LWP 4374)]
[New Thread 0xb321fb90 (LWP 4322)]
[New Thread 0xb3a2fb90 (LWP 4289)]
[New Thread 0xb42ffb90 (LWP 4259)]
[New Thread 0xb4c47b90 (LWP 4246)]
[New Thread 0xb5448b90 (LWP 4222)]
0xb80db424 in __kernel_vsyscall ()

+ Trace 193350

Thread 1 (Thread 0xb689c740 (LWP 4050))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 segv_redirect
at main.c line 413
#6 <signal handler called>
#7 camel_message_info_free
at camel-folder-summary.c line 2793
#8 free_message_info
at camel-folder.c line 975
#9 camel_folder_free_message_info
at camel-folder.c line 993
#10 clear_info
at message-list.c line 2363
#11 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#12 clear_tree
at message-list.c line 2382
#13 regen_list_regened
at message-list.c line 2873
#14 mail_msgport_replied
at mail-mt.c line 473
#15 ??
from /usr/lib/libglib-2.0.so.0
#16 ??
#17 ??
#18 ??
#19 ??
from /usr/lib/libglib-2.0.so.0
#20 ??
#21 ??
#22 ??
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (17 sec old) ---------------------
** (nm-applet:3188): WARNING **: <WARN>  hal_net_physdev_cb(): dbus returned an error.
  (org.freedesktop.Hal.NoSuchProperty) No property net.physical_device on device with id /org/freedesktop/Hal/devices/net_00_16_cb_9b_35_cc
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
** Message: failed to load session from /home/sonne/.nautilus/savedkUy9j4
** (galeon:4065): CRITICAL **: radio_group_set_from_value: assertion `action != NULL' failed
get sonne imap://sonne@mail.nn7.de/
Find Items 0
get newsgate imap://newsgate@mail.nn7.de/
Find Items 0
(evolution:4050): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/sonne/.maildir-fortknox-matches/.#evolution': not a maildir directory.
--------------------------------------------------

Comment 1 André Klapper 2008-04-10 08:14:24 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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