This looks to be a race condition before QApplication() is finished.
The following is a stack trace (missing a few debug symbols) from a hung
program. I notice the call to g_bus_get_sync near the top of the stack,
which a quick search reveals is related to the DBus integration. Also
possibly
As a temporary workaround, installing package qt4-qtconfig and selecting
the Plastique style in qtconfig appears to fix the deadlocking behavior,
though this does cause the program appearance to change.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is
Bug #1096289 appears to report the same or a very similar deadlock.
I've found a temporary workaround by installing the qt4-qtconfig
package, running qtconfig and selecting the Plastique theme (or other
non-GTK based theme).
--
You received this bug notification because you are a member of
I would like to confirm that I am seeing a similar bug with Qt programs.
In my case I am not using Okular or Texworks, but Qt Creator exhibits
this behavior when launching from the main menu, and my own custom Qt
program also exhibits the behavior when launched from within Qt Creator
itself and
