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 525960 - crash in Tasks: Closing evolution becaus...
crash in Tasks: Closing evolution becaus...
Status: RESOLVED DUPLICATE of bug 508447
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-04-03 14:00 UTC by Russell Harrison
Modified: 2008-05-13 09:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Russell Harrison 2008-04-03 14:00:46 UTC 
Version: 2.12

What were you doing when the application crashed?
Closing evolution because it was unresponsive


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:54:46 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 88186880 vsize: 88186880 resident: 20975616 share: 10346496 rss: 20975616 rss_rlim: 4294967295
CPU usage: start_time: 1207230825 rtime: 89 utime: 79 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208964832 (LWP 7603)]
[New Thread -1266701424 (LWP 7738)]
[New Thread -1245721712 (LWP 7663)]
[New Thread -1212335216 (LWP 7604)]
0x00110402 in __kernel_vsyscall ()

+ Trace 194119

Thread 3 (Thread -1245721712 (LWP 7663))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #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 strlen
    from /lib/libc.so.6
  • #10 e_cal_component_set_attachment_list
    at e-cal-component.c line 1570
  • #11 add_ical
  • #12 get_changed_events
    at e-cal-backend-exchange-calendar.c line 515
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6 


----------- .xsession-errors ---------------------
4/3/2008 10:00:04 AM [Info]: Updated first results for 'j'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'k'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'l'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'm'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'n'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'o'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'p'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'q'.
4/3/2008 10:00:04 AM [Info]: Updated first results for 'r'.
[  DEBUG] Change detected in dataproviders data (/home/rusharri:Home)
[  DEBUG] Change detected in dataproviders data (/home/rusharri:Home)
[  DEBUG] Change detected in dataproviders data (/home/rusharri:Home)
[  DEBUG] Change detected in dataproviders data (/home/rusharri:Home)
[  DEBUG] Change detected in dataproviders data (/home/rusharri:Home)
[  DEBUG] Change detected in dataproviders data (/home/rusharri:Home)
--------------------------------------------------
Comment 1 Akhil Laddha 2008-05-13 09:09:59 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 508447 ***