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 568402 - crash in Evolution Mail and Calendar: Sending an email.
crash in Evolution Mail and Calendar: Sending an email.
Status: RESOLVED DUPLICATE of bug 563866
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-01-20 09:32 UTC by Felipe Contreras (banned)
Modified: 2009-01-20 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Felipe Contreras (banned) 2009-01-20 09:32:06 UTC 
What were you doing when the application crashed?
Sending an email.


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.2 2008-11-25 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.9-159.fc10.i686 #1 SMP Tue Dec 16 15:12:04 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 182841344 vsize: 182841344 resident: 46964736 share: 23355392 rss: 46964736 rss_rlim: 18446744073709551615
CPU usage: start_time: 1232442492 rtime: 2552 utime: 2302 stime: 250 cutime:0 cstime: 0 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 0xb7ff9980 (LWP 18918)]
[New Thread 0xb5051b90 (LWP 21642)]
[New Thread 0xb4650b90 (LWP 19748)]
[New Thread 0xb3a0eb90 (LWP 19738)]
[New Thread 0xb7cf7b90 (LWP 18938)]
0x00110416 in __kernel_vsyscall ()

+ Trace 211697

Thread 1 (Thread 0xb7ff9980 (LWP 18918))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 ??
  • #8 <signal handler called>
  • #9 IA__g_type_check_instance_cast
    at gtype.c line 3723
  • #10 window_binding_perform_scheduled_sync
    at gconf-bridge.c line 604
  • #11 g_timeout_dispatch
    at gmain.c line 3589
  • #12 g_main_dispatch
    at gmain.c line 2144
  • #13 IA__g_main_context_dispatch
    at gmain.c line 2697
  • #14 g_main_context_iterate
    at gmain.c line 2778
  • #15 IA__g_main_loop_run
    at gmain.c line 2986
  • #16 bonobo_main
    at bonobo-main.c line 311
  • #17 main 
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug/usr/lib/evolution/2.24/components/libevolution-mail.so.debug" does not match "/usr/lib/evolution/2.24/components/libevolution-mail.so" (CRC mism
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.24/libecontacteditor.so.0.0.0.debug" does not match "/usr/lib/evolution/2.24/libecontacteditor.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/evolution/2.24/libecontacteditor.so.0.0.0.debug" does not match "/usr/lib/evolution/2.24/libecontacteditor.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.24/plugins/liborg-gnome-groupwise-features.so.debug" does not match "/usr/lib/evolution/2.24/plugins/liborg-gnome-groupwise
warning: the debug information found in "/usr/lib/debug/usr/lib/evolution/2.24/plugins/liborg-gnome-groupwise-features.so.debug" does not match "/usr/lib/evolution/2.24/plugins/liborg-gnome-groupwise-
--------------------------------------------------
Comment 1 palfrey 2009-01-20 16:55:03 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 563866 ***