Bug 525641 – crash in Evolution: moviendo correo

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 525641 - crash in Evolution: moviendo correo


Summary:	crash in Evolution: moviendo correo


Status:	RESOLVED DUPLICATE of bug 512605

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-04-01 20:19 UTC by Ariel
Modified:	2008-04-03 14:06 UTC

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

Description Ariel 2008-04-01 20:19:23 UTC

What were you doing when the application crashed?
moviendo correo


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 50716672 vsize: 50716672 resident: 12349440 share: 9957376 rss: 12349440 rss_rlim: 4294967295
CPU usage: start_time: 1207075468 rtime: 27 utime: 22 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb66fb740 (LWP 28938)]
[New Thread 0xb625cb90 (LWP 28940)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 193940

Thread 1 (Thread 0xb66fb740 (LWP 28938))

#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 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 __assert_fail
from /lib/i686/cmov/libc.so.6
#10 ber_flush2
from /usr/lib/liblber-2.4.so.2
#11 ldap_int_flush_request
from /usr/lib/libldap_r-2.4.so.2
#12 ldap_send_server_request
from /usr/lib/libldap_r-2.4.so.2
#13 ldap_send_initial_request
from /usr/lib/libldap_r-2.4.so.2
#14 ldap_ntlm_bind
from /usr/lib/libldap_r-2.4.so.2
#15 ??
from /usr/lib/libexchange-storage-1.2.so.3
#16 ??
#17 ??
from /usr/lib/libexchange-storage-1.2.so.3
#18 ??
#19 ??
#20 ??
#0 __kernel_vsyscall



----------- .xsession-errors (16652 sec old) ---------------------
** (nm-applet:5795): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.221" is not allowed to own the service "org.freedesktop.Netwo
** (nm-applet:5795): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.221" is not allowed to own the service "org.freedesktop.Netwo
** (nm-applet:5795): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.221" is not allowed to own the service "org.freedesktop.Netwo
** (nm-applet:5795): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.221" is not allowed to own the service "org.freedesktop.Netwo
** (nm-applet:5795): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.221" is not allowed to own the service "org.freedesktop.Netwo
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-04-03 14:06:24 UTC

Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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