Bug 429606

Summary: Panel widgets are offline
Product: [Plasma] plasmashell Reporter: Don B. Cilly <donbcilly>
Component: PanelAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.20.3   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Don B. Cilly 2020-11-24 21:15:53 UTC 
SUMMARY
Any panel icons that require an internet connection don't work. Notably the updates (it shows a broken cable) icon and the weather widgets.
If I click on Updates, it does open up Discover (which I never use, but it does), and it does fetch the updates. So it _is_ the panel, isn't it. 

STEPS TO REPRODUCE
1. Boot normally :·)
2. 
3. 

OBSERVED RESULT
See here: https://i.ibb.co/hVxZK9p/nwo.png

EXPECTED RESULT
They worked fine until three days ago.

SOFTWARE/OS VERSIONS


KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
KDE neon User (20.04 base)

After a few forum inquiries, it *seems* I'm the only one on the planet getting this. Still, they used to work, they now don't,
Comment 1 Nate Graham 2020-12-01 01:33:20 UTC 
And  I suppose your internet connection is otherwise working?

If you restart plasmashell by running `plasmashell --replace`, does it start working?
Comment 2 Don B. Cilly 2020-12-01 09:34:57 UTC 
Internet connectivity is 100% for *everything* else.
If I restart plasmashell by running `plasmashell --replace`, it does *not* start working.

Would you like the konsole output of that?
Also, as I've stated, the Updates icons shows "offline", but clicking it does call up Discover and they do work.
Comment 3 Nate Graham 2020-12-01 15:41:15 UTC 
Well that's odd.

Is the clock in the panel displaying the correct time?
Comment 4 Don B. Cilly 2020-12-01 15:59:10 UTC 
It is, but it wouldn't go off by much in a week or so, would it?
Comment 5 Nate Graham 2020-12-01 16:07:09 UTC 
Thanks.
Comment 6 Don B. Cilly 2020-12-06 09:57:38 UTC 
Installing network-manager seems to have fixed it.
Which would explain why just about nobody else had it.
I don't use nm, I use systemd-networkd instead. :·/