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 570760 - crash in Evolution Mail and Calendar: Just started evolution, ...
crash in Evolution Mail and Calendar: Just started evolution, ...
Status: RESOLVED DUPLICATE of bug 535248
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-02-06 08:18 UTC by Iestyn Pryce
Modified: 2009-02-23 18:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Iestyn Pryce 2009-02-06 08:18:31 UTC 
What were you doing when the application crashed?
Just started evolution, and clicked on the 'Evolution Warning' orange triangle in the bottom left hand corner.


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.12-78.2.8.fc9.i686 #1 SMP Mon Jan 19 20:14:35 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 125800448 vsize: 125800448 resident: 44986368 share: 20660224 rss: 44986368 rss_rlim: 4294967295
CPU usage: start_time: 1233908220 rtime: 317 utime: 258 stime: 59 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb7fb0760 (LWP 2997)]
[New Thread 0xb5bffb90 (LWP 3041)]
0x00447416 in __kernel_vsyscall ()

+ Trace 212290

Thread 1 (Thread 0xb7fb0760 (LWP 2997))

  • #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 segv_redirect
    at main.c line 519
  • #9 <signal handler called>
  • #10 ___fprintf_chk
    at fprintf_chk.c line 32
  • #11 e_logger_log
    at /usr/include/bits/stdio2.h line 98
  • #12 handle_error
    at e-activity-handler.c line 499
  • #13 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
  • #22 g_datalist_clear
    from /lib/libgobject-2.0.so.0
  • #23 g_datalist_clear
    from /lib/libgobject-2.0.so.0
  • #24 g_datalist_clear
    from /lib/libgobject-2.0.so.0
  • #25 ??
  • #26 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0 
Backtrace stopped: frame did not save the PC
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (20734779 sec old) ---------------------
get dylunio pop://dylunio@pop.googlemail.com/
Find Items 0
get dylunio pop://dylunio@pop.googlemail.com/
Find Items 0
get dylunio pop://dylunio@pop.googlemail.com/
Find Items 0
get dylunio pop://dylunio@pop.googlemail.com/
Find Items 0
get dylunio pop://dylunio@pop.googlemail.com/
Find Items 0
get dylunio pop://dylunio@pop.googlemail.com/
Find Items 0
fff
get dylunio pop://dylunio@pop.googlemail.com/
Find Items 0
--------------------------------------------------
Comment 1 Milan Crha 2009-02-23 18:41:13 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 535248 ***