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 554190 - crash in Evolution Mail and Calendar: closing evolution
crash in Evolution Mail and Calendar: closing evolution
Status: RESOLVED DUPLICATE of bug 541872
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-09-28 16:05 UTC by Christoph Anton Mitterer
Modified: 2008-09-29 04:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Christoph Anton Mitterer 2008-09-28 16:05:17 UTC 
What were you doing when the application crashed?
closing evolution



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26 #1 SMP PREEMPT Tue Aug 5 00:17:08 CEST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 651706368 vsize: 651706368 resident: 175382528 share: 27824128 rss: 175382528 rss_rlim: 18446744073709551615
CPU usage: start_time: 1222616664 rtime: 4063 utime: 3581 stime: 482 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f893c50a700 (LWP 4257)]
(no debugging symbols found)
0x00007f8937dee5ff in waitpid () from /lib/libpthread.so.0

+ Trace 207492

Thread 1 (Thread 0x7f893c50a700 (LWP 4257))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #6 <signal handler called>
  • #7 ??
  • #8 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #9 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #10 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #11 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #12 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #13 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #14 XRE_TermEmbedding
    from /usr/lib/xulrunner-1.9/libxul.so
  • #15 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #16 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #17 exit
    from /lib/libc.so.6
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue: returning plugin name.
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue return
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue: returning plugin description.
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue return
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetMIMEDescription
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetMIMEDescription return
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue: returning plugin name.
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue return
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue: returning plugin description.
GCJ PLUGIN: thread 0x7f6a2c03c800: NP_GetValue return
RSS: cleaning all remaining sessions ...done
--------------------------------------------------
Comment 1 Akhil Laddha 2008-09-29 04:08:54 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 541872 ***