If you create an engine thread for your application and want to access the network only from that (all the network-related classes are instantiated in the engine thread's context), then the first QNetworkAccessManager::get will trigger the creation of QIcdEngine (and its DBus connections), which are then for some reason moved to the UI thread even though the call was made from the engine thread's context. This seems to happen always on the device (where bearer management is in use). Not reproducible on desktop environment.

The end-result of this is a crash or a mutex hang. Git version 1.1.1~git20110120.