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 572247 - evolution-data-server crashed : trying to sync mails for offline
evolution-data-server crashed : trying to sync mails for offline
Status: RESOLVED DUPLICATE of bug 515158
Product: evolution-data-server
Classification: Platform
Component: Calendar
2.26.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[groupwise]
Depends on:
Blocks:
 
 
Reported: 2009-02-18 06:52 UTC by Akhil Laddha
Modified: 2013-09-14 16:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Akhil Laddha 2009-02-18 06:52:56 UTC 
Evolution 2.25.91 (Group wise)

I clicked on send/receive and in the middle of fetching ,i went offline, eds crashed after some time.  

GThread-ERROR **: file gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...

Program received signal SIGABRT, Aborted.
0xffffe430 in __kernel_vsyscall ()
(gdb) t a a bt

+ Trace 212650







Comment 1


Akhil Laddha





          2009-02-18 06:53:37 UTC
        



Gdb traces of evolution 





+
Trace
    212651
















Comment 2


Akhil Laddha





          2009-02-18 06:54:10 UTC
        



could be related to bug 470651






Comment 3


palfrey





          2009-02-18 17:36:28 UTC
        



Looks like a dupe of bug 559064 which was marked as fixed...






Comment 4


Milan Crha





          2009-02-27 12:33:00 UTC
        



This one crashes in a calendar, Tom's in an address book. Also, the session 0xb5728b08 is still working in Thread 17, while it is going to be finalized in Thread 1.

I've a bit different libsoup, seems to me, my line 70 in soup-session-sync.c is not the g_mutex_free call, but that's fine. I see that this lock is used only in wait_for_connection function, but I do not see here that call, thus it should be something else. Briefly looking info the libsoup code, to that file, in that wait_for_connection function, it's possible to leave this function with a lock locked, under if (proxy_resolver) {, though I do not suppose you've also a proxy set. Maybe the call of the wait_for_connection is just hidden here.

I do not know where the right fix should come, either to libsoup, e-cal-backend-groupwise or to e-gw-connection?






Comment 5


Milan Crha





          2009-03-25 17:51:06 UTC
        



This one has similar issue as in bug #515158, thus marking as a duplicate.
Someone should take care of not finalizing running session and it'll fix it.

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