Bug 1018524 - ModemManager failed to start after upgrade F19 -> F20
Summary: ModemManager failed to start after upgrade F19 -> F20
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-12 22:04 UTC by Rob Sharp
Modified: 2015-06-29 12:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:37:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rob Sharp 2013-10-12 22:04:31 UTC
Description of problem:

ModemManager failed to start after F19 -> F20 upgrade via fedup.


Version-Release number of selected component (if applicable):

/  ᐅ rpm -q ModemManager
ModemManager-1.1.0-2.git20130913.fc20.x86_64

How reproducible:

I am unable to revert my system to re-attempt an upgrade.

Steps to Reproduce:
1. Given a working installation of ModemManager in Fedora 19
2. Upgrade from F19 to F20 via fedup
3. Attempt to use ModemManager via the system status are

Actual results:

My modem is detected (confirmed via syslog) but not shown on the system status area 

Expected results:

My mobile broadband connection to be shown on the system status area

Additional info:

/etc/dbus-1/system.d  ᐅ sudo service ModemManager status
Redirecting to /bin/systemctl status  ModemManager.service
ModemManager.service - Modem Manager
   Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; disabled)
   Active: active (running) since Sat 2013-10-12 23:01:53 EST; 3s ago
 Main PID: 17249 (ModemManager)
   CGroup: /system.slice/ModemManager.service
           └─17249 /usr/sbin/ModemManager

Oct 12 23:01:53 laphroaig ModemManager[17249]: <info>  ModemManager (version 1.1.0-2.git20130913.fc20) starting...
Oct 12 23:01:53 laphroaig systemd[1]: Started Modem Manager.
Oct 12 23:01:53 laphroaig ModemManager[17249]: <warn>  (ttyUSB0): port attributes not fully set
Oct 12 23:01:53 laphroaig ModemManager[17249]: <warn>  (ttyUSB1): port attributes not fully set
Oct 12 23:01:53 laphroaig ModemManager[17249]: <warn>  (ttyUSB2): port attributes not fully set
Oct 12 23:01:53 laphroaig ModemManager[17249]: <warn>  (ttyUSB3): port attributes not fully set
Oct 12 23:01:55 laphroaig ModemManager[17249]: <warn>  Couldn't find support for device at '/sys/devices/pci0000...lugin
Oct 12 23:01:55 laphroaig ModemManager[17249]: <warn>  Couldn't find support for device at '/sys/devices/pci0000...lugin
Hint: Some lines were ellipsized, use -l to show in full.

Comment 1 Andreas Huser 2013-11-19 17:17:24 UTC
Hi, 

i have resolved this problem by reinstall the modemmanager.

yum reinstall ModemManager.x86_64
systemctl restart ModemManager
systemctl enalbe ModemManager

Regards Andreas

Comment 2 Konrad Paumann 2013-11-25 14:30:38 UTC
Can confirm this issue after upgrade with fedup from f19 to f20. Also resolved this by reinstalling ModemManager.

Comment 3 madcatx 2013-12-25 10:07:48 UTC
This is a problem for me as well. I can work around by problem by either starting MM manually or by renaming "/usr/share/dbus-1/system-services/org.freedesktop.ModemManager1.service" to something else.

Comment 4 Fedora End Of Life 2015-05-29 09:34:11 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Comment 5 Fedora End Of Life 2015-06-29 12:37:40 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


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