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 782475 - (Search view) Crash in gcal_manager_set_search_subscriber → gcal_search_view_do_search
(Search view) Crash in gcal_manager_set_search_subscriber → gcal_search_view_...
Status: RESOLVED FIXED
Product: gnome-calendar
Classification: Applications
Component: Views
3.24.x
Other Linux
: High blocker
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2017-05-10 19:19 UTC by Jeremy Bicha
Modified: 2017-05-27 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed patch (654 bytes, patch)
2017-05-25 16:14 UTC, Milan Crha
committed Details | Review

Description Jeremy Bicha 2017-05-10 19:19:03 UTC
Ubuntu has received some semi-automated error reports from Ubuntu 17.04 with this crash signature. The crash appears new to gnome-calendar 3.24.1.

This error is one of several keeping gnome-calendar 3.24.1 from reaching all Ubuntu 17.04 users because Ubuntu has a phased-update system for users who install updates using Ubuntu's update-manager tool.

gnome-calendar (11) gcal_manager_set_search_subscriber → gcal_search_view_do_search → g_timeout_dispatch → g_main_dispatch → g_main_context_dispatch



  • #0 gcal_manager_set_search_subscriber
    at gcal-manager.c line 1305
  • #1 gcal_search_view_do_search
    at gcal-search-view.c line 460
  • #2 g_timeout_dispatch
    at ../../../../glib/gmain.c line 4674
  • #3 g_main_dispatch
    at ../../../../glib/gmain.c line 3203
  • #4 g_main_context_dispatch
    at ../../../../glib/gmain.c line 3856
  • #5 g_main_context_iterate
    at ../../../../glib/gmain.c line 3929
  • #6 g_main_context_iteration
    at ../../../../glib/gmain.c line 3990
  • #7 g_application_run
    at ../../../../gio/gapplication.c line 2381
  • #8 main
    at main.c line 44

Comment 1 Jeremy Bicha 2017-05-10 19:20:14 UTC
.

Thread 7 (Thread 0x7fe5a8abd700 (LWP 25896))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_cond_wait_until
    at ../../../../glib/gthread-posix.c line 1442
  • #2 g_async_queue_pop_intern_unlocked
    at ../../../../glib/gasyncqueue.c line 422
  • #3 g_async_queue_timeout_pop
    at ../../../../glib/gasyncqueue.c line 543
  • #4 g_thread_pool_wait_for_new_pool
    at ../../../../glib/gthreadpool.c line 167
  • #5 g_thread_pool_thread_proxy
    at ../../../../glib/gthreadpool.c line 364
  • #6 g_thread_proxy
    at ../../../../glib/gthread.c line 784
  • #7 start_thread
    at pthread_create.c line 456
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 105

Thread 1 (Thread 0x7fe5cb14db00 (LWP 25836))

  • #0 gcal_manager_set_search_subscriber
    at gcal-manager.c line 1305
  • #1 gcal_search_view_do_search
    at gcal-search-view.c line 460
  • #2 g_timeout_dispatch
    at ../../../../glib/gmain.c line 4674
  • #3 g_main_dispatch
    at ../../../../glib/gmain.c line 3203
  • #4 g_main_context_dispatch
    at ../../../../glib/gmain.c line 3856
  • #5 g_main_context_iterate
    at ../../../../glib/gmain.c line 3929
  • #6 g_main_context_iteration
    at ../../../../glib/gmain.c line 3990
  • #7 g_application_run
    at ../../../../gio/gapplication.c line 2381
  • #8 main
    at main.c line 44

Comment 2 Christian Stadelmann 2017-05-14 00:20:10 UTC
Also happens on Fedora 26, same backtrace: https://bugzilla.redhat.com/show_bug.cgi?id=1450618
Comment 3 Milan Crha 2017-05-25 16:14:32 UTC
Created attachment 352586 [details] [review]
proposed patch

The search view doesn't have set the manager, then there are several runtime warnings on console, then eventual NULL dereference. This one-liner fixes it for me.
Comment 4 Georges Basile Stavracas Neto 2017-05-27 14:02:21 UTC
Thanks!