Comment 12 for bug 1620553

My turbo was affected by this yesterday and reboots didn't seem to fix it. I'm guessing usensord was wedged very quickly after startup, I was receiving lots of SMS messages around the time it happened.

Debugging this morning showed the last process that called usensord was telephony-service-indicator, which handles the notifications for SMS/MMS. The log ended with the initial call from telephony-service-indicator, so it appears usensord never replied to that request and was blocked.

After restarting usensord with upstart in my user session, it started responding like normal. I'm trying to reproduce it again to determine if telephony-service-indicator is the trigger.