tags: -1 + moreinfo help Am 20.01.2015 um 11:42 schrieb Mike Gabriel: > Severity: serious > Justification: GSM modem support will not work out-of-the-box with > non-systemd setups > > Hi, > > I see a similar issue about ModemManager not coming up by default via > network-manager. > > The reason is simple (after staring at mm and nm from jessie and wheezy > for a while): > > o ModemManager comes with a DBus system-service file > o NetworkManager in Debian wheezy triggers that service > (org.freedesktop.ModemManager) > o NetworkManager in Debian testing does not have that code anymore, it > expects > from systemd to launch ModemManager > > => systems without systemd as PID 1 fail to start ModemManager and GSM > devices are not available in NetworkManager.
Looks like ModemManager starts just fine here if I boot with sysvinit. If, as you say, NM no longer pokes the D-Bus service, I guess something else in the desktop (GNOME3 here) does it. So this issue might be specific to certain DEs. > > Solution IMHO: > > o Provide an init script in /etc/init.d/ that launches ModemManager on > non-systemd machines > o other options??? I don't think adding an init script to ModemManager is a good option. For one, I don't want to start MM unconditionally. I'd rather have NM use a runtime check for systemd (sd_booted()). All the code still seems to be there [1], it just needs to be changed to use a runtime check instead of compile time. I'm inclined to re-assign this to NM. > I hope we can get this fixed for jessie. > I'd be willing to review and merge a tested patch for NM. Cheers, Michael [1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=3b76ae18a52b44dbe577557e038fdc263edc5715 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
