kppp does not set KDE network status to "online"

Bug #193907 reported by Kai Blin on 2008-02-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
knetworkmanager (Ubuntu)

Bug Description

Binary package hint: kppp

When dialing in via kppp, the KDE network status is not updated to reflect the fact that the computer is now online. This causes apps like konqueror or kmail to refuse to do network operations.

This can be checked as follows:

1. Dial in via kppp
2. Run "dcop kded networkstatus status foo", which returns 6.
3. Try opening a website in konqueror or check emails in kmail, konqueror will fail and kmail will claim it's finished without doing anything.
4. Run dcop kded networkstatus setNetworkStatus `dcop kded networkstatus networks` 8
5. Retry step 2, should now return 8. If not, network manager is playing up again, see comment below,
5. Retry step 4, both operations will now work.

Sometimes you have to kill NetworkManager to have the network status stay set on 8, I haven't been able to identify a pattern there, though. Sometimes the network status will revert back to 6 right away, sometimes only when you try to access the network and sometimes the network status will just behave and stay on 8. Killing network manager makes sure the online status will keep the value that was set manually.
This is sort of related to the wishlist in bug #133814 as this seems to be an interaction between kpp and network manager.

Observed on Kubuntu 7.10 with KDE 3.5.8, kppp 4:3.5.8-0ubuntu2, network-manager 0.6.5-0ubuntu16.7.10.0, knetworkmanager 1:0.2ubuntu1-0ubuntu5

Christian González (droetker) wrote :

confirmed on Kubuntu hardy beta., KDE 3.5.9
It is impossible to get into internet with kppp/Konqueror using a huawei modem.
the setup is clean, UMTS modem connects, I can ping, Firefox can access the internet.

But Konqueror and Kmail, as describe above, not.

This is a serious bug, as it prevents many people using today's common UMTS modems with Ubuntu.

Christian González (droetker) wrote :

maybe this is a networkmanager bug.
if you close Networkmanager, Konqueror sees the connection.

Kai Blin (kai.blin) wrote :

I still think that this should work if kppp properly told network manager it was online. I don't know what causes NetworkManager to fall back to "offline" status even after manually setting it to "online" using the dcop command I mentioned.

Pitabred (ubuntu-pitabred) wrote :

I will also confirm this bug, and note that the dialer in knetworkmanager starts up kppp somehow differently than normal. I'll check for a bug under knetworkmanager regarding that, though.

lophiomys (lophiomys) wrote :

Confirmed on Kubuntu Hardy, all updates up to 22.May.2008, KDE 3.5.9
Linux T42p 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

Reproduced with a working UMTS connection using a Huawei E220 USB Modem, connected via KPPP ( ttyUSB0 - PPP0)

Using KPPP (via KNetworkmanager-Dial Up Connection or via directly opening KPPP)
 the Huawei modem connects sucessfully, activating interface PPP0,
 but KNetworkManager and Konqueror do not reflect the active connection.
KNetworkManager shows the "disconnected" status.
Only FireFox 3.0 Beta5 connects to the "Internet" after DEactivating "Offline Mode".

Seems to be related to or a duplicate of

lophiomys (lophiomys) on 2008-05-22
Changed in knetworkmanager:
status: New → Confirmed
Changed in kdenetwork:
status: New → Confirmed
lophiomys (lophiomys) wrote :

Confused project "Knetworkmanager nederlandse vertaling" with correct Package "kdenetworkmanager" in Distribution/Project "Ubuntu"
Set to Invalid, because I cant delete it.
Admins please delete this association to "Knetworkmanager nederlandse vertaling"

Changed in knetworkmanager:
status: Confirmed → Invalid
status: New → Confirmed
Kai Blin (kai.blin) wrote :

This is all connected to the network manager online status. As to the workaround, see my bug description. At least on my laptop, I can't always make the network stay connected. An easier workaround is to just close the network manager application.

KPPP isn't the only thing that needs to be changed; umtsmon also starts up pppd. Perhaps a better solution is to emit the appropriate dbus message through the /etc/ppp/ip-up and /etc/ppp/ip-down scripts?

Luis F. Lopez (luis.lopez) wrote :

Andrew is right, the issue is with knetworkmanager...

Also, the workaround mentioned before:

Can be easily implemented in kppp using the execute tab.

Jonathan Thomas (echidnaman) wrote :

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.

Changed in knetworkmanager (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers