Description of problem: attempted LDAP lookup, I seem to remember this to have been working before. Version-Release number of selected component: claws-mail-3.9.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/claws-mail crash_function: __pthread_mutex_lock executable: /usr/bin/claws-mail kernel: 3.8.5-201.fc18.x86_64 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (5 frames) #0 __pthread_mutex_lock at pthread_mutex_lock.c:50 #1 ldapqry_get_stop_flag at ldapquery.c:247 #2 ldapqry_connect at ldapquery.c:715 #3 ldapqry_perform_search at ldapquery.c:891 #4 ldapqry_search at ldapquery.c:933
Created attachment 733066 [details] File: backtrace
Created attachment 733067 [details] File: cgroup
Created attachment 733068 [details] File: core_backtrace
Created attachment 733069 [details] File: dso_list
Created attachment 733070 [details] File: environ
Created attachment 733071 [details] File: limits
Created attachment 733072 [details] File: maps
Created attachment 733073 [details] File: open_fds
Created attachment 733074 [details] File: proc_pid_status
Created attachment 733075 [details] File: var_log_messages
Created attachment 733076 [details] File: xsession_errors
Just my two cents, since I don't have an LDAP env to test with. If the problem is reproducible for you, it might be worth reporting it directly into the upstream tracker or consulting their mailing-list: http://www.thewildbeast.co.uk/claws-mail/bugzilla/index.cgi Notice the contents of your ~/.xsession_errors file: | ** (claws-mail:2249): WARNING **: [10:19:05] x230.internal.pcfe.net: unknown host. | ** (claws-mail:2249): WARNING **: strange, no answers or more than one | (claws-mail:2249): Claws-Mail-CRITICAL **: imap_scan_required: assertion `session != NULL' failed | ** (claws-mail:5117): WARNING **: [10:56:28] x230.internal.pcfe.net: unknown host. The mutex ptr being NULL in thread 1 may be the result of some race between multiple threads working on a dynamically created "qry" (query) object that has been freed and has become invalid: | #0 __GI___pthread_mutex_lock (mutex=0x0) at pthread_mutex_lock.c:50 One step before that it had a "qry" ptr, which would point at an object with an allocated mutex as set up by ldapqry_create(): | #1 0x00000000005b090f in ldapqry_get_stop_flag (qry=0x22f6e00) at ldapquery.c:247 64 LdapQuery *ldapqry_create( void ) { 89 /* Mutex to protect stop and busy flags */ 90 qry->mutexStop = g_malloc0( sizeof( pthread_mutex_t ) ); 91 pthread_mutex_init( qry->mutexStop, NULL ); 99 return qry; And this is how it would be freed with the mutex ptr getting reset to NULL: 328 void ldapqry_free( LdapQuery *qry ) { 336 pthread_mutex_destroy( qry->mutexStop ); 339 g_free( qry->mutexStop ); 344 qry->mutexStop = NULL; If an existing thread keeps using the same "qry" ptr, it would run into the invalid data. Just some theory.
(In reply to comment #12) > Just my two cents, since I don't have an LDAP env to test with. If the > problem is reproducible for you, it might be worth reporting it directly > into the upstream tracker or consulting their mailing-list: > http://www.thewildbeast.co.uk/claws-mail/bugzilla/index.cgi Yes I can do that. Are you OK with me pasting your analysis (which is over my head, I'm just a consultant ;-) > Notice the contents of your ~/.xsession_errors file: > > | ** (claws-mail:2249): WARNING **: [10:19:05] x230.internal.pcfe.net: > unknown host. Good point. Fixing this made the bug no longer reproducible. The notebook is pretty new and I had not yet created the A record when I ran into this bug. I made the missing DNS entry a few minutes ago (and also set up dynamic DNS updates with TSIG so that resolution of the name yields the correct IP) and seem to be able to do LDAP lookups just fine (tried twice).
> Are you OK with me pasting your analysis Of course! It's common practice to link to downstream bug reports anyway, so upstream might look there for attachments/details (such as those from ABRT).
done, sorry for the delay. It's at http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2914
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.