@sconf

Did Sergey ever get back to you about whether he found anything useful in your logs?
*EDIT* It's to do with the second issue you developed, but it'd still be nice to hear from Sergey.


@derliebewolf

I think your solution will lie in carefully observing what sconf did, & trying to mimic that...
He didn't deal with it by killing processes, that's what he had to rely-on until the problem disappeared.
Upon quickly perusing, as far as I can tell this isn't the meegotouchhome issue, it's distinctly different.

Before you mimic everything he did, I'd encourage you to lodge a bug-report & describe your issue.
Mention that you can provide logs, as it may be handy to capture that data while the issue's live.
There's a big chance that you may not be able to reproduce the issue for them.
And so the bug will remain until some other unfortunate users stumble across it