Ok, good to know :) Now, I'm not sure why you don't get a proper connection. The DHCP request on the interface just times out, as reported by NetworkManager:
Apr 4 21:20:56 till-twist NetworkManager[1150]: <warn> (wwan0): DHCPv4 request timed out. Apr 4 21:20:56 till-twist NetworkManager[1150]: <info> (wwan0): canceled DHCP transaction, DHCP client pid 15159 Apr 4 21:20:56 till-twist NetworkManager[1150]: <info> Activation (wwan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Apr 4 21:20:56 till-twist NetworkManager[1150]: <info> Activation (wwan0) Stage 4 of 5 (IPv4 Configure Timeout) started... Apr 4 21:20:56 till-twist NetworkManager[1150]: <info> (wwan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] You say it's a regression the lack of connectivity; could you gather debug logs using an older MM version? Also, check your APN string, is it correct for sure? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164023 Title: modem-manager crashed with SIGSEGV in g_slice_alloc() - REGRESSION: No internet access via mobile broadband To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1164023/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
