#717484 akregator: Akregator does not update feeds, reports "Networking is not available"

Package:
akregator
Source:
akregator
Description:
RSS/Atom feed aggregator
Submitter:
Philipp Hagemeister
Date:
2021-04-19 17:21:11 UTC
Severity:
important
Tags:
#717484#5
Date:
2013-07-21 10:33:18 UTC
From:
To:
akregator does not update feeds when I click "Fetch All Feeds"; the status bar
shows "Networking is not available.". I can browse the Internet just fine; I
have unrestricted IPv4 and IPv6 address and DNS resolution works fine. I am not
using any network managers.

#717484#10
Date:
2013-07-21 10:44:34 UTC
From:
To:
Hi,

Alle domenica 21 luglio 2013, Philipp Hagemeister ha scritto:

Does this happen any time, or (for example) after resuming from suspend?
Can you please paste the outputs of the following commands:
$ qdbus org.kde.kded /modules/networkstatus networks
$ qdbus org.kde.kded /modules/networkstatus status

Thanks,

#717484#15
Date:
2013-07-21 11:27:19 UTC
From:
To:
It has happened multiple times (so before and after I rebooted), and
most of the times after a suspend (but that's just because I'm using
suspend twice or three times a day, and only rebooting every couple of
months or so). I've tried it out a little bit: Akregator seems to
update itself just after the resume. I can't reboot right now
(long-running process without statefile :( ), but I'll try to
reproduce the problem just after a reboot asap.

$ qdbus org.kde.kded /modules/networkstatus networks
SolidNetwork
ntrack
$ qdbus org.kde.kded /modules/networkstatus status
1

Thanks for the fast reply!

- Philipp

#717484#22
Date:
2013-07-21 12:33:26 UTC
From:
To:
Alle domenica 21 luglio 2013, Philipp Hagemeister ha scritto:

Ok, so both at login after boot and after resume, but not always.
I see you already reported it upstream [1]; there was also an existing
bug [2] although that says explicitly about resuming (only).

[1] https://bugs.kde.org/show_bug.cgi?id=322602
[2] https://bugs.kde.org/show_bug.cgi?id=312595

Hm, it'd seem like the ntrack backend explicitly reports "not connected"
somehow, not sure why (especially if you say that you are connected fine
-- and the ntrack libraries do not provide utilities).
In the meanwhile, you could try to manually set a connected state for
the SolidNetwork network:
$ qdbus org.kde.kded /modules/networkstatus setNetworkStatus \
   "SolidNetwork" 4

#717484#27
Date:
2013-07-21 12:59:43 UTC
From:
To:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Thanks, I know where to look then and will examine what ntrack is doing.

Excellent, this workaround lets Akregator update feeds again. Thanks
for the help!

iQIcBAEBCgAGBQJR69m7AAoJENtLVMukgmoYumMP/2SjtbKFjAlPlMCx0plqiOtv
OHkeTuj80rLLl97u0xKoIHRr7LFfI1FZFYXToU+hT19i3znj8lxVwBTjUtXXhxDj
OwH6OewlcNud29xn7L/lcjYZILX71HqMM2N2WsjiLsGxZOlgz2DITVB4zZIjHzUM
FokK8kwEgJ4ABHd4BrpUISazEQXoUmgdJuXoMAsKsAk7rHN8/eWNsGexlb5ZQ59D
KyyIr+o9Whc2w+eeWHUjqr/NQSw4xsX5E/QdmgKnBsWsCits+pETnPvceWVfGt3D
4c77HJNYjBOkXcCQiph2wM72nMkNuYoa6tDnBv8woRirJMTcJ8LF/uve/PixRg8n
gAsbRfzTyVCgT0Tf2Jr7UN4s1rFnXoO+LnUQqFQVwSHDzCySONWFx5fnsd/qZ47F
vAfPzS77BHJgCnsrHObYAHxoemZMywh5KACXWxmW4Frfk4AykF9GAKQpk9h3tpIl
/G8E9AuqV+3bfF2C8M+cCQqxnNLwSgLTiBzjE/W0yM6AL70Bqu/taiyIRx2LAccI
jTh6WH0oE4nNT6EDLmk8/6UJsUknDFOpR7b6z1Bl5Z2Tp3dUqbaW8k9lhy7wx2zi
FxxlS1JPzv47Sq7RzQfQHGP/uh+e08NqVUEgy7Unjsir0nVjo4lBjdizEVB7qngK
esLcv4H51aOrHzt3f5+n
=05TO
-----END PGP SIGNATURE-----

#717484#32
Date:
2014-02-17 14:10:01 UTC
From:
To:
Hello,

I have the same issue with Akregator.

  $ qdbus org.kde.kded /modules/networkstatus networks
ntrack
  $ qdbus org.kde.kded /modules/networkstatus status
1

With current testing version, I tried the workaround
  $ qdbus org.kde.kded /modules/networkstatus setNetworkStatus "SolidNetwork"
4

but Akregator still reported Network is not available and
   $ qdbus org.kde.kded /modules/networkstatus status
1

Reading https://bugs.archlinux.org/task/28850 I found an alternative command
that actually works:

  $ qdbus org.kde.kded /modules/networkstatus
org.kde.Solid.Networking.setNetworkStatus ntrack 4
  $ qdbus org.kde.kded /modules/networkstatus status
4


https://bugs.kde.org/show_bug.cgi?id=226022#c11 provides some insights about
it and a general web search about "org.kde.kded /modules/networkstatus ntrack"
does not look so good (many KDE apps having the same problem that all seems to
pinpoint to this ntrack). Let's hope they'll fix that upstream.

Regards,

#717484#37
Date:
2014-10-11 11:21:43 UTC
From:
To:
I have the same issue with Akregator (4:4.14.1-1)

`killall kded4` works as workaround.