Ticket #442 (new defect)
Frameworkd silently fails. On the phone everything looks normal, suspend/resume working
|Reported by:||khiraly||Owned by:||mickey|
Frameworkd silently failed. From the user point of view everything looked normal. The phone could suspend/resume, they showed a registered network, so I couldnt be aware of any failure.
Calling freerunner resulted at the other end "the number is not disponible". Just like if I would switched off my freerunner.
I have been called numerous time. I suppose (Im not sure, and cant remember exactly) the phone was suspended on the first time. But I verified by calling freerunner myself from an another phone while freerunner was awake, and I got this "the number is disponible" voice in the line.
Restarting frameworkd fixed the issue. And I could call freerunner. I see numeruos python exceptions in the frameworkd.log.
I got from dos1 and spaetz at irc, that I should disable [ophoned] in /etc/frameworkd.conf: [ophoned] disable = 1
From nytowl I got the advise, that I should install om2009 from todays build, because it will supposedly fix this bug too.
Right now, im testing with [ophoned] disabling.
Here are the logs with python exceptions (I stopped extracting them from the logs as they are many):
http://pastebin.com/m3dd29020 http://pastebin.com/m6e38038f http://pastebin.com/m5a5df672 http://pastebin.com/m364b3fd http://pastebin.com/m531838f1 http://pastebin.com/m2ba72406 http://pastebin.com/m72658e4a http://pastebin.com/m53fe8199 http://pastebin.com/m6c790f14 http://pastebin.com/m5d77a4d9
The most interesting part:
In that period I had many incoming calls (from about 6:55 am till 7:15 am). On the other end it said "the number is not disponible"