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
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
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
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
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
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
I have aessa issue too since Kubuntu Dapper, and I have it too into
8.04.1
--
KNetworkManager dialup menu expands to thin empty box
https://bugs.launchpad.net/bugs/211932
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same situation of Florian (openvpn too)
--
KNetworkManager dialup menu expands to thin empty box
https://bugs.launchpad.net/bugs/211932
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
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
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.
--
KNetworkManager dialup menu expands to thin empty box
https://bugs.launchpad.net/bugs/211932
You received this
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
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.
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
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.
--
KNetworkManager dialup menu expands to thin empty box
https://bugs.launchpad.net/bugs/211932
You received this
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.
--
KNetworkManager dialup menu expands to thin empty box
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
Can confirm this on Hardy with knetworkmanager 0.2.2
It seems knetworkmanager does not properly get list of configured dialups from
kpp.
** Changed in: knetworkmanager (Ubuntu)
Status: New = Confirmed
--
KNetworkManager dialup menu expands to thin empty box
I am also seeing this bug. Have to dial up via the configuration menu...
I'm not always at a WLAN AP.
--
KNetworkManager dialup menu expands to thin empty box
https://bugs.launchpad.net/bugs/211932
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Screenshot of the described condition
http://launchpadlibrarian.net/13118233/knetworkmanger.png
--
KNetworkManager dialup menu expands to thin empty box
https://bugs.launchpad.net/bugs/211932
You received this bug notification because you are a member of Ubuntu
Bugs,
20 matches
Mail list logo
