Bug 356772 - "connect" does not work for mobile broadband connection
Summary: "connect" does not work for mobile broadband connection
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: 5.5.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-16 11:14 UTC by Stefan Vater
Modified: 2015-12-17 17:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Patch allowing to unlock PIN2 and other lock types (658 bytes, patch)
2015-12-17 08:01 UTC, Jan Grulich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Vater 2015-12-16 11:14:33 UTC
I have a HUAWEI mobile broadband USB surf stick. When plugged in, it shows correctly up in th nm-applet, but hitting the "connect" buttom, nothing happens. However, I can connect using the command line with nmcli -p con up "connection name", and then disconnect using the applet.

Reproducible: Always

Steps to Reproduce:
1. Plugin surf stick and wait until it is recognized
2. Hit "connect" button in applet

Actual Results:  
No connection is established.
Comment 1 Jan Grulich 2015-12-16 11:33:35 UTC
Weird, it works for me. Did it work before the update? Is there any attempt to activate the connection in NetworkManager log?
Comment 2 Stefan Vater 2015-12-16 13:18:00 UTC
Well, this is already since some time. Unfortunately I cannot really remember since when, maybe since my switch to plasma 5.

Here is what journalctl -u NetworkManager gives me when plugging the stick:
Dez 16 14:00:13 mylinux.org NetworkManager[960]: <info>  (cdc-wdm0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Dez 16 14:00:49 mylinux.org NetworkManager[960]: <info>  (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
Dez 16 14:00:49 mylinux.org NetworkManager[960]: <info>  (cdc-wdm0): new Broadband device (carrier: UNKNOWN, driver: 'qmi_wwan, option1', ifindex: 0)
Dez 16 14:00:49 mylinux.org NetworkManager[960]: <info>  (cdc-wdm0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dez 16 14:00:49 mylinux.org NetworkManager[960]: <info>  (cdc-wdm0): modem state 'enabling'
Dez 16 14:00:49 mylinux.org NetworkManager[960]: <info>  (cdc-wdm0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Dez 16 14:00:50 mylinux.org NetworkManager[960]: <info>  (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)

The only log I could find when hitting the "connect" button was in .xsession-errors:

unlocking  "/org/freedesktop/ModemManager1/Modem/3"
plasma-nm: unlockRequired ==  3

Does that help?
Comment 3 Jan Grulich 2015-12-16 13:41:00 UTC
Yes, that helps, According to the log your SIM card is protected by PIN2, is that true? We handle just PIN and PUK and not PIN2 or PUK2 or any other type. We disabled this because there were some issues due to this but it looks there are now new issues due to not handling those types.
Comment 4 Jan Grulich 2015-12-17 08:01:27 UTC
Created attachment 96140 [details]
Patch allowing to unlock PIN2 and other lock types

Are you able to test this patch?
Comment 5 Stefan Vater 2015-12-17 17:17:29 UTC
No, sorry compiling plasma-nm would take me a while, time I do not have right now. However, I managed to solve my problem by setting up a new "connection" in the connection editor. With this, everything seems to work. Sorry that I did not think about this possibility before. When I look at the configuration files in /etc/NetworkManager/system-connections the difference is essentially in password-flags and pin-flags. 

For the non-working connection it is:
password-flags=1
pin-flags=2

while for the working one it is:
password-flags=4
pin-flags=4

It is strange that I cannot even edit the non-working connection with the connection editor. When I open it the "OK" button is always greyed out and there pops up a notification saying "Connection data for SURFSTICK could not be gathered" (my translation) "No agents were available for this request".

Hopefully this helps for future problems with old connection setups. If you would like to have the full configuration file, please let me know.

Thanks a lot for the quick help! I set the status to RESOLVED/WORKSFORME. I hope that is right.