KNetworkManager dialup menu expands to thin empty box

[Ryan Novosielski]

I have dialup configured through the configure menu in KNetworkManager. Still, when I go to the Dialup Connections menu, it expands to a thin box with some corrupt type of image in them.

Don't know what the problem is. Version is 0.2 for KDE 3.5.9, in Hardy.

[Sami Mäkinen (sami-makinen-helsinki)]

I am also seeing this bug. Have to dial up via the configuration menu... I'm not always at a WLAN AP.

[Luka Renko (lure)]

Can confirm this on Hardy with knetworkmanager 0.2.2
It seems knetworkmanager does not properly get list of configured dialups from kpp.

[Pitabred (ubuntu-pitabred)]

I will also confirm this.

Note that starting KPPP from the menu somehow has kppp with a different configuration set than if you configure the dial-up connections from within knetworkmanager. But even configuring a working dial-up connection from within knetworkmanager doesn't show up in the dial-up connections list. A connection made with <a href="https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/193907">kppp also does NOT set the network state in KDE to "on"</a> (either kppp by itself or started through knetworkmanager), so Konqueror cannot connect to the Internet while using dial-up. Firefox is fine, if you override the "File->Work Offline" setting.

[yobser (yobser)]

Confirm this on Hardy with knetworkmanager 0.2.2
And I found one more bug.
There are two ways two add ppp connection: knetworkmanager settings and kppp settings. And if I make connection in thw first I cannot see it in the second.

[Ryan Novosielski (novosirj)]

yosber: This is not really a bug. The connections added from knetworkmanager are added to root's account (notice the kdesudo box) and connections via kppp go into your own account.

[lophiomys (lophiomys)]

Confirmed on lastest Kubuntu Hardy, with all updates to date.
I have set up two KPPP connections:
a) as root via KNetworkmanager - context menu - Options - Configure - Dial-up Connections - ...
b) as user directly via KPPP
None of the two show up in the sub-menu of "Dial-up Connections" in the context menu of KNetworkManager.
That's why I would confirm this as a real bug.

[Alexander Schmidt (atzeschm)]

I also have this problem, but I don't think it is caused by KNetworkManager. KNetworkManager tries to get the available DialUp connections from networkmanager via Dbus, and networkmanager responds that there are no available connections on my system. I tried the following command:

dbus-send --system --dest=org.freedesktop.NetworkManager --print-reply --type=method_call /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.getDialup

And it returns:

Error org.freedesktop.NetworkManager.NoDialup: There are no available dialup devices.

[Ryan Novosielski (novosirj)]

Thank you for helping to pinpoint the location. I guess then the issue is
really possibly with kppp, which I'm not certain supports dbus. It should
be pretty easy to find out though. This jives with what the KNetworkManager
maintainer just told me yesterday on the kde-networkmanager list.

...... Original Message .......
On Fri, 06 Jun 2008 13:52:26 +0000 "Alexander Schmidt"
<email address hidden> wrote:
>I also have this problem, but I don't think it is caused by
>KNetworkManager. KNetworkManager tries to get the available DialUp
>connections from networkmanager via Dbus, and networkmanager responds
>that there are no available connections on my system. I tried the
>following command:
>
>dbus-send --system --dest=org.freedesktop.NetworkManager --print-reply
>--type=method_call /org/freedesktop/NetworkManager
>org.freedesktop.NetworkManager.getDialup
>
>And it returns:
>
>Error org.freedesktop.NetworkManager.NoDialup: There are no available
>dialup devices.
>
>--
>KNetworkManager dialup menu expands to thin empty box
>https://bugs.launchpad.net/bugs/211932
>You received this bug notification because you are a direct subscriber
>of the bug.

[Camiguin (camiguin)]

I am experiencing exactly the same bug as described, including the return of the dbus-send command above. I am posting this just to be in the mailing list for any solution. Thanks.

[Martin (lodp)]

Same here. Like lophiomys above, I've got dial-up connections set up on both my user account as well as the root account (having gone through the "Configure Dialup Connections" button in the knetworkmanager settings).

