Created attachment 66333 [details] open it for a complete issue description Version: unspecified (using KDE 4.7.3) OS: Linux I'm using the Huawei USB Modem – model E156G. $ lsusb | grep 'Huawei' Bus 001 Device 010: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270 HSDPA/HSUPA Modem In order to work with the modem, I try with different usb_modeswitch options with no success. $ dmesg | grep 'error' | tail [ 1908.581429] option: option_instat_callback: error -108 So I'm able to make it running adding "cdc-acm" module to modprobe blacklist (assuming to work with "vim" editor): $ sudo vim /etc/modprobe.d/blacklist.conf adding the text: blacklist cdc_acm, and using "usbserial" module as option: $ sudo vim /etc/modprobe.d/options.conf adding the text "options usbserial". And at the moment I can manage mobile broadband connection only if I start the system with the dongle plugged-in before power-on, even if I tryied several options with udev.rules. But the nm-applet can't remember the PIN: the requester appears each time at login time. Then, I must always enable mobile broadband device, even if I used it before. Finally, if I try to manage connection, I receive the error "No agents were available for this request" and I notice that the PIN is not properly registered. As reported above, now if I physically disconnect the dongle and I connect it again, I cant see the modem anymore and mobile broadband section disappears from nm-applet. Reproducible: Always Steps to Reproduce: Plug-in the modem. System power-on. Fill the requester with PIN, root password (now you can work with the modem). Go to nn-applet in system tray and Manage Connection | Mobile Broadband tab. Select "Modify" --> Error message: "No agents were available for this request." Actual Results: When you unplug the modem, the only way to work with it is to repeat the above steps. Expected Results: I can unplug the modem, plug it again and work with it without problem (as I can with previous KDE version). Please see the doc in attachment.
Firstly nm-applet is the name of another program. The program you are using is called Plasma NetworkManagement, or Plasma NM for short. Please do not mix the names. I was just about to close this bug as invalid since we do not develop nm-applet. The "No agents were available for this request" appears because the password field is empty. Although most operators uses bogus passwords, they are still required sometimes and always triggers this message if not supplied. See bug http://bugs.kde.org/283204 The fact the modem only works if already plugged in when booting the system is an upstream bug. You should contact NetworkManager/ModemManager developers about that. Plasma NM deals with the communication between users and NetworkManager/ModemManager only. That problem you have is probably a driver issue or a problem in ModemManager. We do not develop neither of those two, you must contact who develops them for correct support. Plasma NM does not save the PIN by default because the PIN is exclusive for the SIM card, not the modem. If you exchange the SIM card in your modem Plasma NM would try to unlock it using the wrong PIN and eventually locks your modem for good. You would be required to enter the PUK code to unlock it. So to minimize that kind of problem we do not save the PIN by default. You can change that in the GUI but them you are will be taking the risk of locking your modem. Be warned about that and do not complain here if that happens. By what I see in the screenshots in the attachment you are using a very old version of Plasma NM that lacks the option to save the PIN. You must upgrade. The other problem where you need to click on "Enable Mobile Broadband" before using the modem is also (mostly) due to the old Plasma NM version you are using. There are still modems that require checking "Enable Mobile Broadband" before use and we cannot do much about that since it is NetworkManager that disables all modems by default to save power when they are plugged.
(In reply to comment #1) > Firstly nm-applet is the name of another program. The program you are using is > called Plasma NetworkManagement, or Plasma NM for short. Please do not mix the > names. I was just about to close this bug as invalid since we do not develop > nm-applet. First of all, thank you for your reply Lamarque. Sorry for my misunderstanding. > > The "No agents were available for this request" appears because the password > field is empty. Although most operators uses bogus passwords, they are still > required sometimes and always triggers this message if not supplied. See bug > http://bugs.kde.org/283204 > > The fact the modem only works if already plugged in when booting the system is > an upstream bug. You should contact NetworkManager/ModemManager developers > about that. Plasma NM deals with the communication between users and > NetworkManager/ModemManager only. That problem you have is probably a driver > issue or a problem in ModemManager. We do not develop neither of those two, you > must contact who develops them for correct support. Can you address me to them, please? How can I, through bugs.kde.org? > > Plasma NM does not save the PIN by default because the PIN is exclusive for the > SIM card, not the modem. If you exchange the SIM card in your modem Plasma NM > would try to unlock it using the wrong PIN and eventually locks your modem for > good. You would be required to enter the PUK code to unlock it. So to minimize > that kind of problem we do not save the PIN by default. You can change that in > the GUI but them you are will be taking the risk of locking your modem. Be > warned about that and do not complain here if that happens. > > By what I see in the screenshots in the attachment you are using a very old > version of Plasma NM that lacks the option to save the PIN. You must upgrade. What is the latest version of Plasma NM and how can I verify the version of Plasma NM? In my Kubuntu I found: $ aptitude show plasma-widget-networkmanagement | grep Vers Versione: 0.9~svngit.nm09.20110610.0c83d8-0ubuntu5 Can you suggest some PPA in order to upgrade Plasma NM, since I prefer to use a debian package? If I don't have any option, then I will compile it. > > The other problem where you need to click on "Enable Mobile Broadband" before > using the modem is also (mostly) due to the old Plasma NM version you are > using. There are still modems that require checking "Enable Mobile Broadband" > before use and we cannot do much about that since it is NetworkManager that > disables all modems by default to save power when they are plugged.
(In reply to comment #2) > (In reply to comment #1) > > The fact the modem only works if already plugged in when booting the system is > > an upstream bug. You should contact NetworkManager/ModemManager developers > > about that. Plasma NM deals with the communication between users and > > NetworkManager/ModemManager only. That problem you have is probably a driver > > issue or a problem in ModemManager. We do not develop neither of those two, you > > must contact who develops them for correct support. > > Can you address me to them, please? How can I, through bugs.kde.org? You should open a bug report in http://bugs.gnome.org and / or contact the developers in NetworkManager's mailing list: http://mail.gnome.org/mailman/listinfo/networkmanager-list. > What is the latest version of Plasma NM and how can I verify the version of > Plasma NM? In my Kubuntu I found: > > $ aptitude show plasma-widget-networkmanagement | grep Vers > Versione: 0.9~svngit.nm09.20110610.0c83d8-0ubuntu5 The latest is Plasma NM 0.8.98: http://lamarque-lvs.blogspot.com/2011/11/plasma-nm-0898.html The best way to check the version number is using the configuration module, just click on "Manage Connections" button and go to the tab named "Other". There should be a string "Version: ..." there. Unfortunately most distributions do not use the official version mumber in their packages yet, so it is better look in the configuration module to be sure of the version number. > Can you suggest some PPA in order to upgrade Plasma NM, since I prefer to use a > debian package? If I don't have any option, then I will compile it. I am not aware of any PPA. I myself do not provide compiled packages, only source code.
Created attachment 66418 [details] Any "Version" string Any "Version" string, I'm sorry. Could be due to an old version of Plasma NM?
(In reply to comment #3) > The best way to check the version number is using the configuration module, > just click on "Manage Connections" button and go to the tab named "Other". > There should be a string "Version: ..." there. Unfortunately most distributions > do not use the official version mumber in their packages yet, so it is better > look in the configuration module to be sure of the version number. Thank you again Lamarque, but I'm not able to find any "Version" string there (see attachment)... anyway I will try with the latest Plasma NM. All the best. -- gianted
You are using an very old version of Plasma NM. You are also using NM-0.8, you should upgrade to NM-0.9, which is the version we support at the moment.