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 763656 - Adding calendar creates segfault
Adding calendar creates segfault
Status: RESOLVED DUPLICATE of bug 781421
Product: gnome-calendar
Classification: Applications
Component: General
3.18.x
Other Linux
: Normal critical
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2016-03-15 01:53 UTC by cgargent
Modified: 2017-04-17 19:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
stack trace output (11.08 KB, text/plain)
2016-03-15 01:53 UTC, cgargent
Details

Description cgargent 2016-03-15 01:53:18 UTC
Created attachment 323939 [details]
stack trace output

when I try and add a new web calendar it segfaults after I have entered the username and password:

stack trace attached
Comment 1 Georges Basile Stavracas Neto 2016-03-15 01:54:47 UTC
This stack trace isn't very helpful, as it doesn't show the place where Calendar crashes. Can you please provide the full version?
Comment 2 cgargent 2016-03-15 02:01:34 UTC
1:504)$ gdb gnome-calendar 
GNU gdb (GDB) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-calendar...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/gnome-calendar 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe5ac4700 (LWP 398)]
[New Thread 0x7fffe52c3700 (LWP 399)]
[New Thread 0x7fffe4ac2700 (LWP 400)]
[New Thread 0x7fffd7fff700 (LWP 401)]
[New Thread 0x7fffd77fe700 (LWP 402)]
[New Thread 0x7fffd6151700 (LWP 403)]
[New Thread 0x7fffd5950700 (LWP 404)]
[New Thread 0x7fffc7137700 (LWP 408)]
[New Thread 0x7fffc6936700 (LWP 409)]
[New Thread 0x7fffc6135700 (LWP 410)]
[Thread 0x7fffc7137700 (LWP 408) exited]
[New Thread 0x7fffc7137700 (LWP 412)]
[New Thread 0x7fffc5934700 (LWP 413)]
[New Thread 0x7fffc5133700 (LWP 414)]
[Thread 0x7fffc6936700 (LWP 409) exited]
[Thread 0x7fffc6135700 (LWP 410) exited]
[Thread 0x7fffc7137700 (LWP 412) exited]
[Thread 0x7fffc5934700 (LWP 413) exited]
[Thread 0x7fffc5133700 (LWP 414) exited]
[Thread 0x7fffd6151700 (LWP 403) exited]
[New Thread 0x7fffd6151700 (LWP 421)]
[Thread 0x7fffd7fff700 (LWP 401) exited]
[New Thread 0x7fffd7fff700 (LWP 426)]

Thread 1 "gnome-calendar" received signal SIGSEGV, Segmentation fault.
0x00000000004249f2 in ?? ()
(gdb) backtrace
  • #0 ??
  • #1 ??
    from /usr/lib/libgio-2.0.so.0
  • #2 ??
    from /usr/lib/libgio-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #6 gtk_dialog_run
    from /usr/lib/libgtk-3.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 ??
    from /usr/lib/libgtk-3.so.0
  • #11 ??
    from /usr/lib/libgtk-3.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-3.so.0
  • #17 ffi_call_unix64
    from /usr/lib/libffi.so.6
  • #18 ffi_call
    from /usr/lib/libffi.so.6
  • #19 g_cclosure_marshal_generic_va
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-3.so.0
  • #24 g_cclosure_marshal_VOID__BOXEDv
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-3.so.0
  • #29 ??
    from /usr/lib/libgtk-3.so.0
  • #30 ??
    from /usr/lib/libgtk-3.so.0
  • #31 gtk_event_controller_handle_event
    from /usr/lib/libgtk-3.so.0
  • #32 ??
    from /usr/lib/libgtk-3.so.0
  • #33 ??
    from /usr/lib/libgtk-3.so.0
  • #34 ??
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #37 ??
    from /usr/lib/libgtk-3.so.0
  • #38 ??
    from /usr/lib/libgtk-3.so.0
  • #39 gtk_main_do_event
    from /usr/lib/libgtk-3.so.0
  • #40 ??
    from /usr/lib/libgdk-3.so.0
  • #41 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #42 ??
    from /usr/lib/libglib-2.0.so.0
  • #43 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #44 g_application_run
    from /usr/lib/libgio-2.0.so.0
  • #45 main

Comment 3 Marinus Schraal 2016-03-27 11:10:40 UTC
Thanks for your effort, but the stack trace sadly lacks debugging info and that makes it less useful. See https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details for steps how to get a stacktrace with debugging info. Note the section about 'debugging information packages', judging from your trace you need the debugging info from the glib, gtk+ and gnome-calendar packages at least.
Comment 4 Georges Basile Stavracas Neto 2017-04-17 19:22:53 UTC
If any news arrive, please describe them at bug 781421.

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