*** Bug 220841 has been marked as a duplicate of this bug. ***

I experience the same problem in KDE SC 4.5 Beta 1, every time after boot, the weather forecast plasmoid is just a blue question mark, saying "please configure" and I get a message that the action to get the weather has timed out.
I solve this by going to the plasmoid settings and just clicking ok since my town (Edmonton, AB), is already entered. The provider is not BBC but iGoogle.

SVN commit 1169287 by asouza:

Make weather dataengine work if started without network

Always call setData() using the original source so it's initialized
and when we reset the ions, they have sources connected to them and are
able to communicate back.

Also, fix the ions to update their data into the weather engine and later
emit the signal that will make the engine force the clients (plasmoids) to
update using the new data.

This mostly fix the problem of turning the computer on without network,
getting network later and the weather plasmoids not updating.

CCBUG: 226022
CCBUG: 245639


 M  +5 -1      envcan/ion_envcan.cpp  
 M  +9 -3      ion.cpp  
 M  +5 -1      noaa/ion_noaa.cpp  
 M  +9 -1      wetter.com/ion_wettercom.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1169287

SVN commit 1170055 by asouza:

backporting r1169287

Make weather dataengine work if started without network

Always call setData() using the original source so it's initialized
and when we reset the ions, they have sources connected to them and are
able to communicate back.

Also, fix the ions to update their data into the weather engine and later
emit the signal that will make the engine force the clients (plasmoids) to
update using the new data.

This mostly fix the problem of turning the computer on without network,
getting network later and the weather plasmoids not updating.

CCBUG: 226022
CCBUG: 245639



 M  +5 -1      envcan/ion_envcan.cpp  
 M  +9 -3      ion.cpp  
 M  +5 -1      noaa/ion_noaa.cpp  
 M  +9 -1      wetter.com/ion_wettercom.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1170055

Thanks for the fix! In Kubuntu Maverick this suddenly started (mostly) working for me with updates that must have been released sometime towards the end of April.

However,  for me the fix is partial.
What works: I log in, but the network is not yet available. I start the wireless network via KNetworkManager, and very soon thereafter the weather applet updates itself. Hurray!

What doesn't work: then, I put my laptop to sleep, head in to work, and connect to the wired network (static IP). The weather applet no longer updates every 30 minutes. Moreoever, at the end of the day if I put my laptop back to sleep, disconnect, head home, and reconnect to my home's wireless network, the weather applet still fails to update. (Currently it is Saturday, but the weather applet is still showing the forecast for the previous Wednesday.) So it seems that it's been fixed for the case when the network wasn't initially available at all, but the more general problem of a temporary network change or disruption still seems problematic.

Weather isn't updating for me any time after resuming from sleep, and on a desktop always connected to the internet.

*** Bug 251481 has been marked as a duplicate of this bug. ***

*** Bug 241768 has been marked as a duplicate of this bug. ***

*** Bug 273182 has been marked as a duplicate of this bug. ***

sounds like solid isn't telling us about the network connectivity on these devices.

kded's networkstatus module supports three backends: NetworkManager, ntrack and Wicd (this one since 4.7.2). Ntrack is the only backend that could detect interfaces started by wvdial (and Kppp for the matter).

Networkstatus' Ntrack backend is only compiled if ntrack library is installed when kde-runtime is compiled. Most distributions do not do that, so in my most cases ntrack backend is disabled.

Ntrack has a history of causing problems for networkstatus module. I, for one, had to recommend uninstalling it to several people who had instability problems.

One workaround for this problem is executing the command below at each login:

qdbus org.kde.kded /modules/networkstatus setNetworkStatus SolidNetwork 4

0 = Unknown
1 = Unconnected
2 = Disconnecting
3 = Connecting
4 = Connected

that will mark the KDE session as Connected.

You can even add that script to /etc/ppp/ip-up.d/ and another one to /etc/ppp/ip-down.d/ to set the networkstatus to unknown (or leave it online if there is another active Internet connection). Actually the script will have to be more complex because qdbus requires DISPLAY to be set so that it can talk to org.kde.kded :-/

As for the problem in comment #5 I fixed it one month ago and is available since 4.7.2:

https://projects.kde.org/projects/kde/kde-runtime/repository/revisions/987e18493c26ea52ca9ca216e4083a6fabb95092

*** Bug 282766 has been marked as a duplicate of this bug. ***

Hi Lamarque & Aaron,

I apologize for not being in a position to easily test your very promising-sounding work on this bug---I am still running Maverick and a bit reluctant to upgrade (basically, because of more scary-sounding bugs in recent Ubuntu releases I'm probably waiting until the next LTS). If I get a chance to try it out on a less mission-critical machine than my own laptop, I will let you know what happens.

However, even before verifying that it all works now, I want to sincerely thank both of you for your time and attention to this bug.  Your work extending & solidifying KDE's behavior makes an enormous difference to large numbers of people. I look forward to seeing the differences first-hand!

Best wishes,
--Tim

*** Bug 282766 has been marked as a duplicate of this bug. ***