Dear Maintainer,
As of recent KDE version, KDE relay on ntrack to check if there are
any network connections. if wvdial is run after a login had been done KDE
apps will behave as if there is no internet connection.
quering solid connection state will be answerd with state 1 (not
connected).
bad state:
qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.status
1
good sate:
qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.status
4
* What led up to the situation?
Upgrade to a recent KDE (4.14)
* What exactly did you do (or not do) that was effective (or
ineffective)?
If wvdial is run after a login, solid is not aware of a network
connection, hence all KDE apps behaving as if there is no network
connection.
If wvdial is run before a login, all is ok.
* What was the outcome of this action?
KDE apps behave as if there is no internet connection
* What outcome did you expect instead?
KDE apps aware of the network connection.
* Workaround
execute as a logged in user:
qdbus org.kde.kded /modules/networkstatus \
org.kde.Solid.Networking.setNetworkStatus ntrack 4
related KDE bugs :
https://bugs.kde.org/show_bug.cgi?id=312595
https://bugs.kde.org/show_bug.cgi?id=322602
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717484