Based on your backtrace I think the problem is in KDE too. It seems that QStyleFactory uses some libraries from kde4 (oxygen.so) which uses QDbusConnection (this also explains why we didn't needed QDbusConnection on our Debian/Ubuntu systems).
The problem is probably in hardcoded Qt path inside the oxygen.os library. I'm not sure if this could be solved in any other way than by using system Qt libraries.
Another solution would be to force application to use another than oxygen style, but I don't think it's a good idea.
I definitely agree with the latter.
However, when the goal is to get a fully portable application, at first trying the systems libraries doesn't seem to be a good idea either. It is likely to cause problems, if not now... then in the future.
This guy is pretty clear about this issue though.
And, a possible solution for oxygen (it is the follow up actually):
nd, actually trying to read it first :).
Maybe the 'solution' is to actually use the libQtDBus library in the application so to force it reading it from the libs/ directory?
It's interesting idea. I'm going to try it.
I tried to initialize DBus session connection at application start, so libQtDBus should be loaded from corerct place. Could you please try it?
However, maybe the message "QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave." shouldn't be taken in vain :). Probably won't do any harm but I'm always in favour of no messages at all :).
Regarding to warning message, I'm not sure if it will be possible to remove it. It's necessary to initialize QDBus before QApplication object is constructed because inside QApplication constructor oxigen.so is called.
I tried one more thing. Instead of creating DBus connection I created QDBusMessage witch didn't write error message. Could you please try if also this solution works for you? https://www.dropbox.com/s/90y8e3wip9mp7tg/deploy.zip
Yep, that works like a charm! Now, I'm a happy camper ;)
Super great ;-). Thank you for fast testing and cooperation. I will move our conversation to standalone thread.