On Fri, May 8, 2015 at 11:00 AM, Torsten Hilbrich <torsten.hilbr...@secunet.com> wrote: > Version of modemmanager: 1.4.6 > Version of libmbim: 1.12.2 > Version of libqmi: 1.12.4 > > I noticed some unexpected behaviour of the modem manager when deleting a > bearer object which was currently in the connecting state. > > <debug> [1428916367.541269] New MBM bearer created at DBus path > '/org/freedesktop/ModemManager1/Bearer/7' > <debug> [1428916367.543275] Connecting bearer > '/org/freedesktop/ModemManager1/Bearer/7' > <info> [1428916367.543292] Modem > /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> > connecting) > > Now the D-Bus client triggers a DeleteBearer. > > <info> [1428916372.035137] Modem > /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> > connected) > <debug> [1428916372.035331] (wwan0): port now disconnected > <debug> [1428916372.035337] Removing from DBus bearer at > '/org/freedesktop/ModemManager1/Bearer/7' > > Problem is, the bearer object is removed but the modem stays connected. > > The API documentation says: > > -------------------------------- > DeleteBearer (IN o bearer); > > Delete an existing packet data bearer. > > If the bearer is currently active and providing packet data server, it > will be disconnected and that packet data service will terminate. > -------------------------------- > > I assumed that this meant that the modem will be disconnected > afterwards. Is this assumption wrong or am I experiencing a bug here? > > Full logs of modemmanager are attached, just some possible sensitive > information (IMEI, IMSI, SIM ID, Location) anonymized.
The modem/bearer should be disconnected if the connected bearer gets removed. If that is not happening, it's a bug. -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel