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 529691 - Deadlock in evolution
Deadlock in evolution
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
2.22.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[passwords]
Depends on:
Blocks:
 
 
Reported: 2008-04-24 10:42 UTC by Akhil Laddha
Modified: 2009-01-23 10:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Akhil Laddha 2008-04-24 10:42:17 UTC 
I was forced to change my password and, now when I connect to a groupwise
server (via. IMAP) I get this:

+ Trace 196011







Comment 1


Akhil Laddha





          2008-04-24 10:43:40 UTC
        



Could be similar deadlock  





+
Trace
    196012
















Comment 2


Milan Crha





          2008-04-24 11:11:08 UTC
        



Akhil, what is your revision number of evolution-data-server? The line
ep_msg_send (msg=0x966d300) at e-passwords.c:465
doesn't match with mine. Also, Matt did some changes here recently.






Comment 3


Akhil Laddha





          2008-04-24 11:15:02 UTC
        



These traces are from stable version 2.22






Comment 4


Matthew Barnes





          2008-04-24 18:43:52 UTC
        



I'll take a closer look at this tomorrow.  I think I recall fixing something recently related to forgetting passwords, at least in trunk.






Comment 5


Matthew Barnes





          2008-04-25 01:06:34 UTC
        



Akhil, are you seeing any messages on the terminal when the deadlock occurs?






Comment 6


Srinivasa Ragavan





          2008-04-25 04:02:19 UTC
        



Matt, it was Michael's upstream bug, akhil filed it here.






Comment 7


Matthew Barnes





          2008-04-25 15:37:29 UTC
        



Hard to tell what's going on here based on these stack traces.  I've not been able to reproduce this deadlock for myself using 2.23.1.  Main difference between the password logic in 2.22 versus 2.23 is bug #518886 (followed by a typo fix in bug #453109), but that was just code cleanup.

If anyone else encounters this, it would be useful to know if any warnings are showing up on the terminal at the point of deadlock.






Comment 8


Tobias Mueller





          2009-01-22 22:12:36 UTC
        



Any news on this one?

This bug is NEEDINFO for pretty long now. I tend to either close it, if it's not reproducible anymore, or REOPEN if it is.






Comment 9


Michael Meeks





          2009-01-23 10:16:41 UTC
        



Havn't seen this in 2.24 at all; I presume it got fixed.