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

Wendy Elmer webe3vt at aim.com
Mon Apr 4 23:34:07 UTC 2011


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.  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.  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.


> 
> Peter, could you check your proxy settings too?
> 
> > 2. there should be a warning somewhere about downgrading from 2.32 and
> > the moving of the .evolution directory 
> 
> Yeah, that's a good idea (I think the warning should be done directly in
> the app but a NEWS.Debian is a good idea indeed).
> 
> Regards,


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.

Let me know if you want me to try anything else.

Brent

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20110404/19625dd5/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: evo_noproxy.pcap
Type: application/octet-stream
Size: 219335 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20110404/19625dd5/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: evo_proxy.pcap
Type: application/octet-stream
Size: 4327 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20110404/19625dd5/attachment-0003.obj>


More information about the Pkg-evolution-maintainers mailing list