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 630231 - Crash in set_send_status at mail-send-recv.c:308
Crash in set_send_status at mail-send-recv.c:308
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
3.4.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-09-21 08:47 UTC by Akhil Laddha
Modified: 2015-03-04 08:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Akhil Laddha 2010-09-21 08:47:26 UTC
evolution 2.33.1

1. Launched evolution, enabled evolution-mapi account
2. Dialog popped up for password
3. Entered password 2-3 times but it failed
4. Canceled the dialog
5. Evolution crashed.

System: Linux 2.6.34.7-0.2-default #1 SMP 2010-09-14 14:21:06 +0200 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10800000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Gilouche
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 242835456 vsize: 242835456 resident: 32038912 share: 23384064 rss: 32038912 rss_rlim: 18446744073709551615
CPU usage: start_time: 1285058255 rtime: 218 utime: 202 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/home/lakhil/opt/gnome3/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xaae6bb70 (LWP 10829)]
[New Thread 0xac801b70 (LWP 10826)]
[New Thread 0xad002b70 (LWP 10825)]
[New Thread 0xad81ab70 (LWP 10824)]
[New Thread 0xaf1e8b70 (LWP 10823)]
[New Thread 0xb51d4b70 (LWP 10821)]
0xffffe430 in __kernel_vsyscall ()

Thread 1 (Thread 0xb580c830 (LWP 10819))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    at gspawn.c line 392
  • #3 g_spawn_command_line_sync
    at gspawn.c line 706
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 segv_redirect
    at main.c line 279
  • #7 <signal handler called>
  • #8 free
    from /lib/libc.so.6
  • #9 g_free
    at gmem.c line 263
  • #10 set_send_status
    at mail-send-recv.c line 308
  • #11 operation_status
    at mail-send-recv.c line 333
  • #12 camel_marshal_VOID__STRING_INT
    at camel-marshal.c line 84
  • #13 g_closure_invoke
    at gclosure.c line 766
  • #14 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #15 g_signal_emit_valist
    at gsignal.c line 2983
  • #16 g_signal_emit
    at gsignal.c line 3040
  • #17 operation_idle_cb
    at camel-operation.c line 140
  • #18 g_idle_dispatch
    at gmain.c line 4254
  • #19 g_main_dispatch
    at gmain.c line 2149
  • #20 g_main_context_dispatch
    at gmain.c line 2702
  • #21 g_main_context_iterate
    at gmain.c line 2780
  • #22 g_main_loop_run
    at gmain.c line 2988
  • #23 IA__gtk_main
    at gtkmain.c line 1219
  • #24 main
    at main.c line 671

	Inferior 1 [process 10819] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (14465 sec old) ---------------------
(gnome-web-photo:8726): GLib-GObject-WARNING **: cannot register existing type `GtkMozEmbed'
** (gnome-web-photo:8726): CRITICAL **: void gtk_moz_embed_load_url(GtkMozEmbed*, const char*): assertion `GTK_IS_MOZ_EMBED(embed)' failed
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 255
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled
--------------------------------------------------
Comment 1 Milan Crha 2010-09-24 14:02:25 UTC
I tried to reproduce this, but something similar happened to me only once :( I suppose that unsubscribing from the "status" signal when freeing 'info' may help here, but as I cannot reproduce this consistently I'm not sure whether it's really it.

Are you able to reproduce this on your will?
Comment 2 Akhil Laddha 2010-09-27 06:05:58 UTC
Nope, i cann't reproduce always :-(
Comment 3 Milan Crha 2011-08-22 06:30:16 UTC
Downstream bug report about the same from 3.0.2:
https://bugzilla.redhat.com/show_bug.cgi?id=732147

Thread 1 (Thread 0x7f0907dde9a0 (LWP 1928))

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #1 __GI_abort
    at abort.c line 93
  • #2 __libc_message
    at ../sysdeps/unix/sysv/linux/libc_fatal.c line 198
  • #3 malloc_printerr
  • #4 g_free
    at gmem.c line 263
  • #5 set_send_status
    at mail-send-recv.c line 311
  • #6 g_closure_invoke
    at gclosure.c line 767
  • #7 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #8 g_signal_emit_valist
    at gsignal.c line 2983
  • #9 g_signal_emit
    at gsignal.c line 3040
  • #10 operation_emit_status_cb
    at camel-operation.c line 133
  • #11 operation_emit_status_cb
    at camel-operation.c line 116
  • #12 g_timeout_dispatch
    at gmain.c line 3895
  • #13 g_main_dispatch
    at gmain.c line 2441
  • #14 g_main_context_dispatch
    at gmain.c line 3014
  • #15 g_main_context_iterate
    at gmain.c line 3092
  • #16 g_main_loop_run
    at gmain.c line 3300
  • #17 gtk_main
    at gtkmain.c line 1358
  • #18 main
    at main.c line 734

Comment 4 Milan Crha 2011-08-22 11:28:44 UTC
I tried couple tests, together with cheating the code, but I still cannot reproduce this. I though that the operation notifies about progress asynchronously while the dialog data info is gone, but I cannot get to that state whatever I do in the code, thus it might be a bad idea of me.
Comment 5 Peter Robinson 2012-04-04 09:11:35 UTC
I'm seeing this now on evolution 3.4.0 with evolution-ews
Comment 6 Milan Crha 2015-03-04 08:11:51 UTC
No duplicates for the past (almost) three years, I'm closing this, but feel free to reopen if you face this with 3.12 or the upcoming 3.16.x.