[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 Stefan Vater changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Stefan Vater --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 --- Comment #4 from Jan Grulich --- Created attachment 96140 --> https://bugs.kde.org/attachment.cgi?id=96140&action=edit Patch allowing to unlock PIN2 and other lock types Are you able to test this patch? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 --- Comment #3 from Jan Grulich --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 --- Comment #2 from Stefan Vater --- 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]: (cdc-wdm0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): new Broadband device (carrier: UNKNOWN, driver: 'qmi_wwan, option1', ifindex: 0) Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): modem state 'enabling' Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Dez 16 14:00:50 mylinux.org NetworkManager[960]: (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? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- Weird, it works for me. Did it work before the update? Is there any attempt to activate the connection in NetworkManager log? -- You are receiving this mail because: You are watching all bug changes.
