|
Bugzilla – Full Text Bug Listing |
| Summary: | SIM PIN unlock impossible | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Holger Sickenberg <holgi> |
| Component: | Mobile Devices | Assignee: | Hans Petter Jansson <hpj> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | doerges, forgotten_5wsNBe_fTf, gp, hpj, prohol, saba, suse |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Component Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Output of ModemManager debug run | ||
|
Description
Holger Sickenberg
2011-02-02 09:46:21 UTC
Probably a Mobile Devices issue. I have the same in 11.3 after upgrade NetworkManager to 0.8.2 with Huawei gsm modem. Before upgrade works fine. Exactly the same problem here with openSuSe 11.4 stable either i586 and x86_64. No matter if after update or new install. It's quite stressing when you have to type PIN and password sitting in some public place over and over again. The feature works without problem in openSuse 11.1, 11.2 and 11.3 with the same device. When click 'Abort' button on PIN request message window and choose GSM connection from NetworkManger (when PIN is entered in NetworkManager options) then in logs there are lots of lines like: kernel: [44488.935467] option: option_instat_callback: error -62 and the connection is not established. Note: the bug 681878 can be duplicated of it. I can replicate this. It looks like a generic problem, not an issue specific to a device. Running ModemManager with --debug yields: ** Message: (ttyUSB1) opening serial device... ** (modem-manager:4771): DEBUG: <1301926643.652919> (ttyUSB1) device open count is 1 (open) ** (modem-manager:4771): DEBUG: (ttyUSB1): probe requested by plugin 'Novatel' ** Message: (ttyUSB0) opening serial device... ** (modem-manager:4771): DEBUG: <1301926643.656308> (ttyUSB0) device open count is 1 (open) ** (modem-manager:4771): DEBUG: (ttyUSB0): probe requested by plugin 'Novatel' ** (modem-manager:4771): DEBUG: <1301926643.754432> (ttyUSB1): --> 'AT+GCAP<CR>' ** (modem-manager:4771): DEBUG: <1301926644.556684> (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:4771): DEBUG: <1301926645.358505> (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:4771): DEBUG: Got failure code 100: Unknown error ** (modem-manager:4771): DEBUG: <1301926645.358808> (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:4771): DEBUG: <1301926646.160477> (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:4771): DEBUG: Got failure code 100: Unknown error ** (modem-manager:4771): DEBUG: <1301926646.160710> (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:4771): DEBUG: <1301926646.962451> (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:4771): DEBUG: Got failure code 100: Unknown error ** (modem-manager:4771): DEBUG: <1301926646.962692> (ttyUSB0): --> 'ATI<CR>' ** (modem-manager:4771): DEBUG: <1301926647.363648> (ttyUSB0): <-- 'ATI<CR><CR><LF>Manufacturer: Novatel Wireless Incorporated<CR><LF>Model: Merlin X950D ExpressCard<CR><LF>Revision: 3.15.00.0-00 [2007-12-04 15:40:23]<CR><LF>IMEI: 356922010078405<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:4771): DEBUG: <1301926647.363885> (ttyUSB0) device open count is 0 (close) ** Message: (ttyUSB0) closing serial device... ** Message: (ttyUSB0) type primary claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 ** Message: (ttyUSB0) opening serial device... ** (modem-manager:4771): DEBUG: <1301926647.378407> (ttyUSB0) device open count is 1 (open) ** (modem-manager:4771): DEBUG: <1301926647.378509> (ttyUSB0) device open count is 2 (open) ** Message: (Novatel): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 claimed port ttyUSB0 ** (modem-manager:4771): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 ** (modem-manager:4771): DEBUG: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 ** (modem-manager:4771): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 ** (modem-manager:4771): DEBUG: <1301926647.379047> (ttyUSB0): --> 'AT+CPIN?<CR>' ** (modem-manager:4771): DEBUG: <1301926647.389126> (ttyUSB0): <-- 'AT+CPIN?<CR>' ** (modem-manager:4771): DEBUG: <1301926647.400221> (ttyUSB0): <-- '<CR><LF>+CPIN: SIM PIN<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:4771): DEBUG: <1301926647.400552> (ttyUSB0) device open count is 1 (close) ** (modem-manager:4771): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 ** (modem-manager:4771): DEBUG: <1301926647.400808> (ttyUSB0): --> 'AT$NWDMAT=1<CR>' ** (modem-manager:4771): DEBUG: <1301926647.413817> (ttyUSB0): <-- 'AT$NWDMAT=1<CR>' ** (modem-manager:4771): DEBUG: <1301926647.415151> (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' ** (modem-manager:4771): DEBUG: <1301926647.415234> (ttyUSB0) device open count is 0 (close) ** Message: (ttyUSB0) closing serial device... ** (modem-manager:4771): DEBUG: <1301926647.762894> (ttyUSB1): --> 'AT+GCAP<CR>' ** (modem-manager:4771): DEBUG: <1301926648.564698> (ttyUSB1): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:4771): DEBUG: Got failure code 100: Unknown error ** (modem-manager:4771): DEBUG: <1301926648.564934> (ttyUSB1): --> 'AT+GCAP<CR>' ** (modem-manager:4771): DEBUG: <1301926649.366499> (ttyUSB1): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:4771): DEBUG: Got failure code 100: Unknown error ** (modem-manager:4771): DEBUG: <1301926649.366726> (ttyUSB1): --> 'ATI<CR>' ** (modem-manager:4771): DEBUG: <1301926649.767599> (ttyUSB1): <-- 'ATI<CR><CR><LF>Manufacturer: Novatel Wireless Incorporated<CR><LF>Model: Merlin X950D ExpressCard<CR><LF>Revision: 3.15.00.0-00 [2007-12-04 15:40:23]<CR><LF>IMEI: 356922010078405<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:4771): DEBUG: <1301926649.767689> (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** Message: (ttyUSB1) type secondary claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 ** Message: (Novatel): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 claimed port ttyUSB1 ** (modem-manager:4771): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5 as /org/freedesktop/ModemManager/Modems/0 ** (modem-manager:4771): DEBUG: (/org/freedesktop/ModemManager/Modems/0): data port is ttyUSB0 ** Message: (ttyUSB0) opening serial device... ** (modem-manager:4771): DEBUG: <1301926664.769788> (ttyUSB0) device open count is 1 (open) ** (modem-manager:4771): DEBUG: <1301926664.769844> (ttyUSB0): --> 'AT+CPIN="8880"<CR>' ** (modem-manager:4771): DEBUG: <1301926664.786570> (ttyUSB0): <-- 'AT+CPIN="8880"<CR>' ** (modem-manager:4771): DEBUG: <1301926664.859291> (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' ** (modem-manager:4771): DEBUG: <1301926664.859515> (ttyUSB0): --> 'AT+CPIN?<CR>' ** (modem-manager:4771): DEBUG: <1301926664.869915> (ttyUSB0): <-- 'AT+CPIN?' ** (modem-manager:4771): DEBUG: <1301926664.870117> (ttyUSB0): <-- '<CR>' ** (modem-manager:4771): DEBUG: <1301926664.873194> (ttyUSB0): <-- '<CR><LF>+CPIN: READY<CR><LF><CR><LF>OK<CR><LF>' ** Message: Modem /org/freedesktop/ModemManager/Modems/0: unlock no longer required ** (modem-manager:4771): DEBUG: <1301926664.873662> (ttyUSB0) device open count is 0 (close) ** Message: (ttyUSB0) closing serial device... For me, however, the modem works after unlocking. Please do: cd /usr/share/dbus-1/system-services mv org.freedesktop.ModemManager.service org.freedesktop.ModemManager.service.OFF rcnetwork restart <plug in your device> modem-manager --debug [a lot of output to be attached] mv org.freedesktop.ModemManager.service.OFF org.freedesktop.ModemManager.service rcnetwork restart Created attachment 423127 [details]
Output of ModemManager debug run
Yes - after providing the PIN code the modem were unlock, but this not the way it should works, because:
1. The pin code was entered in the NetworkManager settings for this connection.
2. After typing pin user also have to provide root password in a short time (before modem pin request timeout).
So it's looks like ModemManager is not trying to get the PIN code from NetworkManager settings.
(In reply to comment #8) > Yes - after providing the PIN code the modem were unlock, but this not the way > it should works, because: OK, I needed to make sure the modem is unlocked if all goes well. > 1. The pin code was entered in the NetworkManager settings for this connection. That should not happen. > 2. After typing pin user also have to provide root password in a short time > (before modem pin request timeout). That also happens if you don't store the PIN. So this is a problem of PolicyKit. You can argue that this is a stupid default. Please make a separate bug report for that. > So it's looks like ModemManager is not trying to get the PIN code from > NetworkManager settings. Yes. *** Bug 681878 has been marked as a duplicate of this bug. *** The same device as in comment#6 with 11.3 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:26910): DEBUG: (ttyUSB1): probe requested by plugin 'Novatel' ** Message: (ttyUSB0) opening serial device... ** (modem-manager:26910): DEBUG: (ttyUSB0): probe requested by plugin 'Novatel' ** (modem-manager:26910): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:26910): DEBUG: Got failure code 100: Unknown error ** (modem-manager:26910): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:26910): DEBUG: Got failure code 100: Unknown error ** (modem-manager:26910): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:26910): DEBUG: Got failure code 100: Unknown error ** (modem-manager:26910): DEBUG: (ttyUSB0): --> 'ATI<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB0): <-- 'ATI<CR><CR><LF>Manufacturer: Novatel Wireless Incorporated<CR><LF>Model: Merlin X950D ExpressCard<CR><LF>Revision: 3.15.00.0-00 [2007-12-04 15:40:23]<CR><LF>IMEI: 356922010078405<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' ** Message: (ttyUSB0) closing serial device... ** Message: (ttyUSB0) opening serial device... ** Message: (Novatel): GSM modem /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1 claimed port ttyUSB0 ** (modem-manager:26910): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1 ** (modem-manager:26910): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1 as /org/freedesktop/ModemManager/Modems/0 ** (modem-manager:26910): DEBUG: (ttyUSB0): --> 'AT$NWDMAT=1<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB0): <-- 'AT$NWDMAT=1<CR><CR><LF>OK<CR><LF>' ** Message: (ttyUSB0) closing serial device... ** (modem-manager:26910): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB1): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:26910): DEBUG: Got failure code 100: Unknown error ** (modem-manager:26910): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB1): <-- 'AT+GCAP<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:26910): DEBUG: Got failure code 100: Unknown error ** (modem-manager:26910): DEBUG: (ttyUSB1): --> 'ATI<CR>' ** (modem-manager:26910): DEBUG: (ttyUSB1): <-- 'ATI<CR><CR><LF>Manufacturer: Novatel Wireless Incorporated<CR><LF>Model: Merlin X950D ExpressCard<CR><LF>Revision: 3.15.00.0-00 [2007-12-04 15:40:23]<CR><LF>IMEI: 356922010078405<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' ** Message: (ttyUSB1) closing serial device... ** Message: (Novatel): GSM modem /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1 claimed port ttyUSB1 HPJ, it seems like the newer MM simply tries to do more upon device detection. Can you explain why that is happening? There has been no answer for almost three months. However, does anyone still having problems with an updated 11.4? (In reply to comment #13) > There has been no answer for almost three months. However, does anyone still > having problems with an updated 11.4? Yes, still same behavior with updated 11.4. SIM PIN window appears with every start or resume. Confirm - I have the problem since 11.4 came out. I use gnome3 with NetworkManager-0.8.9997-2.2 from about 2 months I the windows still appears - even when I unplug my modem and plug it again (without logout or session restart). (In reply to comment #12) > HPJ, it seems like the newer MM simply tries to do more upon device detection. > Can you explain why that is happening? I'm not sure what exactly this bug is about at this point - complete inability to unlock (as in the bug title), or just the annoying dialogs? The password dialogs seem to imply that we're missing some PolicyKit piece. The difference in the logs indicate that the old MM was not passing the PIN to the modem at all, while the new one is. It's an upstream change. Just annoying dialogs - someone should change the title. From the end-user point of view: I plug the modem, dialog appears asking about PIN. After that another dialog asking for root password - but you must hurry, NetworkManager will not wait too long for your entry. In case where gsm range is poor after few minutes the modem disconnects and when it tries to connect again I will be asked about PIN and root pass once again. Yes, I can change my policykit to not be asked about passwd - but the PIN dialogs will still persist. I'm mean - something is broken, which wasn't broken before. Till 11.2 the mechanism was perfect - new modem plugin, PIN question, PIN is stored and I can forget about it. I even don't know where the bug can be: networkmanager, modemmanager, policykit? Actually, it looks like the old ModemManager doesn't store the PIN anywhere. The difference may just be that the new version is more aggressive about inputting the PIN code when it's getting errors from the modem. Most likely this is because there are modems where it's hard to tell if you need to input the PIN or not, so the safest option is to just provide it. The PIN is not stored anywhere, apparently because specs require it to be entered manually. Additionally, it's impossible to identify the SIM card prior to entering it, so an automatic storage mechanism has no reliable way to associate PIN numbers with SIM cards. However, according to the upstream mailing list, it's often possible to identify the *modem* and associate the PIN with that, which is good enough for most users. There's code to do just this in the upstream git repository. It might be possible to adapt it as a patch. Could please you provide me the output from the following commands: rpm -q ModemManager rpm -q --changelog ModemManager | head -20 Hmm, I didn't know that it's impossible. Thanks for explanation. Version of MM: ModemManager-0.4-8.9.1.i586 Changelog of ModemManager: * Wed Apr 27 2011 binli@opensuse.org - Add mm-dismiss-spam-log.patch, dismiss the spam log of Huawei. (bnc#674331, swampid#40503). * Sun Feb 13 2011 vuntz@opensuse.org - Call relevant macros in %post/%postun: + %icon_theme_cache_post/postun because the package ships themed icons. - Add hicolor-icon-theme BuildRequires and Requires since we need to have those macros defined and we install hicolor icons, so we need to have the theme installed. * Wed Nov 10 2010 coolo@novell.com - Remove zero-size files from documentation. * Wed Nov 10 2010 coolo@novell.com - Own parent directories. * Fri Aug 27 2010 vuntz@opensuse.org - Add ModemManager-polkit-deprecated.patch to fix build with a recent polkit (>= 0.97). This is only needed on openSUSE 11.4 and later. (In reply to comment #18) > Actually, it looks like the old ModemManager doesn't store the PIN anywhere. > The difference may just be that the new version is more aggressive about > inputting the PIN code when it's getting errors from the modem. Most likely > this is because there are modems where it's hard to tell if you need to input > the PIN or not, so the safest option is to just provide it. > > The PIN is not stored anywhere, apparently because specs require it to be > entered manually. Additionally, it's impossible to identify the SIM card prior > to entering it, so an automatic storage mechanism has no reliable way to > associate PIN numbers with SIM cards. However, according to the upstream > mailing list, it's often possible to identify the *modem* and associate the PIN > with that, which is good enough for most users. For me the PIN is stored with the connection Data of Network Manager. Starting an connection is possible if I just click cancel at the PIN & root-password request windows. For versions of openSUSE I never had this behavior before (was using 11.3 & 11.1). > There's code to do just this in the upstream git repository. It might be > possible to adapt it as a patch. > > Could please you provide me the output from the following commands: > > rpm -q ModemManager > rpm -q --changelog ModemManager | head -20 I'm experiencing exactly the same behavior on openSUSE-11.4 *after* upgrading from the stock openSUSE KDE packages to the ones from http://download.opensuse.org/repositories/KDE:/Release:/46/openSUSE_11.4 Currently I'm running: ModemManager-0.4-8.9.1.x86_64 NetworkManager-0.8.2-15.24.1.x86_64 NetworkManager-glib-0.8.2-15.24.1.x86_64 NetworkManager-kde4-libs-0.9.1git20110503-4.2.x86_64 NetworkManager-kde4-libs-debuginfo-0.9.1git20110503-4.2.x86_64 NetworkManager-kde4-libs-lang-0.9.1git20110503-4.2.noarch NetworkManager-openvpn-0.8.2-6.1.x86_64 NetworkManager-openvpn-kde4-0.9.1git20110503-4.2.x86_64 NetworkManager-openvpn-lang-0.8.2-6.1.noarch NetworkManager-pptp-0.8.2-4.1.x86_64 NetworkManager-pptp-kde4-0.9.1git20110503-4.2.x86_64 NetworkManager-pptp-lang-0.8.2-4.1.noarch NetworkManager-vpnc-0.8.2-4.1.x86_64 NetworkManager-vpnc-kde4-0.9.1git20110503-4.2.x86_64 NetworkManager-vpnc-lang-0.8.2-4.1.noarch plasmoid-networkmanagement-0.9.1git20110503-4.2.x86_64 Before the upgrade only these packages were different: NetworkManager-kde4-libs-0.9.svn1192577-7.2.x86_64 NetworkManager-kde4-libs-debuginfo-0.9.svn1192577-7.2.x86_64 NetworkManager-openvpn-kde4-0.9.svn1192577-7.2.x86_64 NetworkManager-pptp-kde4-0.9.svn1192577-7.2.x86_64 NetworkManager-vpnc-kde4-0.9.svn1192577-7.2.x86_64 plasmoid-networkmanagement-0.9.svn1192577-7.2.x86_64 Note that only the KDE parts changed. NetworkManager or ModemManager themselves haven't changed. As for PolicyKit I'm now running: gconf-polkit-2.32.1-4.1.x86_64 libpolkit0-0.99-5.6.1.x86_64 libpolkit-qt-1-1-0.99.1-5.1.x86_64 polkit-0.99-5.6.1.x86_64 polkit-default-privs-0.1_201102151742-1.2.1.noarch polkit-kde-agent-1-0.99.0-13.5.x86_64 polkit-kde-kcmmodules-1-0.98.1-13.13.x86_64 Before the upgrade it was: gconf-polkit-2.32.1-4.1.x86_64 libpolkit0-0.99-5.6.1.x86_64 libpolkit-qt-1-1-0.99.1-5.1.x86_64 polkit-0.99-5.6.1.x86_64 polkit-default-privs-0.1_201102151742-1.2.1.noarch polkit-kde-agent-1-0.99.0-3.1.x86_64 polkit-kde-kcmmodules-1-0.98.1-3.2.x86_64 Again, only the KDE parts seem to have changed. I also get this behaviour with openSUSE 12.1 # rpm -q ModemManager NetworkManager ModemManager-0.5-3.1.3.x86_64 NetworkManager-0.9.1.90-4.8.1.x86_64 Since this bug report has become somewhat confusing, please check whether Bug 749537 Comment #1 helps or clarifies the issue that the PIN has to be entered manually although it is saved "somewhere". Thanks! The status for this problem here is: Using 12.1 with LXDE as window-manager, I still get the "Enter PIN" popup. It does not matter if I enter the PIN and press "OK" or if I just press "Cancel", using the UMTS modem is working fine. So from my point of view the popup is useless. Thus, the original problem of not being able to unlock the SIM is solved? If so, I would recommend to resolve this bug as fixed. The useless popup might be worth a new bug report. Fine with me. For me also fine. Thank you both for your help! |