Bug 1036293 - ModemManager fails to load when a 3G dongle is plugged in
Summary: ModemManager fails to load when a 3G dongle is plugged in
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-30 15:34 UTC by Berend De Schouwer
Modified: 2015-06-29 13:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:17:35 UTC
Type: Bug


Attachments (Terms of Use)

Description Berend De Schouwer 2013-11-30 15:34:33 UTC
Description of problem:

3G Dongles no longer work with Fedora 20 (Beta)  ModemManager is not loaded.


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

ModemManager-1.1.0-2.git20130913.fc20.x86_64


How reproducible:

Always


Steps to Reproduce:
1. Plug in 3G dongle
2. wait

Actual results:

Nothing happens.

In the background, USB detects the dongle.  usb_modeswitch triggers.  Systemd attempts to load ModemManager.  Systemd cannot find ModemManager


Expected results:

Somehow magically the 3G network becomes available in the network list.


Additional info:

ModemManager is i686 ONLY in Fedora 20 ???  Rest is x86_64.


From /var/log/messages:

Nov 30 17:21:16 klatch systemd-udevd[30502]: renamed network interface wwan0 to wwp0s29u1u2i1
Nov 30 17:21:57 klatch dbus-daemon: dbus[598]: [system] Activating via systemd
: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.Mode
mManager1.service'
Nov 30 17:21:57 klatch dbus-daemon: dbus[598]: [system] Activation via systemd
 failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.f
reedesktop.ModemManager1.service failed to load: No such file or directory.
Nov 30 17:21:57 klatch dbus[598]: [system] Activating via systemd: service nam
e='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.ser
vice'
Nov 30 17:21:57 klatch dbus[598]: [system] Activation via systemd failed for u
nit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.Mo
demManager1.service failed to load: No such file or directory.


/usr/share/dbus-1/system-services/org.freedesktop.ModemManager1.service:

[D-BUS Service]
Name=org.freedesktop.ModemManager1
Exec=/usr/sbin/ModemManager
User=root
SystemdService=dbus-org.freedesktop.ModemManager1.service


/usr/lib/systemd/system/ModemManager.service:

[Unit]
Description=Modem Manager
After=syslog.target

[Service]
Type=dbus
BusName=org.freedesktop.ModemManager1
ExecStart=/usr/sbin/ModemManager
StandardError=null
Restart=on-abort

[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.ModemManager1.service



ldd /usr/sbin/ModemManager:

	linux-vdso.so.1 =>  (0x00007fff399fe000)
	libgudev-1.0.so.0 => /lib64/libgudev-1.0.so.0 (0x0000003a74200000)
	libmm-glib.so.0 => /lib64/libmm-glib.so.0 (0x00000032d8600000)
	libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007f9049750000)
	libqmi-glib.so.1 => /lib64/libqmi-glib.so.1 (0x00000032c5200000)
	libmbim-glib.so.0 => /lib64/libmbim-glib.so.0 (0x0000003a72200000)
	libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007f90493ea000)
	libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007f9049199000)
	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f9048e6d000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003144e00000)
	libc.so.6 => /lib64/libc.so.6 (0x0000003144200000)
	libudev.so.1 => /lib64/libudev.so.1 (0x0000003a71e00000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003145e00000)
	librt.so.1 => /lib64/librt.so.1 (0x0000003146200000)
	libdl.so.2 => /lib64/libdl.so.2 (0x0000003144a00000)
	libffi.so.6 => /lib64/libffi.so.6 (0x0000003148200000)
	libz.so.1 => /lib64/libz.so.1 (0x0000003145200000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003147200000)
	/lib64/ld-linux-x86-64.so.2 (0x0000003143a00000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003145600000)
	libpcre.so.1 => /lib64/libpcre.so.1 (0x0000003145a00000)

Comment 1 Adam Williamson 2013-12-14 18:16:46 UTC
Does 'systemctl start ModemManager.service' help? 'systemctl enable ModemManager.service' to enable it permanently.

Comment 2 Berend De Schouwer 2013-12-15 15:24:46 UTC
Works great.

Comment 3 Adam Williamson 2013-12-15 18:20:33 UTC
Did you upgrade from an earlier release to F20? I think in tests I did, the service is enabled on fresh installs...

Comment 4 nucleo 2013-12-16 01:41:53 UTC
I also have this message:

Dec 16 03:38:12 localhost dbus-daemon[221]: dbus[221]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbu
s-org.freedesktop.ModemManager1.service failed to load: No such file or directory.

There is file org.freedesktop.ModemManager1.service, so maybe activation failed because of dbus- prefix in unit name?

Comment 5 nucleo 2013-12-16 01:43:03 UTC
There is in ModemManager package:
/usr/share/dbus-1/system-services/org.freedesktop.ModemManager1.service

Comment 6 Adam Williamson 2013-12-16 01:45:17 UTC
Those messages will go away now you've enabled ModemManager.service. It's 'normal' that they're printed when it's installed but disabled (it's a bug, but a known one): https://fedoraproject.org/wiki/Common_F20_bugs#modemmanager-dbus-spam , https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1018017 .

Comment 7 Berend De Schouwer 2013-12-16 11:14:09 UTC
I did upgrade, yes.

Comment 8 Fedora End Of Life 2015-05-29 09:53:12 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 9 Fedora End Of Life 2015-06-29 13:17:35 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.