Bug 1483051 - Rebase ModemManager to new upstream version
Summary: Rebase ModemManager to new upstream version
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ModemManager
Version: 7.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Desktop QE
Ioanna Gkioka
Depends On:
Blocks: 1470965 1491343
TreeView+ depends on / blocked
Reported: 2017-08-18 16:34 UTC by Thomas Haller
Modified: 2022-12-14 13:41 UTC (History)
8 users (show)

Fixed In Version: ModemManager-1.6.8-1.el7, libqmi-1.18.0-1.el7, libmbim-1.14.2-1.el7, usb_modeswitch-2.5.1-1.el7, usb_modeswitch-data-20170806-1.el7
Doc Type: Release Note
Doc Text:
_ModemManager_ rebased to version 1.6.8 The _ModemManager_ package has been upgraded to upstream version 1.6.8 to support newer modem hardware. This provides a number enhancements over the previous version. Notably, the version of the `libqmi` library has been upgraded to 1.18.0 and the `libmbim` library to 1.14.2. In addition, the `usb_modeswitch` tool has been upgraded to 2.5.1 and the _usb-modeswitch-data_ package to 20170806.
Clone Of:
: 1491343 (view as bug list)
Last Closed: 2018-04-10 10:10:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0699 0 None None None 2018-04-10 10:10:49 UTC

Description Thomas Haller 2017-08-18 16:34:23 UTC
For RHEL-7.5 we'd like to improve modem support.

In rhel-7.4 we have MM-1.6.0.

We could either rebase to
  - 1.6.8 (which is latest upstream release)
  - 1.6.10 (or newer), which would be yet-to-be-release 1.8
  - 1.10.0 (or newer), which is current master, not yet released.

I think we should aim for 1.6.10.

Rebasing to not-yet-released 1.10.0 would also require a rebase of libqmi.

Comment 2 Lubomir Rintel 2017-08-29 12:50:07 UTC
Updated ModemManager and the associated libraries:


Comment 8 errata-xmlrpc 2018-04-10 10:10:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.