Comment 5 for bug 782326

Revision history for this message
Most People Use Their Full Name here (fullname1) wrote :

According to
http://doc.qt.nokia.com/4.7-snapshot/qapplication.html#setGraphicsSystem (thanks to ~persia !) there are four ways to the the garphicssystem to use:

* the application commandline -graphicssystem switch
This is what I did above. The way I did it seems ugly, and Olivier's method doesn't work flawlessly either.

* QApplication::setGraphicsSystem()
No idea what that is.

*the Qt configure -graphicssystem
I am looking for a run time fix to this because I do not want to recompile unity-2d for every image I use

* the QT_GRAPHICSSYSTEM environment variable
This is very promising. ~persia proposed set this via Xsession.d .

I added "/etc/X11/Xsession.d/54setupenv" in my rootfs containing
export QT_GRAPHICSSYSTEM=native

I expected unity-2d-* and any other QT program to be ran with the native graphicssystem after I would restart the Xserver. Unfortunately this is not the case.
I investigated manually: From a remote console I started the unity-2d-session , killed unity-2d-launcher and ran it with

QT_GRAPHICSSYSTEM=native unity-2d-launcher

Still glitchy which means it does not run in native mode.

Starting with

unity-2d-launcher -graphicssystem native

it works flawlessly. (native graphicssystem mode present!)

This shows unity-2d-launcher does not seem to parse the QT_GRAPHICSSYSTEM environment variable but only the -graphicssystem paramter. This can also be assumed for the other unity-2d programs.