Bug 200723 - remember the milk widget does not update after KDE start
Summary: remember the milk widget does not update after KDE start
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-rememberthemilk (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Andrew Stromme
URL:
Keywords:
: 216542 216543 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-19 01:34 UTC by Chirag Anand
Modified: 2011-08-12 14:08 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chirag Anand 2009-07-19 01:34:03 UTC
Version:            (using KDE 4.2.95)
OS:                Linux
Installed from:    SuSE RPMs

if there is no internet connection at kde start (as network manager connects late), the remember the milk widget does not get updated even after the internet is connected. I have to remove it from plasma and add again to get it working.
Comment 1 Steffen Schloenvoigt 2009-07-20 10:38:25 UTC
This may be related to bug 199224. Probably the same issue. Occurs to me, too. The Plasmoid displays a button saying "Login Failed. Please try again." But pressing this button doesn't work (In fact it does nothing at all).
Comment 2 Piotr Budny 2009-08-05 22:32:30 UTC
Got this same on KDE 4.3.0. 
Plasmoid does not try to connect again, when there were no internet at the kde start.
Comment 3 geekonek 2009-08-10 22:19:19 UTC
Same here on 4.3.0.
Comment 4 Keith Brown 2009-09-08 22:40:27 UTC
Still in KDE 4.3.1
Comment 5 Lex Rivera 2009-10-15 13:56:57 UTC
can confirm that bug.
Comment 6 capi /. etheriel 2009-11-07 12:16:31 UTC
still in kde 4.3.3
confirmed bug in Arch.
Comment 7 yo.defender 2009-11-12 10:31:50 UTC
still not fixed
Comment 8 Giulio Guzzinati 2009-11-23 19:29:26 UTC
This is very annoying.

If I'm not connected to the internet at the time I login, which is usually the case for wifi connections which are initiated by networkmanager, the plasmoid does not connect.

Also if I add a task from a phone or another machine I have to delete/add the plasmoid or to logout/login to get the changes on my desktop.

An option to make the plasmoid check the server every 10 minutes or so would probably be enough for most people.

Arch and KDE 4.3.3 here.
Comment 9 Kolia 2010-01-03 02:15:57 UTC
Hi,

Not sure to understand the problem.

Once you get the internet connection on, you can not login in the RTM plasmoid, or the plasmoid does not login automatically but you can do it manually via the settings (clicking the "Authenticate..." button) ?
Comment 10 Giulio Guzzinati 2010-01-03 12:53:58 UTC
That is exactly the point. If the plasmoid finds no connection it makes no other attempt, and it is necessary to open the settings page and enter the password every time.

Although I must say I didn't see this bug in a while so it might be gone with KDE SC 4.3.4.
Comment 11 Beat Wolf 2010-01-06 12:37:52 UTC
was this fixed? thank you
Comment 12 Andrew Stromme 2010-02-14 05:44:23 UTC
I've implemented a basic hacky way of retrying the connection. This should fix this bug in most cases but the real fix requires some api changes to librtm that will need to wait for 4.5 (and for me to have more time). 

The relevant fix is in svn revision 1089813. This didn't make it in time for 4.4.0, but it is backported and should be present in 4.4.1
Comment 13 Andrew Stromme 2010-02-14 06:17:53 UTC
SVN commit 1089821 by astromme:

CCBUG: 200723 Handle the offline/transient offline case much better by retrying every 60 seconds rather than failing immeadiately

 M  +5 -0      request.cpp  
 M  +1 -0      request.h  
 M  +2 -0      session.cpp  
 M  +2 -0      session.h  
 M  +18 -1     session_p.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1089821
Comment 14 Nicolas L. 2010-06-07 10:21:06 UTC
commit 1089821 have not been backported, is it possible to do so ?
Comment 15 Nicolas L. 2010-06-07 18:32:35 UTC
*** Bug 216543 has been marked as a duplicate of this bug. ***
Comment 16 Nicolas L. 2010-06-07 18:32:55 UTC
*** Bug 216542 has been marked as a duplicate of this bug. ***