Hello Atlas, or anyone else affected, Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.4 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: modemmanager (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2067240 Title: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID information, and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo laptops. (lp: #2045276) [ Test Plan ] Under Jammy environment, with latest linux-oem kernel installed, check output of `mmcli -L` to see if the modems are properly recognized. Modems to check: - EM061K-GL - EM160 - EM160 [ Where problems could occur ] EM160R-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs EM061K-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs RM520N-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs All these changes are merged, and they only introduce new PIDs for initial supports, which do not affect existing ones. Noble contains these changes, so, only SRU jammy and mantic. [ Other Info ] These patches are proved work with the test version on my PPA: https://launchpad.net/~pseudoc/+archive/ubuntu/nate To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067240/+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
