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 553881 - crash in Evolution Mail and Calendar: I had just added a 3rd R...
crash in Evolution Mail and Calendar: I had just added a 3rd R...
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-26 03:18 UTC by kerry
Modified: 2008-09-26 03:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description kerry 2008-09-26 03:18:46 UTC 
What were you doing when the application crashed?
I had just added a 3rd RSS feed and closed the application.


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

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: stilllife

Memory status: size: 112480256 vsize: 112480256 resident: 31768576 share: 22159360 rss: 31768576 rss_rlim: 4294967295
CPU usage: start_time: 1222399010 rtime: 207 utime: 194 stime: 13 cutime:1 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb655ab40 (LWP 23335)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 207371

Thread 1 (Thread 0xb655ab40 (LWP 23335))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.5/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 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #8 <signal handler called>
  • #9 ??
  • #10 AppendAndRemoveThread
    at ../../dist/include/xpcom/nsAutoPtr.h line 972
  • #11 nsBaseHashtable<nsVoidPtrHashKey, nsRefPtr<nsThread>, nsThread*>::s_EnumStub
    at ../../dist/include/xpcom/nsBaseHashtable.h line 346
  • #12 PL_DHashTableEnumerate
  • #13 nsThreadManager::Shutdown
    at ../../dist/include/xpcom/nsBaseHashtable.h line 221
  • #14 NS_ShutdownXPCOM_P
    at nsXPComInit.cpp line 774
  • #15 XRE_TermEmbedding
    at nsEmbedFunctions.cpp line 160
  • #16 EmbedPrivate::PopStartup
    at EmbedPrivate.cpp line 565
  • #17 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #18 rss_finalize
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #19 exit
    from /lib/i686/cmov/libc.so.6
  • #20 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #21 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors (15924 sec old) ---------------------
(evolution:5930): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:5930): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:5930): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:5930): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:5930): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:5930): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:5930): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-09-26 03:47:55 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 ***