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 586788 - crash in Evolution Mail and Calendar: Sending email...
crash in Evolution Mail and Calendar: Sending email...
Status: RESOLVED DUPLICATE of bug 535516
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-06-23 19:49 UTC by vms
Modified: 2009-06-24 03:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description vms 2009-06-23 19:49:53 UTC 
What were you doing when the application crashed?
Sending email...


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.24.3 2009-06-13 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.27-gentoo-r8 #1 SMP PREEMPT Tue Mar 10 23:38:03 CET 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 308170752 vsize: 308170752 resident: 57143296 share: 25858048 rss: 57143296 rss_rlim: 18446744073709551615
CPU usage: start_time: 1245785255 rtime: 2455 utime: 2220 stime: 235 cutime:44 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb56a3720 (LWP 919)]
[New Thread 0xa8618b90 (LWP 2406)]
[New Thread 0xb20a1b90 (LWP 976)]
[New Thread 0xae9f4b90 (LWP 975)]
0xb7f8f424 in __kernel_vsyscall ()

+ Trace 216160

Thread 1 (Thread 0xb56a3720 (LWP 919))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 check_if_gdb
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 bugbuddy_segv_handle
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 <signal handler called>
  • #8 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #9 window_binding_perform_scheduled_sync
    from /usr/lib/evolution/2.24/libeutil.so.0
  • #10 g_timeout_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (4330 sec old) ---------------------
(21:36:37) jabber: Recv (ssl)(244): <iq from='vladmihaisima@jabber.org' to='vladmihaisima@jabber.org/Gaim' type='error' id='purple335f8328'><ping xmlns='urn:xmpp:ping'/><error code='503' type='cancel'
(21:36:37) jabber: xmlParseChunk returned warning 100
(21:36:40) msn: C: NS 000: PNG
(21:36:40) msn: S: NS 000: QNG 46
(21:37:04) jabber: Sending (ssl): <iq type='get' id='purple2de92e82'><ping xmlns='urn:xmpp:ping'/></iq>
(21:37:04) jabber: Recv (ssl)(81): <iq to="vladmihaisima@gmail.com/Home06773B75" id="purple2de92e82" type="result"/>
(21:37:04) jabber: xmlParseChunk returned warning 100
(21:37:07) jabber: Sending (ssl): <iq type='get' id='purple335f8329'><ping xmlns='urn:xmpp:ping'/></iq>
(21:37:07) jabber: Recv (ssl)(244): <iq from='vladmihaisima@jabber.org' to='vladmihaisima@jabber.org/Gaim' type='error' id='purple335f8329'><ping xmlns='urn:xmpp:ping'/><error code='503' type='cancel'
(21:37:07) jabber: xmlParseChunk returned warning 100
(21:37:10) msn: C: NS 000: PNG
(21:37:10) msn: S: NS 000: QNG 42
(21:37:34) jabber: Sending (ssl): <iq type='get' id='purple2de92e83'><ping xmlns='urn:xmpp:ping'/></iq>
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-06-24 03:54:45 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 535516 ***