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 621162 - crash in Evolution: Doing a send and receive...
crash in Evolution: Doing a send and receive...
Status: RESOLVED DUPLICATE of bug 528022
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-10 02:31 UTC by trlinde
Modified: 2010-06-10 03:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description trlinde 2010-06-10 02:31:58 UTC
What were you doing when the application crashed?
Doing a send and received on exchange email.
Last time I had issues all debug files were installed and no info was showing in the bug check. I uninstalled evolution and it worked till now.


Distribution: openSUSE 11.2 (x86_64)
Gnome Release: 2.28.2 (null) (SUSE)
BugBuddy Version: 2.28.0

System: Linux 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Sonar
Icon Theme: Gilouche
GTK+ Modules: canberra-gtk-module, gnomebreakpad, gail:atk-bridge

Memory status: size: 1110745088 vsize: 1110745088 resident: 252067840 share: 31203328 rss: 252067840 rss_rlim: 18446744073709551615
CPU usage: start_time: 1276118295 rtime: 10867 utime: 9767 stime: 1100 cutime:2 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fd37c90f910 (LWP 16170)]
[New Thread 0x7fd38e6bd910 (LWP 16169)]
[New Thread 0x7fd381a98910 (LWP 11674)]
[New Thread 0x7fd37d7a2910 (LWP 11673)]
[New Thread 0x7fd38f6bf910 (LWP 6157)]
[New Thread 0x7fd3828bf910 (LWP 5809)]
[New Thread 0x7fd38eebe910 (LWP 5797)]
[New Thread 0x7fd38fec0910 (LWP 5794)]
[New Thread 0x7fd390ec2910 (LWP 5792)]
[New Thread 0x7fd3916c3910 (LWP 5791)]
[New Thread 0x7fd392c70910 (LWP 5789)]
[New Thread 0x7fd396c16910 (LWP 5788)]
0x00007fd3ad80374d in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 0x7fd37c90f910 (LWP 16170))

  • #0 __lll_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_lock_941
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 <signal handler called>
  • #4 exchange_get_folder_info
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #5 camel_store_get_folder_info
    from /usr/lib64/libcamel-provider-1.2.so.14
  • #6 get_folderinfo_exec
    from /usr/lib64/evolution/2.28/libevolution-mail-shared.so.0
  • #7 mail_msg_proxy
    from /usr/lib64/evolution/2.28/libevolution-mail-shared.so.0
  • #8 ??
    from /usr/lib64/libglib-2.0.so.0
  • #9 ??
    from /usr/lib64/libglib-2.0.so.0
  • #10 start_thread
    from /lib64/libpthread.so.0
  • #11 clone
    from /lib64/libc.so.6
  • #12 ??
A debugging session is active.

	Inferior 1 [process 5759] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (420 sec old) ---------------------
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
(Pidgin:5001): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2010-06-10 03:44:09 UTC
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 bug 528022 ***