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 666490 - Crash in e-mail-session.c:user_message_response
Crash in e-mail-session.c:user_message_response
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Milan Crha
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-12-19 09:05 UTC by Milan Crha
Modified: 2011-12-22 17:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
evo patch (1.30 KB, patch)
2011-12-22 16:05 UTC, Milan Crha
committed Details | Review
evo patch ][ (600 bytes, patch)
2011-12-22 17:08 UTC, Milan Crha
committed Details | Review

Description Milan Crha 2011-12-19 09:05:59 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=768761

libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        evolution
comment:        I clicked on the "Dismiss" button for the near quota warning
window. Evolution crashed.
crash_function: e_flag_set
executable:     /usr/bin/evolution
kernel:         3.1.4-1.fc16.i686.PAE
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time:           Sun 18 Dec 2011 12:21:57 PM EST

Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

Thread 2 (Thread 0xb7685b40 (LWP 11750))

  • #0 __kernel_vsyscall
  • #1 read
    at ../sysdeps/unix/syscall-template.S line 82
  • #2 read
    at /usr/include/bits/unistd.h line 45
  • #3 unix_signal_helper_thread
    at gmain.c line 4551
  • #4 g_thread_create_proxy
    at gthread.c line 1962
  • #5 start_thread
    at pthread_create.c line 309
  • #6 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 133

Thread 1 (Thread 0xb78a28c0 (LWP 11748))

  • #0 e_flag_set
    at e-flag.c line 89
  • #1 user_message_response
    at e-mail-session.c line 166
  • #2 g_cclosure_marshal_VOID__INT
    at gmarshal.c line 224
  • #3 g_closure_invoke
    at gclosure.c line 774
  • #4 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #5 g_signal_emit_valist
    at gsignal.c line 3003
  • #6 g_signal_emit
    at gsignal.c line 3060
  • #7 gtk_dialog_response
    from /usr/lib/libgtk-3.so.0
  • #8 g_cclosure_marshal_VOID__INT
    at gmarshal.c line 224
  • #9 g_closure_invoke
    at gclosure.c line 774
  • #10 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #11 g_signal_emit_valist
    at gsignal.c line 3003
  • #12 g_signal_emit
    at gsignal.c line 3060
  • #13 e_alert_response
    at e-alert.c line 946
  • #14 alert_action_activate
    at e-alert.c line 361
  • #15 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #16 g_closure_invoke
    at gclosure.c line 774
  • #17 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #18 g_signal_emit_valist
    at gsignal.c line 3003
  • #19 g_signal_emit
    at gsignal.c line 3060
  • #20 ??
    from /usr/lib/libgtk-3.so.0
  • #21 gtk_action_activate
    from /usr/lib/libgtk-3.so.0
  • #22 ??
    from /usr/lib/libgtk-3.so.0
  • #23 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #24 g_closure_invoke
    at gclosure.c line 774
  • #25 signal_emit_unlocked_R
    at gsignal.c line 3342
  • #26 g_signal_emit_valist
    at gsignal.c line 3003
  • #27 g_signal_emit
    at gsignal.c line 3060
  • #28 gtk_button_clicked
    from /usr/lib/libgtk-3.so.0
  • #29 ??
    from /usr/lib/libgtk-3.so.0
  • #30 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #31 g_type_class_meta_marshal
    at gclosure.c line 885
  • #32 g_closure_invoke
    at gclosure.c line 774
  • #33 signal_emit_unlocked_R
    at gsignal.c line 3202
  • #34 g_signal_emit_valist
    at gsignal.c line 3003
  • #35 g_signal_emit
    at gsignal.c line 3060
  • #36 gtk_button_released
    from /usr/lib/libgtk-3.so.0
  • #37 ??
    from /usr/lib/libgtk-3.so.0
  • #38 ??
    from /usr/lib/libgtk-3.so.0
  • #39 g_type_class_meta_marshal
    at gclosure.c line 885
  • #40 g_closure_invoke
    at gclosure.c line 774
  • #41 signal_emit_unlocked_R
    at gsignal.c line 3310
  • #42 g_signal_emit_valist
    at gsignal.c line 3013
  • #43 g_signal_emit
    at gsignal.c line 3060
  • #44 ??
    from /usr/lib/libgtk-3.so.0
  • #45 gtk_propagate_event
    from /usr/lib/libgtk-3.so.0
  • #46 gtk_main_do_event
    from /usr/lib/libgtk-3.so.0
  • #47 ??
    from /usr/lib/libgdk-3.so.0
  • #48 ??
    from /usr/lib/libgdk-3.so.0
  • #49 g_main_dispatch
    at gmain.c line 2425
  • #50 g_main_context_dispatch
    at gmain.c line 2995
  • #51 g_main_context_iterate
    at gmain.c line 3073
  • #52 g_main_loop_run
    at gmain.c line 3281
  • #53 gtk_main
    from /usr/lib/libgtk-3.so.0
  • #54 main
    at main.c line 696

Comment 1 Milan Crha 2011-12-22 16:05:05 UTC
Created attachment 204097 [details] [review]
evo patch

for evolution;

Confirming, I can reproduce it too. The issue is that the message 'm' is already gone when user finishes the dialog. This happens when only an informative message is shown to a user. Question messages do not suffer of this.
Comment 2 Milan Crha 2011-12-22 16:07:09 UTC
Created commit 8ad132c in evo master (3.3.4+)
Created commit 88f6f20 in evo gnome-3-2 (3.2.3+)
Comment 3 Milan Crha 2011-12-22 17:08:42 UTC
Created attachment 204102 [details] [review]
evo patch ][

for evolution;

Err, the previous patch is not working correctly when there is a question dialog and the invoker waits for a response, while the question was invoked in a dedicated thread. This fixes it.
Comment 4 Milan Crha 2011-12-22 17:12:58 UTC
Created commit a1112c6 in evo master (3.3.4+)
Created commit 1cc1011 in evo gnome-3-2 (3.2.3+)