ModemManager-1.20.6-2.fc39.x86_64 was from the mass rebuild. I downgraded to ModemManager-1.20.6-1.fc39 with sudo dnf downgrade https://kojipkgs.fedoraproject.org//packages/ModemManager/1.20.6/1.fc39/x86_64/ModemManager-1.20.6-1.fc39.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/ModemManager/1.20.6/1.fc39/x86_64/ModemManager-glib-1.20.6-1.fc39.x86_64.rpm in a QEMU/KVM VM using Fedora-KDE-Live-x86_64-Rawhide-20230725.n.1.iso. ModemManager from ModemManager-1.20.6-1.fc39 started normally with sudo systemctl start ModemManager.
Could you consider untagging ModemManager-1.20.6-2.fc39 from rawhide? I proposed this problem as a possible F39 final blocker https://bugzilla.redhat.com/show_bug.cgi?id=2226577#c3
When do you need this? (YYYY/MM/DD) I'm not sure.
When is this no longer needed or useful? (YYYY/MM/DD) I'm not sure.
If we cannot complete your request, what is the impact? ModemManager from ModemManager-1.20.6-2.fc39 won't start in rawhide and wireless broadband devices using it might not function properly until this problem is fixed. Allan reported that their phones don't work due to this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2226577#c2
Metadata Update from @jnsamyak: - Issue tagged with: high-gain, medium-trouble, ops
ModemManager-1.20.6-3.fc39 fixes this problem https://bugzilla.redhat.com/show_bug.cgi?id=2226577#c8 https://bodhi.fedoraproject.org/updates/FEDORA-2023-d26a306d68 Untagging ModemManager-1.20.6-2.fc39 shouldn't be needed as long as ModemManager-1.20.6-3.fc39 is in the next compose. Thanks.
Metadata Update from @mattf: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.