Bug 435190 – crash in Evolution:

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 435190 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 435124

Product:	evolution
Classification:	Applications
Component:	general
Version:	unspecified
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-05-02 14:00 UTC by renatogallo
Modified:	2007-05-15 09:20 UTC

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

Description renatogallo 2007-05-02 14:00:42 UTC

Version: 2.12.x

What were you doing when the application crashed?



Distribution: Slackware Slackware 11.1.0
Gnome Release: 2.18.1 2007-04-30 (GARNOME)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-rc7 #2 SMP Wed Apr 18 17:46:42 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 110297088 vsize: 110297088 resident: 27107328 share: 16859136 rss: 27107328 rss_rlim: 4294967295
CPU usage: start_time: 1178114371 rtime: 158 utime: 149 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1234536768 (LWP 7932)]
[New Thread -1310192752 (LWP 7958)]
[New Thread -1301382256 (LWP 7956)]
[New Thread -1265632368 (LWP 7943)]
[New Thread -1282409584 (LWP 7942)]
[New Thread -1290798192 (LWP 7941)]
[New Thread -1274020976 (LWP 7938)]
[New Thread -1255490672 (LWP 7936)]
0xb6a31ad1 in ?? () from /lib/libpthread.so.0

+ Trace 131889

Thread 8 (Thread -1255490672 (LWP 7936))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 _L_mutex_lock_88
from /lib/libpthread.so.0
#2 pthread_mutex_lock
from /lib/libpthread.so.0
#3 <signal handler called>
#4 camel_index_add_name
at camel-index.c line 183
#5 camel_folder_summary_info_new_from_parser
at camel-folder-summary.c line 1026
#6 camel_folder_summary_add_from_parser
at camel-folder-summary.c line 931
#7 summary_update
at camel-mbox-summary.c line 485
#8 mbox_summary_check
at camel-mbox-summary.c line 572
#9 camel_local_summary_check
at camel-local-summary.c line 268
#10 mbox_append_message
at camel-mbox-folder.c line 203
#11 camel_folder_append_message
at camel-folder.c line 648
#12 camel_filter_driver_filter_message
at camel-filter-driver.c line 1511
#13 camel_filter_driver_filter_folder
at camel-filter-driver.c line 1279
#14 em_filter_folder_element_filter
at mail-ops.c line 140
#15 fetch_mail_fetch
at mail-ops.c line 325
#16 mail_msg_received
at mail-mt.c line 582
#17 thread_dispatch
at e-msgport.c line 1005
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6



----------- .xsession-errors ---------------------
kbluetoothd: DeviceNameCache::slotInquiryResult
kbluetoothd: HCI-event: 22
kbluetoothd: DeviceNameCache::slotInquiryResult
kbluetoothd: HCI-event: 1
kbluetoothd: NeighbourMonitor: end of inquiry detected
kbluetoothd: HciSocket::open()
kbluetoothd: NeighbourMonitor::processQueue
Invalid entry (missing '=') at /root/Desktop/gnome-terminal.desktop:1
CalDAV Eplugin starting up ...
** (evolution-2.12:7932): DEBUG: mailto URL command: evolution %s
** (evolution-2.12:7932): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Cannot access memory at address 0xb
Cannot access memory at address 0xb
--------------------------------------------------

Comment 1 palfrey 2007-05-03 12:29:01 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 Akhil Laddha 2007-05-15 06:58:37 UTC

Hi Tom,
        This is dup of Bug 435124.

Comment 3 palfrey 2007-05-15 09:20:14 UTC

(In reply to comment #2)
> Hi Tom,
>         This is dup of Bug 435124. 

If you think it's a dupe, then please mark it as such. I won't mind!

Reporter, thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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