No action when clicking connection name (GSM + Wireless)

I have the same problem with:

plasma-widget-networkmanagement: 0.9~svn1029786-0ubuntu2.1~jaunty1

on Kubuntu 9.04 amd64.

Before upgrading this package my GSM (hso) connection works properly.

I can confirm the exact same problem. Clicking to a specific wireless connection results in no response, while clicking on other connections works.

However, I solved the problem by removing the connection from the list of saved connection setups (right click on the plasma widget, then click "Manage connections", and then adding it back again via connection scanning.

I guess the reason must be hidden at how connections are saved or how the saved info is accessed, loaded back and reused.

The same has happened to me before and the same solution worked. As much as I remember the problem reappeared always after updating packaged related to networking. And it has persisted for several update cycles, still persisting at my latest setup:

plasma-widget-networkmanagement = 0.9~svn1029786-0ubuntu2.1~jaunty1
network-manager = 0.8~a~git.20091013t193206.679d548-0ubuntu1

I also tried to create a new GSM connection but it is the same behavior as before - nothing happens when clicking.

I also recreated the GSM connection dozens of time and still nothing
happens. [I aways keep my OS updated]

I also recreated the GSM connection dozens of times and still nothing happens.

maybe my patch will help: https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/334122/comments/44

Is this patch for network-manager? It's weird; my network-manager is working fine here. I just forced the installation of the old plasma-widget-networkmanagement and it's working greatly.

Did anyone tried this patch, anyway?

I did the same. I installed plasma-widget-networkmanagement_0.1~svn1023224-0ubuntu1_amd64 and everything works very well.

For me the problem has gone with plasma-widget-networkmanagement 0.9~svn1040607-0ubuntu1~karmic1~ppa1

Thanks who ever has fixed this :)

Michael, pls ppa where address work plasma-widget-networkmanagement 0.9~svn1040607-0ubuntu1~karmic1~ppa1?
im search if not found :-(

I assume you want to know where to get it from...

I found the package on https://launchpad.net/~kubuntu-ppa/+archive/staging

Yay, I haven't saw that PPA before. Looks great, thanks. :)

The 0.9~svn1040607-0ubuntu1~karmic1~ppa1 doesn't work for me. Still using 0.1~svn1023224. :(

Perhaps some of you are suffering from bug #459052.

I'm unfortunately seeing the same kind of regression problems with the NM plasma widget. My setup is as follows:
* EeePC netbook 901Go with integrated Huawei Technologies E620 USB Modem.
* Kubuntu 9.10 with 2.6.31-17-generic kernel.
* plasma-widget-networkmanagement 0.9~sn1029768+ag1-0ubuntu1
* network-manager 0.8~rc1-0ubuntu1~nmt1~karmic
* KDE 4.3.85

The modem is properly detected by the kernel and the NM plasma widget shows the phone symbol (both task bar as well as in the widget menu). I can click on the menu item for the phone connection and nothing happens. The logs show nothing -- not even an attempt to establish a ppp connection. Removing and creating a new mobile broadband connection does not help, still same situation.

Currently, the only solution is to install Gnome's nm-applet and use that: the Gnome NM applet works flawlessly out of the box; creating the mobile broadband connection is a breeze; connecting also. Sigh. KDE 4 has still a long way to go to mature.

Why is KDE 4.x broken when it comes to mobile broadband and also bluetooth (same situation)?

Is this an upstream KDE issue or a Kubuntu issue? I'm not clear on which person's ballpark this is in ...

@Harald
Unfortunately KDE is very immature when it comes to connectivity.
Try plasma-widget-networkmanagement 0.1, it works for me. If you are not lucky on that too, try pon/poff via terminal (pppconfig can do it all).

I also reproduced this bug on Chakra Linux, so I guess it's KDE.

Unfortunately, UMTSmon and a direkt pppd or wvdial did not work -- I don't know why. nm-applet works out of the box, as knetworkmanager does when it is not broken most of the time.

plasma-widget-networkmanagement 0.9~svn1029768+ag1-0ubuntu1 gives:

knetworkmanager(1876)/Network Management (internals) Knm::Activatable::activate:
knetworkmanager(1876)/Solid (NetworkManager) NMNetworkManager::activateConnection: Activating connection "/org/freedesktop/NetworkManagerSettings/1" on service "org.freedesktop.NetworkManagerUserSettings" on interface "/org/freedesktop/NetworkManager/Devices/33" with extra "/"
knetworkmanager(1876)/kdeui (KNotification) KNotification::slotReceivedId: 0
knetworkmanager(1876)/kdeui (KNotification) KNotification::close: 0
knetworkmanager(1876)/kdeui (KNotification) KNotification::~KNotification: -2

This bug also affects me.

It is the irresponsivity that annoys me the most. If something goes wrong, the applet should tell me so.

My USB mobile broadband device is handled by the hso driver. lsusb outputs:

$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 009: ID 0af0:7501 Option
Bus 001 Device 002: ID 064e:f111 Suyin Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 08ff:1600 AuthenTec, Inc. AES1600
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

this bug bothers me in lucid too, installing backports modules lets knetworkmanager react - a connection won't be established anyways though

in fact, the backports modules where used in karmic recently, there are non in lucid yet. Maybe someone can post NetworkManager output when these modules are installed.
sudo killall NetworkManager && sudo NetworkManager --no-daemon should bring that up. otherwise post cat /var/log/daemon.log |grep NetworkManager (only post the part which is necessary)
nm-applet works without these in karmic and lucid without backports.

ok, deletet and set up the connection again brings a reaction in NetworkManager:
NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4 (reason 0)
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> (ttyUSB0): device state change: 4 -> 6 (reason 0)
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: Tried to set deprecated property gsm/puk
NetworkManager: Tried to set deprecated property gsm/puk
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> (ttyUSB0): device state change: 6 -> 4 (reason 0)
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <WARN> stage1_prepare_done(): GSM modem connection failed: (32) Network ended call
NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9 (reason 1)
NetworkManager: <info> Marking connection 'o2surf' invalid.
NetworkManager: <info> Activation (ttyUSB0) failed.
NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3 (reason 0)
NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).

but no connection

Sorry for spamming

sorry again - put in the wrong number

so i can say, it works in lucid - just the connection has to be deleted and set up again

for me it doesn't work in lucid, no reaction when I click on a connection, even not on the auto eth0
Nothing in the daemon.log (gnome's nm-applet works ok)

Same problem on 10.10. Nothing happens if yo don't put it a login/password and if you do, it just fails and never connects.
Modem works fine with kppp