Ticket #346 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

RetrieveMessagebook fails with a timout error

Reported by: charlie Owned by: mickey
Priority: major Milestone: milestone5.5
Component: framework/ogsmd Version:
Keywords: Cc:

Description

Using my taiwanese SIM card (don't know if that makes any difference), I get this error (cli-framework session):

>>> usageiface.RequestResource('GSM')
>>> gsmdevice.SetAntennaPower(True)
# I wait for the sim to be ready...
>>> gsmsim.RetrieveMessagebook('all')
DBusException: org.freesmartphone.GSM.Device.Timeout: device did not answer within 10 seconds

I attach the framework log file.

Attachments

frameworkd.log Download (133.3 KB) - added by charlie 3 years ago.
Timout error when retrieving MessageBook?

Change History

Changed 3 years ago by charlie

Timout error when retrieving MessageBook?

comment:1 Changed 3 years ago by charlie

Additional info : If I retry the call to RetrieveMessagebook?, it will eventually work.

But strangely enough, I will never be able to get the messages in the case I did register on the network before I try the calls.

comment:2 Changed 3 years ago by jluebbe

  • Status changed from new to assigned
  • Milestone set to milestone5.5

comment:3 Changed 3 years ago by daniel

This happens because reporting all the messages takes more time than the timeout. Mickey's new-timeout branch should help here, maybe you could try with that and report if that fixes your problem.

comment:4 Changed 3 years ago by johnsu01

Isn't this a duplicate of 345, which was closed as fixed?

comment:5 Changed 3 years ago by daniel

No, this is not a duplicate of 345.

Charlie, the new-timeout branch has been merged in master now and is being tested at the moment. Could you retry with a recently built frameworkd? Best would be one from today since a couple bugs related to SMS and the new parser have been fixed.

comment:6 Changed 3 years ago by daniel

Okay, I guess this is fixed... Charlie, any news? I'll close it in a couple of days if there's no answer - feel free to reopen.

comment:7 Changed 3 years ago by jluebbe

  • Status changed from assigned to closed
  • Resolution set to fixed

According to Mickey, this is fixed by the new timeout handling.

Note: See TracTickets for help on using tickets.