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 567046 - crash in Evolution Mail and Calendar:
crash in Evolution Mail and Calendar:
Status: RESOLVED DUPLICATE of bug 522277
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-01-08 17:20 UTC by Russell Harrison
Modified: 2009-01-08 17:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Russell Harrison 2009-01-08 17:20:20 UTC 
What were you doing when the application crashed?



Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.27.9-73.fc9.i686 #1 SMP Tue Dec 16 15:25:05 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 86740992 vsize: 86740992 resident: 13815808 share: 8470528 rss: 13815808 rss_rlim: 4294967295
CPU usage: start_time: 1231435071 rtime: 26 utime: 17 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

[Thread debugging using libthread_db enabled]
[New Thread 0xb7fae980 (LWP 22142)]
[New Thread 0xb65fdb90 (LWP 22241)]
[New Thread 0xb7bc7b90 (LWP 22144)]
0x00110416 in __kernel_vsyscall ()

+ Trace 211392

Thread 1 (Thread 0xb7fae980 (LWP 22142))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at 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 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 IA__g_str_hash
    at gstring.c line 95
  • #10 IA__g_hash_table_lookup
    at ghash.c line 118
  • #11 message_removed
    at mail-stub-exchange.c line 400
  • #12 sync_deletions
    at mail-stub-exchange.c line 1203
  • #13 connection_handler
    at mail-stub.c line 170
  • #14 g_io_unix_dispatch
    at giounix.c line 162
  • #15 IA__g_main_context_dispatch
    at gmain.c line 2012
  • #16 g_main_context_iterate
    at gmain.c line 2645
  • #17 IA__g_main_loop_run
    at gmain.c line 2853
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 main
    at main.c line 238 


----------- .xsession-errors (17 sec old) ---------------------
file changes to /home/username/.evolution/mail/local/Inbox.sbd/2007.ibex.index.data is pausing tracker
File Change queue is:
file changes to /home/username/.evolution/mail/local/Inbox.sbd/2006.ibex.index.data is pausing tracker
File Change queue is:
file changes to /home/username/.evolution/mail/local/Inbox.sbd/2005.ibex.index is pausing tracker
File Change queue is:
file changes to /home/username/.evolution/mail/local/Inbox.sbd/2005.ibex.index.data is pausing tracker
File Change queue is:
pausing indexing while client requests or external disk I/O are taking place
Current memory usage is 16560, word count 31 and hits 35
indexing #13250 - /home/username/.evolution/mail/imap/username@email.example.com/folders/Journal/cmeta
Flushing all words - total hits in cache is 35, total words 31
CalDAV Eplugin starting up ...
** (evolution:22128): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:22128): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 palfrey 2009-01-08 17:29: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 522277 ***