Ticket #557 (closed defect: fixed)
opimd sometimes doesn't get messages
| Reported by: | PaulFertser | Owned by: | TAsn |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | framework/opimd | Version: | milestone5.5 |
| Keywords: | Cc: |
Description
I definitely got this message today's morning (and opimd was and still is running) but it never actually made it to the database:
{{ [SIGNAL] org.freesmartphone.GSM.SMS.IncomingTextMessage? /org/freesmartphone/GSM/Device :1.102 ( "Beeline", "10/05/02,07:20:14+16", "?????? 300,00 ?. ???????? 02.05 ? 07:19 ????? Sberbank" ) }}
Might be related to the fact i restarted fsogsmd many times without restarting frameworkd.
Attachments
-
0001-opimd-bind-to-the-well-known-name-for-ogsmd.patch
(1.2 KB) -
added by PaulFertser 21 months ago.
Change History
comment:1 Changed 22 months ago by TAsn
- Owner changed from mickey to TAsn
- Status changed from new to accepted
comment:2 Changed 21 months ago by PaulFertser
- Status changed from accepted to in_testing
This is partially related to the restart of fsogsmd and the fact opimd binds to the unique name instead of the well-known name. The attached patch should fix this part of the problem.
However, i noticed another problem with messages, it looked like fsogsmd not reacting to an unsoliceted signalling the message is received. I'll open a separate bug when i investigate more.
Changed 21 months ago by PaulFertser
-
attachment
0001-opimd-bind-to-the-well-known-name-for-ogsmd.patch
added
Maybe there's something with python-dbus, signals and restarting of daemons. I remember something about it, well, I guess I will just have to track fsogsmd.