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 702709 - host lookup fails during first refresh after resume from suspend
host lookup fails during first refresh after resume from suspend
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 723594 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-06-20 05:22 UTC by Troy Sankey
Modified: 2014-03-26 08:36 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8



Description Troy Sankey 2013-06-20 05:22:45 UTC
After resuming the system from suspend, Evolution attempts to refresh the inbox but always fails at the first host lookup. Clicking refresh a second time always works.

However, if I just bring down/up the network interface, Evolution handles it elegantly.

Here is the command line output when lookup fails (and the GUI displays a notice):

(evolution:12851): evolution-mail-WARNING **: Failed to refresh folder 'UCLA: INBOX': Could not connect to 'mail.ucla.edu:143': Host lookup 'mail.ucla.edu' failed: System error

It is unpleasant because Evolution displays an error every time I open my laptop.

openSUSE 12.3, GNOME 3.8.2
Comment 1 Milan Crha 2013-08-09 12:10:44 UTC
Thanks for a bug report. I think this is due to evolution trying to do the connection before the machine itself gets properly connected to the network after resume. This can be related to bug #700414.
Comment 2 Peter Sonntag 2013-12-10 14:26:51 UTC
I have the same problem on openSuse 13.1 with evolution 3.10.1.

After resume my laptop I get the following messages:
[imapx:A] camel_imapx_read: -1
evolution-shell-Message: Connection established.  Going online.

(evolution:20606): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL)

(evolution:20606): evolution-mail-WARNING **: receive_update_got_folderinfo: Could not connect to 'imap.1und1.de:143': Host lookup 'imap.1und1.de' failed. Check your host name for spelling errors.

As this is a regular use case, it would be really great if somebody could fix it.
Comment 3 Peter Sonntag 2013-12-10 17:14:11 UTC
As Evolution needs to be restarted in order to recover, this defect should be priority high.
Comment 4 Troy Sankey 2013-12-11 01:37:11 UTC
Upgraded to GNOME 3.10.x (openSUSE 13.1) and problem persists.

(In reply to comment #3)
> As Evolution needs to be restarted in order to recover, this defect should be
> priority high.

If I wait long enough, Evolution will come back to life, but it's normally much quicker to just kill it and restart it (which I've done a lot since reporting this issue):

1. alt+f2, type "xkill"
2. click on Evolution to kill it
3. re-open Evolution
Comment 5 Milan Crha 2014-01-21 11:57:40 UTC
(In reply to comment #2)
> I have the same problem on openSuse 13.1 with evolution 3.10.1.
> 
> After resume my laptop I get the following messages:
> [imapx:A] camel_imapx_read: -1

This might be covered by:
https://git.gnome.org/browse/evolution-data-server/commit/?id=480399fab3628
thought I disagree with the commit comment a bit.

There are also a follow-up changes in evolution-data-server and evolution itself, which I've done:

Created commit 04501c5 in eds master (3.11.5+) [1]
Created commit a9730b3 in evo master (3.11.5+) [2]

Created commit b81954c in eds gnome-3-10 (3.10.4+)
Created commit 3424952 in evo gnome-3-10 (3.10.4+)

[1] https://git.gnome.org/browse/evolution-data-server/commit/?id=04501c5
[2] https://git.gnome.org/browse/evolution/commit/?id=a9730b3
Comment 6 Milan Bouchet-Valat 2014-02-13 10:57:27 UTC
*** Bug 721915 has been marked as a duplicate of this bug. ***
Comment 7 Mildred 2014-03-26 08:36:29 UTC
*** Bug 723594 has been marked as a duplicate of this bug. ***