Re: ModemManager: 'org.freedesktop.DBus.Error.NoReply: Did not receive a reply.'

[Aleksander Morgado <aleksander lanedo com>]

Hi Dan,

> > > 
> > > i have a detected Modem and tried to send the SIM-PIN with the dbus 
> > > method (with d-feet) 
> > > org.freedesktop.ModemManager.Modem.Gsm.Card.SendPin() and get a dbus 
> > > error back:
> > > 
> > > 'org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible 
> > > causes include: the remote application did not send a reply, the message 
> > > bus security policy blocked the reply, the reply timeout expired, or the 
> > > network connection was broken.'
> > 
> > How long does it take to return that error?  Sometimes the unlock takes
> > a while, and if the program uses a very short timeout, this could
> > happen.  I'm not sure what d-feet uses offhand.  The other possibility
> > of course is that ModemManager has a bug.  From the trace you've got
> > there, it doesn't appear that MM should be rechecking the PIN state like
> > that.  Any chance you can poke around in mm-generic-gsm.c where it
> > checks the pin state and see what's going on?
> 
> The problem is, that the reply from the modem does not contain a "OK".
> That's why MM repeats the request.
> I have this behaviour with a Wavecom modem. Alexander Morgado [1] is
> already working on this problem.
> 
> 

Check the patch attached in:
http://mail.gnome.org/archives/networkmanager-list/2011-March/msg00227.html

Which allows a plugin to configure its own list of successful and error
responses. That would allow the plugin to expect a CPIN reply without
OK, with a regex like this: "\\r\\n\\+CPIN: .*\\r\\n"

Cheers,

-- 
Aleksander