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 681615 - crash in camel_folder_thread_messages_unref (thread=0x83650000) at camel-folder-thread.c:730
crash in camel_folder_thread_messages_unref (thread=0x83650000) at camel-...
Status: RESOLVED DUPLICATE of bug 680467
Product: evolution
Classification: Applications
Component: Mailer
3.6.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-08-10 17:06 UTC by David Ronis
Modified: 2013-09-13 01:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Ronis 2012-08-10 17:06:51 UTC
I was looking at emails (in the git/master) and deleted several,  individually, but in rapid succession (i.e., before allowing the view window to finish drawing the e-mail. 

Here's a backtrace:

Thread 3 (Thread 0xb238b860 (LWP 17065))

  • #0 poll
    from /lib/libc.so.6
  • #1 _xcb_conn_wait
    from /usr/lib/libxcb.so.1
  • #2 xcb_wait_for_event
    from /usr/lib/libxcb.so.1
  • #3 _XReadEvents
    from /usr/lib/libX11.so.6
  • #4 XIfEvent
    from /usr/lib/libX11.so.6
  • #5 gdk_x11_get_server_time
    at gdkwindow-x11.c line 4913
  • #6 clipboard_get_timestamp
    at gtkclipboard.c line 489
  • #7 gtk_clipboard_request_contents
    at gtkclipboard.c line 1008
  • #8 gtk_clipboard_request_targets
    at gtkclipboard.c line 1354
  • #9 e_focus_tracker_update_actions
    at e-focus-tracker.c line 802
  • #10 shell_view_update_actions
    at e-shell-view.c line 797
  • #11 mail_shell_view_update_actions
    at e-mail-shell-view.c line 845
  • #12 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #13 g_type_class_meta_marshal
    at gclosure.c line 970
  • #14 g_closure_invoke
    at gclosure.c line 777
  • #15 signal_emit_unlocked_R
    at gsignal.c line 3481
  • #16 g_signal_emit_valist
    at gsignal.c line 3300
  • #17 g_signal_emit
    at gsignal.c line 3356
  • #18 e_shell_view_update_actions
    at e-shell-view.c line 1767
  • #19 mail_shell_view_reader_changed_cb
    at e-mail-shell-view-private.c line 383
  • #20 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #21 g_closure_invoke
    at gclosure.c line 777
  • #22 signal_emit_unlocked_R
    at gsignal.c line 3551
  • #23 g_signal_emit_valist
    at gsignal.c line 3300
  • #24 g_signal_emit_by_name
    at gsignal.c line 3393
  • #25 reconnect_changed_event
    at e-mail-shell-content.c line 83
  • #26 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #27 g_closure_invoke
    at gclosure.c line 777
  • #28 signal_emit_unlocked_R
    at gsignal.c line 3551
  • #29 g_signal_emit_valist
    at gsignal.c line 3300
  • #30 g_signal_emit
    at gsignal.c line 3356
  • #31 e_mail_reader_changed
    at e-mail-reader.c line 4121
  • #32 mail_reader_message_selected_cb
    at e-mail-reader.c line 2959
  • #33 g_cclosure_marshal_VOID__STRING
    at gmarshal.c line 964
  • #34 g_closure_invoke
    at gclosure.c line 777
  • #35 signal_emit_unlocked_R
    at gsignal.c line 3551
  • #36 g_signal_emit_valist
    at gsignal.c line 3300
  • #37 g_signal_emit
    at gsignal.c line 3356
  • #38 on_cursor_activated_idle
    at message-list.c line 4020
  • #39 g_idle_dispatch
    at gmain.c line 4797
  • #40 g_main_dispatch
    at gmain.c line 2707
  • #41 g_main_context_dispatch
    at gmain.c line 3211
  • #42 g_main_context_iterate
    at gmain.c line 3282
  • #43 g_main_loop_run
    at gmain.c line 3476
  • #44 gtk_main
    at gtkmain.c line 1162
  • #45 main
    at main.c line 674

Comment 1 Milan Crha 2012-08-17 09:07:32 UTC
Thanks for a bug report. I'm pretty sure this is jut another variation of bug #680467, thus I'm marking this as a duplicate of it. I still do not know how to reproduce this, or what might happen in the background. The threads doesn't suggest anything obvious.

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