maemo.org Bugzilla – Bug 6219
Modest doesn't take care of preferences for automatic update
Last modified: 2010-02-03 14:08:25 UTC
You need to
before you can comment on or make changes to this bug.
(Control Panel > General > About product)
STEPS TO REPRODUCE THE PROBLEM:
Set auto update in Modest's parameters for Local Wifi Network only
Connect to the internet mobile connection (3G, or edge)
Modest keep quiet and doesn't try to update
Modest try to update, say that it cannot update (due to isp blocking imap), and
show windows account parameters.
Everytime the tablet lost the connection, and reconnect on the mobile network
EXTRA SOFTWARE INSTALLED:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:220.127.116.11)
Gecko/20091102 Firefox 3.5.3
It was working in firmware release 2009.41-10
Change priority as it s relly annoying
> STEPS TO REPRODUCE THE PROBLEM:
Please ALWAYS provide exact steps, click by click. Thanks!
Modest > Settings > Update automatically > Update when connected via: WLAN
> (due to isp blocking imap)
I need a mobile provider that blocks IMAP to reproduce this. :-P
Can you say which exact ISP this is about, please?
(Note to myself: This does not seem to be int-136358.)
This has been already fixed internally in the last weeks.
There was a problem in tinymail when switching connections.
Not exactly clear which release version the fix is included in, but it should
definitely be in a week48 release, most likely way earlier.
Any public update released with or after this week will include the fix.
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
*** Bug 7664 has been marked as a duplicate of this bug. ***
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update
A confirmation whether this works now in 2.2009.51-1 is highly welcome.
(In reply to comment #8)
> A confirmation whether this works now in 2.2009.51-1 is highly welcome.
Thx for remind me.
Works for me. I change the status to Verified.
*** Bug 8264 has been marked as a duplicate of this bug. ***
Can we reopen this bug?
*** This bug has been confirmed by popular vote. ***
Please note that this still does not always work correctly in 2.2009.51-1 - see
bug 6898 about it, as it is a different issue (codewise) than this report here.