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



Am Montag, den 04.04.2011, 22:20 -0500 schrieb Dan Williams:
> On Tue, 2011-03-15 at 13:02 +0100, Thomas Bechtold wrote:
> > Hi,
> > 
> > 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.


Cheers,

Tom


[1]
http://mail.gnome.org/archives/networkmanager-list/2011-March/msg00225.html 


> 
> Dan
> 
> > 
> > The debug output of modemmanager (it's the latest git version, 
> > 0c4b94458ac0a71d278ce1b711a022fdf96b3abf) is:
> > 
> > modem-manager[597]: <info>  [1300190254.302326] [mm-serial-port.c:702] 
> > mm_serial_port_open(): (ttyACM3) opening serial port...
> > modem-manager[597]: <debug> [1300190254.302770] [mm-serial-port.c:764] 
> > mm_serial_port_open(): (ttyACM3) device open count is 1 (open)
> > modem-manager[597]: <debug> [1300190254.302829] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): --> 'AT+CPIN="0000"<CR>'
> > modem-manager[597]: <debug> [1300190256.961482] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): <-- '<CR><LF>OK<CR><LF>'
> > modem-manager[597]: <debug> [1300190256.961575] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): --> 'AT+CPIN?<CR>'
> > modem-manager[597]: <debug> [1300190257.005482] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): <-- '<CR><LF>+CPIN: 
> > READY<CR><LF>'
> > modem-manager[597]: <debug> [1300190262.002825] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): --> 'AT+CPIN?<CR>'
> > modem-manager[597]: <debug> [1300190262.020984] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): <-- '<CR><LF>+CPIN: 
> > READY<CR><LF>'
> > 
> > 
> > 
> > modem-manager[597]: <debug> [1300190267.001354] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): --> 'AT+CPIN?<CR>'
> > modem-manager[597]: <debug> [1300190267.020984] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): <-- '<CR><LF>+CPIN: 
> > READY<CR><LF>'
> > modem-manager[597]: <debug> [1300190272.001748] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): --> 'AT+CPIN?<CR>'
> > modem-manager[597]: <debug> [1300190272.017483] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): <-- '<CR><LF>+CPIN: 
> > READY<CR><LF>'
> > modem-manager[597]: <debug> [1300190277.001042] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): --> 'AT+CPIN?<CR>'
> > modem-manager[597]: <debug> [1300190277.020986] 
> > [mm-at-serial-port.c:298] debug_log(): (ttyACM3): <-- '<CR><LF>+CPIN: 
> > READY<CR><LF>'
> > modem-manager[597]: <debug> [1300190280.001790] [mm-serial-port.c:798] 
> > mm_serial_port_close(): (ttyACM3) device open count is 0 (close)
> > modem-manager[597]: <info>  [1300190280.001826] [mm-serial-port.c:811] 
> > mm_serial_port_close(): (ttyACM3) closing serial port...
> > modem-manager[597]: <info>  [1300190280.003664] [mm-serial-port.c:834] 
> > mm_serial_port_close(): (ttyACM3) serial port closed
> > 
> > 
> > So the AT-Command to set the SIM-PIN worked correct, but ModemManager 
> > tries to send the PIN again and again and the dbus method have a timeout?!
> > 
> > 
> > Any ideas,
> > 
> > Cheers,
> > 
> > Tom
> > _______________________________________________
> > networkmanager-list mailing list
> > networkmanager-list gnome org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> 
> 

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]