Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qt4-x11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096289
Title:
Qt
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 subsc
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 rela
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 whe
** Package changed: ubuntu => qt4-x11 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096289
Title:
Qt apps often fail to start from file manager
To manage notifications about this bug go t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
