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 513113 - evolution-data-server-2.22 crashed with signal 5 in g_mutex_free_posix_impl()
evolution-data-server-2.22 crashed with signal 5 in g_mutex_free_posix_impl()
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
2.26.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 557068 570668 573822 575596 599375 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-30 13:01 UTC by Pedro Villavicencio
Modified: 2011-01-27 05:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Pedro Villavicencio 2008-01-30 13:01:45 UTC 
This report has been filled here:

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

"Logged out and back in, got this error right after logging in."

Version is: evolution-data-server 2.21.5

".

+ Trace 187384

Thread 1 (process 6000)

  • #0 IA__g_logv
  • #1 IA__g_log
  • #2 g_mutex_free_posix_impl
    at /build/buildd/glib2.0-2.15.2/gthread/gthread-posix.c line 171
  • #3 e_data_cal_factory_finalize
    at e-data-cal-factory.c line 286
  • #4 IA__g_object_unref
    at /build/buildd/glib2.0-2.15.2/gobject/gobject.c line 1793
  • #5 bonobo_object_unref
    at bonobo-object.c line 201
  • #6 main
    at server.c line 427
  • #7 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #8 _start 






Comment 1


Matthew Barnes





          2008-03-11 01:01:50 UTC
        



Bumping version to a stable release.






Comment 2


Andrew Conkling





          2008-08-25 02:13:25 UTC
        



Just got this again on GNOME/Evolution 2.23.90.






Comment 3


Milan Crha





          2008-09-15 13:51:46 UTC
        



Could you attach "thread apply all bt" command result from gdb next time is crashes for you, please? I do not see this crash myself, thus asking. It seems that EDataCalFactory thinks is the last there, but someone is still using it.






Comment 4


André Klapper





          2008-12-04 23:36:17 UTC
        



*** Bug 557068 has been marked as a duplicate of this bug. ***






Comment 5


Akhil Laddha





          2009-02-06 04:03:07 UTC
        



*** Bug 570668 has been marked as a duplicate of this bug. ***






Comment 6


Sam Morris





          2009-02-06 10:41:17 UTC
        



That was weird... I hit this crash, but got no less than four(!) bug-buddies, two of which said they could not find any useful information, and two of which submitted my dupes of this bug from yesterday.






Comment 7


Milan Crha





          2009-02-06 11:14:43 UTC
        



I see Sam's bug #570668 is still on 2.22, but I see there these messages on console:
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate
calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)

which may be a clue. 






Comment 8


Akhil Laddha





          2009-03-03 03:42:50 UTC
        



*** Bug 573822 has been marked as a duplicate of this bug. ***






Comment 9


Brian J. Murrell





          2009-03-10 14:24:35 UTC
        



(In reply to comment #3)
> Could you attach "thread apply all bt" command result from gdb next time is
> crashes for you, please? I do not see this crash myself, thus asking. It seems
> that EDataCalFactory thinks is the last there, but someone is still using it.

I think what you are looking for can be found here:

http://launchpadlibrarian.net/11370412/ThreadStacktrace.txt

and here:

http://launchpadlibrarian.net/11370443/ThreadStacktrace.txt

and here, for 2.25.92:

http://launchpadlibrarian.net/23717629/foo






Comment 10


Fabio Durán Verdugo





          2009-03-16 22:53:45 UTC
        



*** Bug 575596 has been marked as a duplicate of this bug. ***






Comment 11


Milan Crha





          2009-03-17 14:06:34 UTC
        



(In reply to comment #9)

Hmm, those are quite similar to the one in comment #0, where I do not see any pending operation on the backend. Maybe it's doing something in other process, like in evolution, or evo alarm notify, or such.






Comment 12


Akhil Laddha





          2009-10-26 03:23:54 UTC
        



*** Bug 599375 has been marked as a duplicate of this bug. ***






Comment 13


Akhil Laddha





          2009-10-26 03:24:40 UTC
        



last dupe in 2.26.x






Comment 14


Akhil Laddha





          2010-12-24 07:17:22 UTC
        



Could you please confirm if this bug is still happening at your end ? Please try in 2.30.3 or 2.32.1 and report back, thanks.