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 581069 - crash in Evolution Mail and Calendar: Opened evolution
crash in Evolution Mail and Calendar: Opened evolution
Status: RESOLVED DUPLICATE of bug 523463
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: 2009-05-02 04:11 UTC by timday
Modified: 2009-05-04 04:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description timday 2009-05-02 04:11:22 UTC 
What were you doing when the application crashed?
Opened evolution



Distribution: Debian 5.0.1
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Fri Mar 13 18:08:45 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 93175808 vsize: 93175808 resident: 29945856 share: 19165184 rss: 29945856 rss_rlim: 4294967295
CPU usage: start_time: 1241237390 rtime: 337 utime: 303 stime: 34 cutime:2 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb64e16d0 (LWP 23514)]
[New Thread 0xb3908b90 (LWP 23609)]
[New Thread 0xb410ab90 (LWP 23608)]
[New Thread 0xb5277b90 (LWP 23601)]
[New Thread 0xb5ab5b90 (LWP 23564)]
0xb7f22424 in __kernel_vsyscall ()

+ Trace 215015

Thread 1 (Thread 0xb64e16d0 (LWP 23514))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 segv_redirect
    at main.c line 519
  • #7 <signal handler called>
  • #8 IA__g_main_context_check
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2491
  • #9 g_main_context_iterate
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2642
  • #10 IA__g_main_loop_run
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2853
  • #11 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #12 main
    at main.c line 793
  • #0 __kernel_vsyscall 


----------- .xsession-errors (24743 sec old) ---------------------
** (nm-applet:18468): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.272" is not allowed to own the service "org.freedesktop.Netw
** (nm-applet:18468): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.272" is not allowed to own the service "org.freedesktop.Netw
** (nm-applet:18468): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.272" is not allowed to own the service "org.freedesktop.Netw
** (nm-applet:18468): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.272" is not allowed to own the service "org.freedesktop.Netw
** (nm-applet:18468): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.272" is not allowed to own the service "org.freedesktop.Netw
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-05-04 04:11:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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