Ticket #473 (closed defect: fixed)

Opened 2 years ago

Last modified 19 months ago

SIM Messages get read multiple times on restart

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

Description

On reregistering a phone application on fso, it happens that messages from sim are displayed multiple times. To reproduce this just kill your running application (ophonekitd, litephone, etc.) and start it again. After setting the pin again, reading messages from sim card is delayed and starts after some seconds. Because csm_id is not set in the new entry it will be added again to the message list.

I've added some more debugging to dump the entry variable in the method process_all_entries in pimb_sim_messages_fso.py:

2009.09.02 21:40:39.504 opimd INFO entry dbus.Struct((dbus.Int32(20), dbus.String(u'read'), 
dbus.String(u'+49171xxxx'), dbus.String(u'test4'), 
dbus.Dictionary({dbus.String(u'status-report-indicator'): 
dbus.Boolean(False, variant_level=1), dbus.String(u'more-messages-to-send'): dbus.Boolean(False, variant_level=1), 
dbus.String(u'alphabet'): dbus.String(u'gsm_default', 
variant_level=1), dbus.String(u'pid'): dbus.Int32(0, 
variant_level=1), dbus.String(u'reply-path'): dbus.Boolean(False, 
variant_level=1), dbus.String(u'timestamp'): dbus.String(u'Wed Aug 19 21:43:01 2009 +0200', variant_level=1), dbus.String(u'type'): 
dbus.String(u'sms-deliver', variant_level=1)}, 
signature=dbus.Signature('sv'))), signature=None)

I'm not sure if it really a bug in opimd or in ogsmd. If I'm wrong please chage the component.

Change History

comment:1 Changed 2 years ago by sim

 decoration Changed 1 year ago by admin

 bathtub Changed 1 year ago by admin

 solar system Changed 1 year ago by admin

 stair parts Changed 1 year ago by admin

 solar supply Changed 1 year ago by admin

comment:2 Changed 19 months ago by mickey

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

Thanks for reporting this problem. With fsogsmd, this seems to be no longer an issue.

Note: See TracTickets for help on using tickets.