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 709013 - Evolution does not download folders and messages via imap
Evolution does not download folders and messages via imap
Status: RESOLVED DUPLICATE of bug 680961
Product: evolution
Classification: Applications
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-09-29 03:49 UTC by Raul Liota da Rosa
Modified: 2013-10-07 10:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Image Evolution (58.08 KB, image/png)
2013-09-29 16:23 UTC, Raul Liota da Rosa
Details
backtrace (10.49 KB, text/plain)
2013-10-04 00:06 UTC, Raul Liota da Rosa
Details

Description Raul Liota da Rosa 2013-09-29 03:49:51 UTC
Evolution does not download folders and messages via IMAP.

distro: ROSA Desktop Fresh R1 release 2012.1
pkg: evolution-3.8.4-1-rosa2012.1.i586

Attached the log of evolution
Comment 1 Matthew Barnes 2013-09-29 13:48:06 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 2 Raul Liota da Rosa 2013-09-29 16:23:35 UTC
Created attachment 256030 [details]
Image Evolution
Comment 3 Raul Liota da Rosa 2013-09-29 16:24:37 UTC
Ok I'll try to explain the problem below

I have a Gmail account set up as IMAP + (there is no option to configure IMAP normal in Evolution).

And since when set up this account, Evolution gets that message in the status bar "Searching folder in IMAP server imap.gmail.com" and not out of it.

Follows an image attachment that can help you understand the problem.
Comment 4 Milan Crha 2013-09-30 16:09:11 UTC
Could you go to Edit->Preferences->Mail Accounts-><GMail IMAP account>->Receiving Email tab, and verify your settings are:
   Server: imap.gmail.com
   Port: 993
   Username: <your GMAIL user name, I have it without '@gmail.com'>
   Encryption method: SSL on a dedicated port
   Authentication: Password

please? This setup works fine for me. In case you've it the same, can you:
   $ telnet imap.gmail.com 993

It should tell (the actual IP address can differ):
   Trying 173.194.67.108...
   Connected to imap.gmail.com.
   Escape character is '^]'.

if everything works fine, aka if you can connect to the server.
Comment 5 Raul Liota da Rosa 2013-10-01 13:05:38 UTC
Evolution configured the way you asked, but still the same thing.

Follows the result of Telnet.

# telnet imap.gmail.com 993
Trying 173.194.76.109 ...
Connected to imap.gmail.com.
Escape character is '^]'.
Comment 6 Milan Crha 2013-10-01 15:21:17 UTC
Good, so you can connect to the Google server. Are you asked for a password for your Google account? When you use Seahorse, do you the right password being stored in there? (It's quite challenging to catch the right account in Seahorse, especially when you've configured multiple accounts in evolution.)

Could you install debuginfo packages for evolution and evolution-data-server, and when you get into the wrong state, then get a backtrace of running evolution and evolution-source-registry process, please? You can get a backtrace with a command like this:

   $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
Comment 7 Milan Crha 2013-10-01 15:22:25 UTC
(oops, I forgot to add):

Please make sure the backtraces will not contain any private information, like passwords, email addresses, server names and so on. I usually search for "pass" (quotes for clarity only).
Comment 8 Raul Liota da Rosa 2013-10-01 16:15:33 UTC
I ran the following command:

gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt | evolution 

And this was the return:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i686/libthread_db.so.1".
0xb772d045 in _dl_relocate_object () from /lib/ld-linux.so.2

Thread 1 (process 12742)

  • #0 _dl_relocate_object
    from /lib/ld-linux.so.2
  • #1 dl_main
    from /lib/ld-linux.so.2
  • #2 _dl_sysdep_start
    from /lib/ld-linux.so.2
  • #3 _dl_start
    from /lib/ld-linux.so.2
  • #4 _start
    from /lib/ld-linux.so.2


Alias ​​output of evolution when executed by the terminal that is:

GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

(evolution:12742): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (evolution:12742): WARNING **: Unrecognized junk filter name 'Bogofilter' in GSettings
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

(evolution:12742): Gtk-CRITICAL **: gtk_application_inhibit: assertion `application->priv->sm_proxy != NULL' failed
Comment 9 Milan Crha 2013-10-02 06:46:04 UTC
(In reply to comment #8)
> I ran the following command:
> 
> gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt | evolution 

This is not the way it should be run. First run evolution, get it to the state where it doesn't talk to the server, and only then get the backtrace (bt.txt) by invoking the gdb command.

> GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will
> not be saved or shared with other applications.

This means you do not have installed dconf. Please install it.

Those other runtime warning are fine, you are not using gnome-shell, thus you see those. I see those as well (except of the junk filter name, but that's harmless).
Comment 10 Raul Liota da Rosa 2013-10-04 00:06:07 UTC
Ok now I think I did right; p

1 - I installed dconf.
2 - I ran Evolution
3 - I ran the command "gdb - batch - ex" taa bt "-pid =` pidof `evolution &> bt.txt"

Thus, following the file bt.txt attached.
Comment 11 Raul Liota da Rosa 2013-10-04 00:06:59 UTC
Created attachment 256434 [details]
backtrace
Comment 12 Milan Crha 2013-10-07 10:34:26 UTC
Thanks for the update. The below thread shows that evolution is waiting for a response from the evolution-source-registry process, to receive a password. From that I believe you face bug #680961, thus I'm closing this as a duplicate of it.

It sometimes happens that the evolution-source-registry fails to start its libsecret/gcr connections properly (the connections as such are managed by the respective libraries, not directly by evolution-data-server), and it sometimes helps to close/kill evolution processes and let them restart them from scratch. You can do this:
a) close evolution
b) list background evolution processes:
   $ ps ax | grep evolution
c) get process IDs (PID) from the list and kill all of them by
   $ kill -9 PID
   in order of the evolution-source-registry as the first
d) start evolution, which will also start other background processes
e) you should be asked for the mail password, or it should be properly read
   from the Gnome Keyring

Thread 7 (Thread 0xa24d8b40 (LWP 12377))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/i686/libc.so.6
  • #2 g_poll
    from /lib/libglib-2.0.so.0
  • #3 ??
    from /lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #5 e_source_registry_authenticate_sync
    at e-source-registry.c line 2086
  • #6 mail_session_authenticate_sync
    at e-mail-session.c line 1600
  • #7 camel_session_authenticate_sync
    at camel-session.c line 1832
  • #8 imapx_reconnect
    at camel-imapx-server.c line 4236
  • #9 camel_imapx_server_connect
    at camel-imapx-server.c line 7332
  • #10 imapx_create_new_connection_unlocked
    at camel-imapx-conn-manager.c line 604
  • #11 camel_imapx_conn_manager_get_connection
    at camel-imapx-conn-manager.c line 674
  • #12 camel_imapx_store_get_server
    at camel-imapx-store.c line 266
  • #13 imapx_connect_sync
    at camel-imapx-store.c line 289
  • #14 service_connect_thread
    at camel-service.c line 773
  • #15 ??
    from /lib/libgio-2.0.so.0
  • #16 ??
    from /lib/libgio-2.0.so.0
  • #17 ??
    from /lib/libgio-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 ??
    from /lib/libglib-2.0.so.0
  • #20 start_thread
    from /lib/i686/libpthread.so.0
  • #21 clone
    from /lib/i686/libc.so.6

*** This bug has been marked as a duplicate of bug 680961 ***