Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34117 - [qt5-base] First Qt5 application in a session takes very long time to start
Attached to Project:
Arch Linux
Opened by Mad Fish (MadFish) - Saturday, 02 March 2013, 19:01 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 09 March 2013, 18:12 GMT
Opened by Mad Fish (MadFish) - Saturday, 02 March 2013, 19:01 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 09 March 2013, 18:12 GMT
|
DetailsI've tried this in barebone Openbox session and also in KDE.
Apparently this happens to all Qt5 applications - both QtCreator and my own compiled Qt5 app exhibit the same problem. It can take up to ~20 seconds to start (didn't measure the exact time). This appears in console during that first problematic start: Qt at-spi: error getting the accessibility dbus address: "Process /usr/lib/at-spi2-core/at-spi-bus-launcher exited with status 1" Accessibility DBus not found. Falling back to session bus. qt5-base is 5.0.1-5 qtcreator is 2.6.2-2 Steps to reproduce: 1. Install qtcreator. 2. Login into clean session. 3. Launch qtcreator. 4. Observe huge delay before the application window appears. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Saturday, 09 March 2013, 18:12 GMT
Reason for closing: Not a bug
Additional comments about closing: at least not in qt5
Saturday, 09 March 2013, 18:12 GMT
Reason for closing: Not a bug
Additional comments about closing: at least not in qt5
Plain startx with "exec openbox-session" in .xinitrc also works fine.