Qt for Embedded Linux data directory is not owned by user 0: /tmp/qtembedded-0

Question

Okay so I'm very new at all of this so please forgive me if I don't provide enough information but feel free to ask for more.

I had to install ParaView from source on my linux system. ParaView requires Qt to be installed to be able to compile and install it. So I installed Qt on my linux system from source as well (version 4.8.6 to be precise). My ParaView is now installed but I can't seem to run it. The first time I tried I got the following output:

QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
No Qt for Embedded Linux server appears to be running.
If you want to run this program as a server,
add the "-qws" command-line option.

When I ran it as sudo, I got the following output:

Qt for Embedded Linux data directory is not owned by user 0:  /tmp/qtembedded-0

I have no idea what this means or how to fix it, any help will be much appreciated.

Extra info: I installed ParaView version 4.4

my Qt dir is /usr/local/Trolltech/QtEmbedded-4.8.6/bin

my ParaView dir is /usr/local/bin

I couldn't find anything on google or on here and that's why I'm asking.

Answer 1

If you want to run this program as a server, add the "-qws" command-line option.

You really need this; append it to the line where you call your binary. When trying to start it on a machine that runs X11 you'll need QVFb installed and running, too, plus support for it (graphics, mouse and keyboard) compiled into the Qt libs.

I strongly advise against starting with root privileges.

Answer 2

It seems that you ran the application under the user, then killed it, switched to root and tried to run it again. You can just remove the temporary folder. rm -rf /tmp/qtembedded-0

Answer 3

I just removed

rm -rf /tmp/qtembedded-0

and then restarted the framebuffer and it works for me.

Mistake: I changed the permission of /tmp/qtembedded-0 while framebuffer was running.