Did some digging around and compared the plasma widget configuration files ($HOME/.kde/share/apps/networkmanagement/connections) and previous knetworkmanager configuration files ($HOME/.kde/share/config/knetworkmanagerrc).
The only obvious error in /var/log/daemon.log when trying to connect using my Huawei E220 mobile broadband modem is the following snippet:
--------------------------
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Apr 13 02:44:59 ladyjaye nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0, iface: (null)): iface not found
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB0): found serial port (udev:GSM hal:GSM)
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB0): new Modem device (driver: 'option')
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0
Apr 13 02:45:04 ladyjaye NetworkManager: <info> (ttyUSB0): device state change: 1 -> 2
Apr 13 02:45:04 ladyjaye NetworkManager: <info> (ttyUSB0): deactivating device (reason: 2).
Apr 13 02:45:04 ladyjaye NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Apr 13 02:45:04 ladyjaye NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Apr 13 02:45:04 ladyjaye NetworkManager: <info> (ttyUSB0): device state change: 2 -> 3
--------------------------
The findings in that page seems to indicate that the modem was not unlocked by NetworkManager using the correct PIN (or any PIN at all). So that led me to thinking maybe this same error is affecting the plasma widget.
Looking through my configuration file for my mobile broadband connection, I noticed that there the parameter for the PIN was defined in knetworkmanagerrc but was stored in kwallet instead for the plasma widget.
I'm wondering if it's possible that the plasma widget fails to submit the PIN information to NetworkManager to unlock the modem leading to this issue. I know that the maintainer of this package may not have the resources to test using mobile broadband modems but if this clue leads to something we'd be much happier for it :)
Did some digging around and compared the plasma widget configuration files ($HOME/ .kde/share/ apps/networkman agement/ connections) and previous knetworkmanager configuration files ($HOME/ .kde/share/ config/ knetworkmanager rc).
The only obvious error in /var/log/daemon.log when trying to connect using my Huawei E220 mobile broadband modem is the following snippet:
------- ------- ------- ----- p/Hal/devices/ usb_device_ 12d1_1003_ noserial_ if0_serial_ usb_0, iface: (null)): iface not found p/Hal/devices/ usb_device_ 12d1_1003_ noserial_ if0_serial_ usb_0 device_ flush_ip4_ routes_ with_iface: assertion `iface_idx >= 0' failed device_ flush_ip4_ addresses_ with_iface: assertion `iface_idx >= 0' failed ------- ------- -----
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Apr 13 02:44:59 ladyjaye nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedeskto
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB0): found serial port (udev:GSM hal:GSM)
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB0): new Modem device (driver: 'option')
Apr 13 02:44:59 ladyjaye NetworkManager: <info> (ttyUSB0): exported as /org/freedeskto
Apr 13 02:45:04 ladyjaye NetworkManager: <info> (ttyUSB0): device state change: 1 -> 2
Apr 13 02:45:04 ladyjaye NetworkManager: <info> (ttyUSB0): deactivating device (reason: 2).
Apr 13 02:45:04 ladyjaye NetworkManager: nm_system_
Apr 13 02:45:04 ladyjaye NetworkManager: nm_system_
Apr 13 02:45:04 ladyjaye NetworkManager: <info> (ttyUSB0): device state change: 2 -> 3
-------
Googling for the search term "nm_system_ device_ flush_ip4_ routes_ with_iface: assertion `iface_idx >= 0' failed", I found the following page: https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/289690
The findings in that page seems to indicate that the modem was not unlocked by NetworkManager using the correct PIN (or any PIN at all). So that led me to thinking maybe this same error is affecting the plasma widget.
Looking through my configuration file for my mobile broadband connection, I noticed that there the parameter for the PIN was defined in knetworkmanagerrc but was stored in kwallet instead for the plasma widget.
I'm wondering if it's possible that the plasma widget fails to submit the PIN information to NetworkManager to unlock the modem leading to this issue. I know that the maintainer of this package may not have the resources to test using mobile broadband modems but if this clue leads to something we'd be much happier for it :)