Hide Forgot
Description of problem: Fedora 19 had a regression with device Onda MW875UP. At the moment the system does not ask for SIM PIN so, the device is not usable. I noticed that lsusb changed device id of Onda MW875UP, comparing to the past ( https://bugzilla.redhat.com/show_bug.cgi?id=857647 ) Bus 001 Device 004: ID 1ee8:0053 ONDA COMMUNICATION S.p.a. Version-Release number of selected component (if applicable): usb_modeswitch-1.2.7-3.fc19
It happens on upgraded to Fedora 20 systems too. But it does not happen on fresh installed Fedora 20
On a fresh Fedora 20 installation, the device works correctly...
There must be a certain upgrade that broken compatibility with the device
Could we check why the system is no longer asking for PIN activation?
Turns out that on upgrade from F19 to F20, something disables the ModemManager service with systemd. Fresh installs of F20 do not have this problem, and ModemManager is enabled. (11:25:44 AM) Caterpillar2: ModemManager.service - Modem Manager (11:25:44 AM) Caterpillar2: Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; disabled) (11:25:45 AM) Caterpillar2: Active: inactive (dead) Over to systemd to see if for some reason the presets are configured differently on upgrade than on fresh install? ModemManager's specfile only calls %systemd_preun and %systemd_post and does not explicitly enable the service itself on RPM install.
In Fedora 19 (and earlier), ModemManager does not have a service file. There's just /usr/share/dbus-1/system-services/org.freedesktop.ModemManager.service, for dbus activation. In Fedora 20, there's a service file, which does get enabled by default according to the preset on new installations. When upgrading, the preset is ignored because the package was previously present. This is consistent with the reported behaviour. If the service should be enabled on update from F19, some scriptlet should be added. This does not seem to be a systemd issue.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.