Would be cool if knetworkmanager could handle dial-up connections as well. Just as a matter of convenience. Why have that "Dial-up connections" menu item if it doesn't work and never has (if I'm getting the situation right)?

[Florian (floeschie)]

Same here!

I tried to configure a (3G) dial-up connection with knetwormanager/kppp (as root) without success. The configured dial-up connection does not show up in the list.

Using same configuration options with kppp stand-alone (as normal user) everything works fine, but I cannot connect to an openvpn network via knetworkmanager 'cause it thinks I'm offline...

Hope this will be fixed soon, any workaround appreciated!

Regards,
Florian

[kirys (kirys)]

Same situation of Florian (openvpn too)

[Aessa (aessa)]

One more confirmation of this scenario. Kubuntu 8.04.1.
For what it's worth, I run kppp as my normal user to make a bluetooth dialup connection. For the rest of KDE to notice that there is a gateway available I must quit knetworkmanager. Then it all works fine. I have not tried kppp as root via knetworkmanager, but suspect that the same thing will happen.

[kirys (kirys)]

I have aessa issue too since Kubuntu Dapper, and I have it too into 8.04.1

[Sami Mäkinen (sami-makinen-helsinki)]

This issue does not appear to be present in Kubuntu Intrepid 8.10.

The network manager in KDE 4.1 does not seem to support dialup connections at all!

KPPP can be found separately in the startup menu, and it prompts for a password when started, so I suppose it runs as root even though started from a regular user's K menu.

However since bluetooth support seems to be completely broken in Intrepid I can't actually test PPP.

Since KDE 3 I guess is not really being developed anymore, this issue could be changed into a feature request for KDE 4, to include this feature and make it work correctly.

[Sami Mäkinen (sami-makinen-helsinki)]

Hah, managed finally to get a dialup connection, after using the Gnome bluetooth applet to re-establish mobile pairing.

Result: KPPP manages to create a functional dialup connection. Network Manager is not aware of this connection - it is only visible via KPPP or ifconfig.

So: KDE bluetooth applet is broken, and KDE network manager does not support dialup connections. Should I file separate new bug reports on both issues, since this bug report is really about KDE 3 and thus quickly becoming obsolete?

[sven-ola (sven-ola)]

The network-manager dbus backend for Debian reports only configured dial-up connections from the interfaces file. You need to configure a ppp connection manually, something like this:

/etc/network/interfaces:
iface ppp0 inet ppp
        provider Congstar_UMTS_Bluetooth

/etc/ppp/peers/Congstar_UMTS_Bluetooth:
user t-mobile
connect "/usr/sbin/chat -v -f /etc/chatscripts/Congstar_UMTS -T *99***1#"
/dev/rfcomm0
921600
noipdefault
usepeerdns
defaultroute
persist
noauth

/etc/chatscripts/Congstar_UMTS:
ABORT BUSY
ABORT VOICE
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
"" ATZ
OK AT+CGDCONT=1,"IP","internet.t-mobile","0.0.0.0",0,0
OK ATDT\T
CONNECT ""

/etc/ppp/pap-secrets:
"t-mobile " * "tm"

/etc/bluetooth/rfcomm.conf:
rfcomm0 {
        bind yes;
        device 00:19:63:11:f7:c6;
        # channel 1 does not work for me!
        channel 2;
        comment "SonyEricsson K610i";
}

HTH
// Sven-Ola

[sven-ola (sven-ola)]

Addon: there's another quirks with dial-up (see Bug #293139): nm does not report "online" to apps if a dialup connection is established. Found also no good way to force online e.g. by dbus-send while the dev-list mentions that nm-0.7 may fix this. Because in kubuntu/intrepid, the bluetooth support is really rotten this is no option for my netbook.

As a temp solution (until kubuntu jaunty or so), you can add "auto eth0" and "iface eth0 inet dhcp" to /etc/network/interaces which removes eth0 from network-manager (verify this by starting "nm-tool" on cmd line). In this way nm does not report eth0 status and will stay online even if wifi is disconnected. You loose the display icon switching from [x] to [modem] and the [gray plug] is show if no wifi, but you can use VPN with dial-up as well then.

HTH
// Sven-Ola

[Jonathan Thomas (echidnaman)]

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.