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 662193 - e-calendar-factory crashed with SIGABRT in raise()
e-calendar-factory crashed with SIGABRT in raise()
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: libical
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-10-19 13:45 UTC by Pedro Villavicencio
Modified: 2011-11-30 08:23 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-10-19 13:45:21 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/829818

latest duplicate is with: evolution-data-server 3.2.0-0ubuntu1

".

Thread 2 (Thread 0x7f540ba67700 (LWP 1646))

  • #0 read
    at ../sysdeps/unix/syscall-template.S line 82
  • #1 read
    at /usr/include/x86_64-linux-gnu/bits/unistd.h line 45
  • #2 unix_signal_helper_thread
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 4546
  • #3 g_thread_create_proxy
    at /build/buildd/glib2.0-2.29.16/./glib/gthread.c line 1962
  • #4 start_thread
    at pthread_create.c line 304
  • #5 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #6 ??

Comment 1 Matthew Barnes 2011-10-19 14:02:12 UTC
Thread 10 is crashing deep in libical.

What version of libical is being used here?

Note, the libical project has it's own bug tracking system.

This may have to be moved to:
http://sourceforge.net/tracker/?group_id=16077&atid=116077
Comment 2 Pedro Villavicencio 2011-10-19 15:01:41 UTC
This is libical0 0.44-3 , should i move the bug there (libical tracker) then?. Thanks!.
Comment 3 Matthew Barnes 2011-10-19 16:02:15 UTC
Yeah, that might be a better place to start.  If it turns out to be an Evo thing you can always bounce it back here.
Comment 4 Milan Crha 2011-11-30 08:23:45 UTC
Same downstream bug report from 3.2.2:
https://bugzilla.redhat.com/show_bug.cgi?id=758455

It might be fixed with commit [1] in git master for 3.3.3+ and commit [2] in gnome-3-2 for 3.2.3+ of evolution-data-server.

[1] http://git.gnome.org/browse/evolution-data-server/commit/?id=f3a1b06f7
[2] http://git.gnome.org/browse/evolution-data-server/commit/?h=gnome-3-2&id=af5d404e57f43