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 728392 - Segmentation fault when attempting to add alarm
Segmentation fault when attempting to add alarm
Status: RESOLVED FIXED
Product: gnome-clocks
Classification: Applications
Component: general
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: Clocks maintainer(s)
Clocks maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-04-17 03:26 UTC by Craig Cabrey
Modified: 2014-09-14 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.11/3.12


Attachments
Fix segfault when modifying an alarm (2.13 KB, patch)
2014-09-11 20:24 UTC, Garrett Regier
committed Details | Review

Description Craig Cabrey 2014-04-17 03:26:52 UTC
On Arch Linux with Gnome 3.12, attempting to add an alarm to the Gnome Clocks application results in a segmentation fault.
Comment 1 PioneerAxon 2014-04-18 14:55:16 UTC
Sorry for the missing debugging symbols. Arch doesn't seem to have them by default.

  • #0 clocks_alarm_setup_dialog_apply_to_alarm
  • #1 ??
  • #2 ??
    from /usr/lib/libgobject-2.0.so.0
  • #3 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
    from /usr/lib/libgtk-3.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 ??
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 gtk_adjustment_value_changed
    from /usr/lib/libgtk-3.so.0
  • #11 clocks_alarm_setup_dialog_construct
  • #12 ??
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgio-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-3.so.0
  • #19 ??
    from /usr/lib/libgtk-3.so.0
  • #20 ??
    from /usr/lib/libgtk-3.so.0
  • #21 ??
    from /usr/lib/libgtk-3.so.0
  • #22 ??
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-3.so.0
  • #26 ??
    from /usr/lib/libgtk-3.so.0
  • #27 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-3.so.0
  • #32 ??
    from /usr/lib/libgtk-3.so.0
  • #33 ??
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-3.so.0
  • #37 ??
    from /usr/lib/libgtk-3.so.0
  • #38 gtk_main_do_event
    from /usr/lib/libgtk-3.so.0
  • #39 ??
    from /usr/lib/libgdk-3.so.0
  • #40 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #41 ??
    from /usr/lib/libglib-2.0.so.0
  • #42 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #43 g_application_run
    from /usr/lib/libgio-2.0.so.0
  • #44 _vala_main
  • #45 __libc_start_main
    from /usr/lib/libc.so.6
  • #46 _start

Comment 2 Evgeny Bobkin 2014-04-19 21:44:38 UTC
what vala, glib and gtk+ version do you have installed?
Comment 3 Garrett Regier 2014-09-11 20:24:04 UTC
Created attachment 285949 [details] [review]
Fix segfault when modifying an alarm

The days must be set before set_range() as it will emit signals which will try to access days.


I think I have the same issue, the backtrace looks similar enough anyways...
Comment 4 Paolo Borelli 2014-09-11 21:41:43 UTC
Review of attachment 285949 [details] [review]:

thanks!
Comment 5 Paolo Borelli 2014-09-14 20:07:42 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.