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 561156 - crash in update_update at camel-groupwise-folder.c line 2070
crash in update_update at camel-groupwise-folder.c line 2070
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[groupwise]
: 561157 561163 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-11-17 06:28 UTC by jorschiedt
Modified: 2010-09-30 03:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
gdb "bt full" after coredump (39.11 KB, text/plain)
2008-11-27 10:34 UTC, jorschiedt
Details
attachement for #6 (5.65 KB, text/plain)
2008-11-27 13:03 UTC, jorschiedt
Details

Description jorschiedt 2008-11-17 06:28:10 UTC
Version: 2.26.x

What were you doing when the application crashed?
start evolution after "evolution --force-shutdown"


Distribution: openSUSE 11.0 (X86-64)
Gnome Release: 2.25.1 2008-11-09 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.18-0.2-default #1 SMP 2008-10-21 16:30:26 +0200 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: iTunes-gekos-0.2
Icon Theme: glass-icons

Memory status: size: 627978240 vsize: 627978240 resident: 32645120 share: 25534464 rss: 58179584 rss_rlim: 2910443520
CPU usage: start_time: 1226903197 rtime: 825 utime: 704 stime: 121 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f9b12b65760 (LWP 32597)]
[New Thread 0x42e12950 (LWP 32742)]
[New Thread 0x41aa7950 (LWP 32725)]
0x00007f9b0889964f in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 0x42e12950 (LWP 32742))

  • #0 __lll_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_lock_102
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 <signal handler called>
  • #4 update_update
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelgroupwise.so
  • #5 session_thread_proxy
    from /usr/lib64/libcamel-provider-1.2.so.13
  • #6 g_thread_pool_thread_proxy
    from /usr/lib64/libglib-2.0.so.0
  • #7 g_thread_create_proxy
    from /usr/lib64/libglib-2.0.so.0
  • #8 start_thread
    from /lib64/libpthread.so.0
  • #9 clone
    from /lib64/libc.so.6


----------- .xsession-errors (28413 sec old) ---------------------
(firefox31:9694): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Java process: caught exception from sun.plugin.navig.motif.Plugin.start
Exception in thread "main" Allocating more space for read msg 754
** Message: <info>  New secrets for Auto Noodle/802-11-wireless-security requested; ask the user
** (nm-applet:4040): WARNING **: nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/2: Method "Get" with signature "ss" on interface "org.freedesktop.DB
** (nm-applet:4040): WARNING **: nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/2: Method "Get" with signature "ss" on interface "org.freedesktop.DB
** (nm-applet:4040): WARNING **: applet-device-wireless.c.1299 (get_secrets_dialog_response_cb): canceled
--------------------------------------------------
Comment 1 Kandepu Prasad 2008-11-17 06:45:54 UTC
*** Bug 561157 has been marked as a duplicate of this bug. ***
Comment 2 Kandepu Prasad 2008-11-17 06:46:43 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing some debugging packages [1],
start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] Please install debug packages for evolution, evolution-data-server,
gtkhtml, gtk, glib, glibc, orbit2, gnome-vfs, pango, libgnome and libgnomeui 
(as far as those packages are provided by your distribution).

More details can be found here: http://live.gnome.org/GettingTraces
Comment 3 Kandepu Prasad 2008-11-17 08:10:08 UTC
*** Bug 561163 has been marked as a duplicate of this bug. ***
Comment 4 jorschiedt 2008-11-27 10:32:08 UTC
The current build (evolution-data-server-2.25.20081127-1.1) is much more stable than the verison I reported.
However, it doesn't work without core dumps.

Here's the latest I got this morning:

jorschiedt@lowrider:~> gdb evolution
GNU gdb 6.8
Copyright (C) 2008 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 "x86_64-suse-linux"...
(gdb) core-file core.26863
<cut reading of symbols>
Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.
[New process 26863]
[New process 27139]
[New process 27134]
[New process 27121]
[New process 26986]
[New process 26950]
  • #0 e_iterator_reset
    at e-iterator.c line 76

Full bt will follow as attachement...
Comment 5 jorschiedt 2008-11-27 10:34:21 UTC
Created attachment 123532 [details]
gdb "bt full" after coredump

evolution-2.25.20081127-1.1, evolution-data-server-2.25.20081127-1.1
Comment 6 jorschiedt 2008-11-27 13:03:51 UTC
Created attachment 123540 [details]
attachement for #6
Comment 7 Kandepu Prasad 2008-12-10 06:24:04 UTC
The traces in comments 5,6 does not match with the original crash. Can you reproduce and give us the traces. 

There is a similar trace in downstream bug 
https://bugzilla.novell.com/show_bug.cgi?id=448079

Program received signal SIGSEGV, Segmentation fault.

Thread 140736942160208 (LWP 1197)

  • #0 update_update
    at camel-groupwise-folder.c line 2056
  • #1 session_thread_proxy
    at camel-session.c line 592
  • #2 ??
    from /usr/lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/libglib-2.0.so.0
  • #4 start_thread
    at pthread_create.c line 297
  • #5 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #6 ??

Comment 8 jorschiedt 2008-12-12 10:08:19 UTC
So, which of the 56 coredumps I got the last two days is the one you like to see?

Pattern is always the same - fire evolution and see it dying without any user action. So how shall I select the "right" coredump?
Comment 9 ben selinger 2008-12-17 22:32:16 UTC
I've got the same problem.  Evolution crashes usually about 5 - 10 seconds after startup.
I connect to groupwise mail and address book.  No user interaction required, although right clicking on the left sidebar, causes an immediate seg-fault.
Comment 10 Kandepu Prasad 2009-01-21 11:18:45 UTC
I got this with the latest updated trunk
Evolution revision: 37112
Evolution-data-server revision: 9957


(evolution:15957): camel-WARNING **: Trying to check junk data is OBJECT 'CamelFolder'

(evolution:15957): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed

(evolution:15957): camel-CRITICAL **: camel_folder_thaw: assertion `CAMEL_IS_FOLDER (folder)' failed
[Thread 0x7fffdddd3950 (LWP 16182) exited]

Number of items in the folder: 600 

(evolution:15957): camel-WARNING **: Trying to check junk data is OBJECT 'CamelGroupwiseFolder'

(evolution:15957): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed

(evolution:15957): camel-WARNING **: Trying to check junk data is OBJECT 'CamelFolder'

(evolution:15957): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed

(evolution:15957): camel-CRITICAL **: camel_folder_get_summary: assertion `CAMEL_IS_FOLDER (folder)' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd11b2950 (LWP 16174)]
update_update (session=<value optimized out>, msg=<value optimized out>) at camel-groupwise-folder.c:2070
2070		while (index < summary->len) {
(gdb) t a a bt

Thread 64 (Thread 0x7fffd11b2950 (LWP 16174))

  • #0 update_update
    at camel-groupwise-folder.c line 2070
  • #1 session_thread_proxy
    at camel-session.c line 597
  • #2 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #3 g_thread_create_proxy
    at gthread.c line 635
  • #4 start_thread
    at pthread_create.c line 297
  • #5 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #6 ??
(gdb) 

Comment 11 Akhil Laddha 2010-08-19 12:11:19 UTC
This bug was reported against a GNOME version that is now not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.

The current stable GNOME and Evolution version is 2.30.2
Please check if the problem you reported here still occurs with a recent version of GNOME by reporting back which exact version you tested against

Thank you for reporting this bug and we are sorry it could not be fixed for your version.
Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Comment 12 Fabio Durán Verdugo 2010-09-30 03:13:59 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!