SRU the new 1.18 serie to focal for hwe

Hi seb128,

Currently we met issue for Fibocom L860-GL-16(8086:7560) could cause the ACPI reporting huge interrupts when modemmanager(1.16.6-2~20.04.1) was started. After upgrade to 1.18.6 from https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/ , this issue is gone, although this type modem was not supported yet.

https://bugs.launchpad.net/bugs/1964767

Putting a bit more thought into this, I'm a bit concerned by regressing user. The plus side, as per our face-to-face discussion, there are not many modem users, but still... maybe I'd like to investigate some possibilities.

Reading up on the modemmanager page gave me some necessary context here. I agree with the upstream decision not to unlock modems automatically and their recommendation for distributions not doing it automatically as well. That being said, 20.04 has been released with auto-unlocking, so this feels like going against our stability principles in Ubuntu. Some question here regarding this: does the new modemmanager add some new FCC locked modems in 1.18 in comparison to 1.16? Since one fair way to go forward in my eyes (at least right now) would be to keep auto-unlocking the previously supported modems but require manual unlocks of the new ones. Are there any new ones? Or does this basically only relate and lock down those that were previously available?

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.

Hello Sebastien, or anyone else affected,

Accepted libmbim into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.26.2-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Sebastien, or anyone else affected,

Accepted libqmi into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.30.4-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Sebastien, or anyone else affected,

Accepted modemmanager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.18.6-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Added the block-proposed-focal tag until we have clarity on how to proceed with the missing auto-unlocking functionality.

Fibocom L860-GL-16(8086:7560) could cause the ACPI reporting huge interrupts when modemmanager(1.16.6-2~20.04.1) was started at ThinkPad X1 Carbon and X13 Yoga. After upgrade to 1.18.6 from proposed channel, this issue is gone, although this type modem was not supported yet.

After various discussions, let's proceed with releasing this SRU and monitoring any reports regarding modems stopping to work.

This bug was fixed in the package libmbim - 1.26.2-1~ubuntu20.04.1

---------------
libmbim (1.26.2-1~ubuntu20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1965901)
  * Lower debhelper to 12 which is the version available on the serie

 -- Sebastien Bacher <email address hidden> Fri, 08 Apr 2022 11:33:15 +0200

This bug was fixed in the package libqmi - 1.30.4-1~ubuntu20.04.1

---------------
libqmi (1.30.4-1~ubuntu20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1965901)
  * Lower debhelper to 12 which is the version available on the serie

 -- Sebastien Bacher <email address hidden> Fri, 08 Apr 2022 11:31:16 +0200

This bug was fixed in the package modemmanager - 1.18.6-1~ubuntu20.04.1

---------------
modemmanager (1.18.6-1~ubuntu20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1965901)
  * Lower debhelper to 12 which is the version available on the serie

 -- Sebastien Bacher <email address hidden> Fri, 08 Apr 2022 11:37:10 +0200

The verification of the Stable Release Update for libmbim has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

It turns out that this actually regressed some qualcomm modems because modem-manager started to use some special netlink sockets that were not enabled in the 5.4 kernel.

To have that we need (see LP: #1998194):

CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m

in the 5.4 kernel. However, this might not be easy according to some discussion I had. Would it be possible to revisit this backport?