So this is a bit of a pickle this SRU. Basically we need to decide on one of the two worlds: staying compliant with what the manufacturers demand (not performing the FCC unlock by default) and not breaking users (as previously modemmanager was automatically performing the unlock). We would probably need to consult someone regarding the legal aspect of automatically unlocking the devices - so it's something we really should do. Since by default we should really REALLY make sure that we're not breaking existing users, but then again - we shouldn't be doing things that are 'not okay' by our main packages as well.
However, in the meantime, I'll review the SRU as-is, without the auto- unlocking, consider pulling it into focal-proposed and then set a block- proposed tag until we know for sure which way to go. We can always patch the package with the unlocks and re-upload, if needed. A bit of additional data regarding the regression potential of this change, maybe even some pros of just going with 1.118 as-is: * From what I know, some of the locked modems (the Lenovo-shipped ones I think?) are already broken by a firmware upgrade right now. * Users upgrading to the next LTS (22.04), once upgrades are enabled, will encounter this issue anyway, having to manually perform the unlock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
