GNOME Bugzilla – Bug 691778
Provide more information about the 'FAILED' state of a modem
Last modified: 2013-03-12 19:17:40 UTC
Modems in 'failed' state aren't really shown in the UIs right now, as the user cannot do anything with them. A good approach, though, would be to show them in the UI but stating the reason why they went into failed state. One approach would be to use new more specific 'failed' state values to handle this, e.g.: MM_MODEM_STATE_FAILED_AIRPLANE_MODE = -5 MM_MODEM_STATE_FAILED_SIM_MISSING = -4 MM_MODEM_STATE_FAILED_SIM_LOCKED = -3 MM_MODEM_STATE_FAILED_SIM_ERROR = -2 MM_MODEM_STATE_FAILED = -1 The problem with this approach is that the 'state' enum is used in lots of places, and we don't really want to get forced to modify lots of code just to handle this. Another approach would be to have a 'FailureReason' property in the Modem interface, which will contain the reason for the failure only if the state == failed.
The second options sounds best. Is it then just to update the clients to display failed modems too, with a message describing why?
Implemented in the 'state-failed-reason' branch in upstream git: http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=state-failed-reason&id=1cc6c9800fb48ed61d134df5592b2ea970774e47 Comments welcome.
This branch was merged to git master not long ago.
Then see bug #559488.
Probably fixed in commit 75d20c15d4f844270cfc6c31fae261412e4b1b59 and friends, not yet in any release.