[Evolution] Bug#618861: Bug#618861: Narrowed the problem down

Yves-Alexis Perez corsac at debian.org
Tue Apr 5 05:45:20 UTC 2011


On lun., 2011-04-04 at 19:34 -0400, Wendy Elmer wrote:
> On Mon, 2011-04-04 at 07:25 +0200, Yves-Alexis Perez wrote:
> 
> > On dim., 2011-04-03 at 21:08 -0400, Wendy Elmer wrote:
> > 
> > Thanks for your debugging session, it really helps.
> > 
> > > So, I see two problems:
> > > 1. evolution 2.32 does not issue prompts when going through
> > > squid/squidguard which is a regression from 2.30
> > 
> > Ok so that might be related to #620260
> > 
> > If you re-enable proxy stuff, could you tell us if it breaks again or
> > not? If it does, could you take some network traces using tcpdump?
> 
> Yes, it does break again if evolution needs to get a password.  If
> evolution stores the password by checking the remember password box then
> retrieving mail works.

This one wether or not proxy settings are enabled?

>   To test this, I turned on the squid network
> proxy, unchecked the box remember password and closed evolution and
> restarted.  Evolution hung again with no password prompt and the 0%
> complete messages.  I closed evolution, changed to direct network
> connection, and restarted evolution.  Evolution started and retrieved
> messages.  There was no password prompt because evolution got the
> password from the keyring.

So when password are in gnome-keyring it'd change the situation? Or is
it just unrelated to password handling?

>   I repeated both tests this time removing all
> keyrings in ~/.gnome2/keyrings each time.  The direct network connection
> case prompted for the password.  The network proxy case did not prompt
> for the password and hung again.


So when there's no password anymore, it works without proxy but it
doesn't with.

> I don't know much about tcpdump but I tried what was in the 620260 bug
> report.  port 110 did not give anything so I left off the port hoping it
> would capture on all ports.  Here is what I ran and the results.
> 
> 
> tcpdump -s0 -w evo_noproxy.pcap -nlei any
> started evolution with no proxy then closed evolution
> 
> tcpdump -s0 -w evo_proxy.pcap -nlei any
> started evolution with proxy then killed evolution
> 
> The squid proxy port is 3128.

Ok, I can see there's a tentative connection on the 3128 port but
there's nothing in there which could help us track that done. By the
way, is the proxy working (for browsing)?

Regards,
-- 
Yves-Alexis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20110405/7b04bff4/attachment.pgp>


More information about the Pkg-evolution-maintainers mailing list