IMAP accounts checked only once per service start

Bug #113261 reported by JonathanC
2
Affects Status Importance Assigned to Milestone
cGmail
Fix Committed
Undecided
Unassigned

Bug Description

I have had this behavior for the last few days (maybe since the time the checker has been made multi-threaded?): my IMAP accounts are being checked only once per service start.

Here's an example run where I have put some spaces between the first run of checks and the others.

stop called
Enabling AWN notifications
checking gmail account [gmail_account] ...
checking imap account [imap_account_1] ...
connecting to the imap server ...
checking imap account [imap_account_2] ...
connecting to the imap server ...
checking imap account [imap_account_3] ...
connecting to the imap server ...
... connection done
authenticate user ...
...auth done
getting mails...
... connection done
authenticate user ...
...done
...done
...auth done
getting mails...
...done
... connection done
authenticate user ...
...auth done
getting mails...
...done

checking gmail account [gmail_account] ...
...done
checking gmail account [gmail_account] ...
...done
checking gmail account [gmail_account] ...
...done
checking gmail account [gmail_account] ...
...done
checking gmail account [gmail_account] ...
...done
checking gmail account [gmail_account] ...
...done
checking gmail account [gmail_account] ...
...done

Revision history for this message
JonathanC (jhonnyc) wrote :

I forgot to write that I am using the revision 10

Revision history for this message
Marco Ferragina (ferama) wrote :

mmm on my system it seem to work well! Anyway I will indagate the problem as soon as I can.
I can't work to cgmail development for a couple of week from now (or anyway I can't work so hard) (I should
finish my studies at university) so sorry but you must wait :(

Revision history for this message
JonathanC (jhonnyc) wrote :

Don't worry, I am also very busy trying to finish up my thesis for graduation.

If I find some time I will try to fix it myself! :)

Revision history for this message
Marco Ferragina (ferama) wrote :

I still can't reproduce this. Someone else with this problem?

Revision history for this message
JonathanC (jhonnyc) wrote :

Still doing in rev 12.

If it can help, the new status check icon remains displayed for the accounts which are stuck and not checked anymore.

Here's the log:

checking gmail account 1
checking imap account 2
connecting to the imap server ...
checking imap account 3
connecting to the imap server ...
checking imap account 4
connecting to the imap server ...
... connection done
authenticate user ...
...auth done
getting mails...
...done
...done
... connection done
authenticate user ...
...auth done
getting mails...
...done
... connection done
authenticate user ...
...auth done
getting mails...
...done

At this point, the three IMAP accounts seem to have completed the check process, but their "checkng icons" are still displayed in the GUI. The GMAIL account instead behaves correctly.
After the refresh timeout I get:

checking gmail account 1 ...
...done

Only gmail is checked.

Revision history for this message
Marco Ferragina (ferama) wrote :

I have had problems with threads and dbus (if one don't pay attention threads are evils)

It can be that last revision have solved your problem. Onestly I'm not sure but It can be :)

Please try and let me know

Revision history for this message
JonathanC (jhonnyc) wrote :

I have found the problem and attached a patch for revision 13.

The self.stop_check() call was missing in the IMAP checker when no new emails were found

Revision history for this message
Marco Ferragina (ferama) wrote :

Thanks alot. Why I don't found it? :) Ouch

I will include the patch in next commit.

I think 0.4 version of cGmail is almost there, it needs only some
tests.

Marco Ferragina (ferama)
Changed in cgmail:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.