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 534053 - crash in Evolution Mail and Calendar:
crash in Evolution Mail and Calendar:
Status: RESOLVED DUPLICATE of bug 512605
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-20 14:15 UTC by manuel.garciaext
Modified: 2008-05-21 04:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description manuel.garciaext 2008-05-20 14:15:43 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.16-2-686-smp #1 SMP Fri Aug 18 19:25:21 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 90030080 vsize: 90030080 resident: 25718784 share: 9273344 rss: 25718784 rss_rlim: 4294967295
CPU usage: start_time: 1211291660 rtime: 198 utime: 180 stime: 18 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)
[Thread debugging using libthread_db enabled]
[New Thread 0xa66c59a0 (LWP 11626)]
[New Thread 0xa6227b90 (LWP 11628)]
0xa7040f91 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xa66c59a0 (LWP 11626))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 __assert_fail
    from /lib/libc.so.6
  • #8 ber_flush2
    from /usr/lib/liblber-2.4.so.2
  • #9 ldap_int_flush_request
    from /usr/lib/libldap_r-2.4.so.2
  • #10 ldap_send_server_request
    from /usr/lib/libldap_r-2.4.so.2
  • #11 ldap_send_initial_request
    from /usr/lib/libldap_r-2.4.so.2
  • #12 ldap_ntlm_bind
    from /usr/lib/libldap_r-2.4.so.2
  • #13 ??
    from /usr/lib/libexchange-storage-1.2.so.3
  • #14 ??
  • #15 ??
    from /usr/lib/libexchange-storage-1.2.so.3
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (21667 sec old) ---------------------
** (nm-applet:4113): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4113): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4113): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4113): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4113): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-05-21 04:09:58 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 ***